PowerShell Scripting to Replicate QuickBooks POS Data to MySQL

Ready to get started?

Download for a free trial:

Download Now

Learn more:

QuickBooks POS Cmdlets

An easy-to-use set of PowerShell Cmdlets offering real-time access to QuickBooks POS data. The Cmdlets allow users to easily read, write, update, and delete live data - just like working with SQL server.

Write a simple PowerShell script to replicate QuickBooks POS data to a MySQL database.

The CData Cmdlets for QuickBooks POS offer live access to QuickBooks POS data from within PowerShell. Using PowerShell scripts, you can easily automate regular tasks like data replication. This article will walk through using the CData Cmdlets for QuickBooks POS and the CData Cmdlets for MySQL in PowerShell to replicate QuickBooks POS data to a MySQL database.

After obtaining the needed connection properties, accessing QuickBooks POS data in PowerShell and preparing for replication consists of four basic steps.

When you are connecting to a local QuickBooks instance, you do not need to set any connection properties.

Requests are made to QuickBooks POS through the Remote Connector. The Remote Connector runs on the same machine as QuickBooks POS and accepts connections through a lightweight, embedded Web server. The server supports SSL/TLS, enabling users to connect securely from remote machines.

The first time you connect, you will need to authorize the Remote Connector with QuickBooks POS. See the "Getting Started" chapter of the help documentation for a guide.

Collecting QuickBooks POS Data

  1. Install the module:

    Install-Module QuickBooksPOSCmdlets
  2. Connect to QuickBooks POS:

    $quickbookspos = Connect-QBPOS
  3. Retrieve the data from a specific resource:

    $data = Select-QBPOS -Connection $quickbookspos -Table "Customers"

    You can also use the Invoke-QBPOS cmdlet to execute pure SQL-92 statements:

    $data = Invoke-QBPOS -Connection $quickbookspos -Query 'SELECT * FROM Customers WHERE LastName = @LastName' -Params @{'@LastName'='Cook'}
  4. Save a list of the column names from the returned data.

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name

Inserting QuickBooks POS Data into the MySQL Database

With the data and column names collected, you are ready to replicate the data into a MySQL database.

  1. Install the module:

    Install-Module MySQLCmdlets
  2. Connect to MySQL, using the server address and port of the MySQL server, valid user credentials, and a specific database with the table in which the data will be replicated:

    $mysql = Connect-MySQL -User $User -Password $Password -Database $Database -Server $Server -Port $Port
  3. Loop through the QuickBooks POS data, store the values, and use the Add-MySQL cmdlet to insert the data into the MySQL database, one row at a time. In this example, the table will need to have the same name as the QuickBooks POS resource (Customers) and to exist in the database.

    $data | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Customers" -Columns $columns -Values $values }

You have now replicated your QuickBooks POS data to a MySQL database. This gives you freedom to work with QuickBooks POS data in the same way that you work with other MySQL tables, whether that is performing analytics, building reports, or other business functions.


  • Once you have connected to QuickBooks POS and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

    Select-QBPOS -Connection $quickbookspos -Table "Customers" | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Customers" -Columns $columns -Values $values }
  • If you wish to replicate the QuickBooks POS data to another database using another PowerShell module, you will want to exclude the Columns, Connection, and Table columns from the data returned by the Select-QBPOS cmdlet since those columns are used to help pipe data from one CData cmdlet to another:

    $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name | ? {$_ -NotIn @('Columns','Connection','Table')}