Converting Sage BusinessWorks to QuickBooks Desktop or Online

A phased migration playbook for exporting Sage BusinessWorks master lists and transaction history into QuickBooks Desktop as an intermediate format before uploading to QuickBooks Online.

Sage BusinessWorks stores chart of accounts, customer, vendor, inventory, and transaction data in a proprietary structure that QuickBooks cannot import directly. Our engineers route every BusinessWorks conversion through QuickBooks Desktop as an intermediate format, which rewrites the data into a native .qbw structure. From there, the file can either remain in Desktop or upload to QuickBooks Online. This playbook covers the full path: source preparation, list and transaction export, intermediate Desktop conversion, and Online upload.

Source File Assessment

Before any conversion work begins, we need a current, verified backup of the Sage BusinessWorks company database. The backup must be the most recent version of the file and should include every module the business actively uses—general ledger, accounts receivable, accounts payable, inventory, sales orders, and purchase orders.

Gather the following before submitting the file:

• The BusinessWorks backup archive (or a secure upload link if the file exceeds email limits)
• The administrator password for the BusinessWorks file
• Confirmation of the BusinessWorks version and edition
• A list of active modules and the fiscal year-end date
• The target QuickBooks Desktop edition and version year (Pro, Premier, or Enterprise)
• Whether the destination is QuickBooks Desktop or QuickBooks Online

If confidentiality is a concern, a non-disclosure agreement can be signed before the file is transmitted. An accurate quote requires evaluating the actual backup file, not a summary or screenshot.

Scope and Data Mapping

Our engineers open the BusinessWorks backup in an isolated environment and run a full inventory of the source data. This includes counting all active and inactive customers, vendors, inventory items, chart of accounts entries, and historical transactions. We map each BusinessWorks module to its QuickBooks equivalent and flag structural differences that require translation:

• BusinessWorks custom fields are mapped to the closest QuickBooks equivalent or to custom fields where available.
• Inventory valuation methods are reviewed for compatibility with QuickBooks inventory tracking.
• Multi-currency settings, if present, are documented so the target file is configured correctly before import.
• Historical transaction depth is confirmed—typically two to three full fiscal years, though the cutoff is adjustable.

This phase produces a conversion specification that both sides review before the actual data transfer begins.

Intermediate Desktop Conversion

BusinessWorks data cannot be loaded straight into QuickBooks Online. We use QuickBooks Desktop as a bridge format because it accepts structured imports and produces a native company file that the Online migration tool recognizes.

During this phase our engineers:

1. Create a new, clean QuickBooks Desktop company file configured with the correct fiscal year-end, chart of accounts structure, and multi-currency setting.
2. Import the master lists—customers, vendors, employees, items, and accounts—using structured export files pulled from the BusinessWorks database.
3. Import transaction history within the agreed date range, including invoices, bills, payments, credits, journal entries, and inventory adjustments.
4. Reconcile opening balances for every balance-sheet account against the BusinessWorks trial balance as of the conversion cutoff date.

If the resulting Desktop file is oversized—particularly when the destination is QuickBooks Online, which has list and file-size ceilings—we may recommend running a SuperCondense to trim the file to a manageable range before upload.

Upload to QuickBooks Online

When the Desktop conversion is verified and the target is QuickBooks Online, the file is handed off for upload. The Online migration is typically managed by the customer or through Intuit's assisted migration process, using the Desktop file as the source.

Before initiating the upload:

• Confirm the QuickBooks Online subscription tier supports the list sizes and feature set in the converted file.
• Verify that multi-currency is enabled in the Online account before starting the migration if the Desktop file uses it.
• Schedule the upload during a window where no new transactions will be entered in BusinessWorks.

Verification and Rollback Points

Each phase has a distinct checkpoint. After the Desktop conversion, our engineers run a full verify and rebuild on the intermediate file, then compare key reports—trial balance, A/R aging, A/P aging, and inventory valuation—against the BusinessWorks source. Discrepancies are corrected before the file moves to the next stage.

Rollback is available at two points. Before the Online upload begins, the Desktop file serves as a complete fallback. After the upload, the BusinessWorks backup and the converted Desktop file both remain available, so data can be re-examined or re-migrated if the Online account is misconfigured.

Clean Outcome

A successful conversion produces a QuickBooks company file—Desktop or Online—where master lists match the BusinessWorks source, historical transactions post correctly within the agreed date range, balance-sheet accounts reconcile to the cutoff trial balance, and the file passes verification with no errors.