BusinessVision to QuickBooks Desktop: A Full Migration Playbook

BusinessVision data will not copy into QuickBooks Desktop; this playbook covers the cutoff, mapping, and reconciliation that make the move succeed.

BusinessVision and QuickBooks Desktop share no data structure, so this conversion is a rebuild, not a copy. QuickBooks ships no converter for BusinessVision company data, which means every account, list, and opening balance has to be mapped and moved deliberately. The projects that go well follow a fixed sequence. This playbook lays out that sequence, the checks inside each phase, and the points where you can still turn back. If you would rather hand the move to an engineer, our data conversion services follow this same sequence.

Take a verified backup and the credentials first

Start in the legacy system, not in QuickBooks. Run the backup utility inside BusinessVision and let it finish; copying the live data folder while people are working can capture files mid-write. Restore the backup into a scratch location and open it before anything else. A backup that has never been restored is a hope, not a rollback point.

You will also need the supervisor credentials for the BusinessVision data, because module data cannot be validated without them. At the same time, pull a trial balance, the receivables and payables agings, and an inventory valuation report, all dated the same day. Those reports become the acceptance test for the new file.

Decide the QuickBooks Desktop edition now, since inventory, sales tax, and user seats shape how the lists get mapped.

Freeze the legacy data at a cutoff

Pick a cutoff date and make it a hard stop. A period end works best, because the balances are already proven and few transactions are in flight. Post everything the system is owed, then stop new entry and close the periods so nobody backdates into the frozen range.

Print the cutoff reports after the last entry, not before; balances move even on quiet days. From here on, those reports are the fixed reference for every number that appears in QuickBooks.

Tell the team what the freeze means: invoices, bills, and payments wait, or they are captured after cutover. Keep BusinessVision available read-only, because its history still gets consulted. If the project stalls, lift the freeze and resume posting; nothing in QuickBooks matters until cutover.

Map accounts and lists before anything moves

Export the BusinessVision chart of accounts and map every account to a QuickBooks account of the correct type. Retire dormant accounts during the mapping instead of carrying clutter forward.

Decide the item strategy next. BusinessVision inventory and order entry do not translate one to one into QuickBooks items, so work out what becomes an inventory part, a non-inventory part, or a service. Map customers, vendors, payment terms, and sales tax treatment at the same time, because QuickBooks handles tax codes differently from most legacy systems.

Write the whole mapping into a spreadsheet and keep it. It is the audit trail for every opening balance in the new file.

Build the file and load the opening balances

Create the QuickBooks company file with the correct fiscal year start, and keep a pristine copy of it before any list is imported. If an import goes wrong, you rebuild from the empty shell rather than patching a half-loaded file. That untouched copy is this phase's rollback point.

Import the lists, then bring the trial balance across as one journal entry dated at the cutoff. For receivables, payables, and inventory, choose between control totals and full detail. Detail takes longer, though a team cannot apply a payment against an invoice that never entered the file, so open invoices and bills usually need to exist as real transactions.

Load inventory quantities and values at the cutoff, and confirm the inventory asset account ties to the valuation report before moving on.

Reconcile the trial balance and the open transactions

Run a QuickBooks trial balance at the cutoff and compare it to the BusinessVision report line by line. Every difference needs a cause you can name in writing.

Check the detail under the totals. An aging where every customer balance matches builds more confidence than one control figure, and the same holds for payables. Reconcile each bank and credit card account through the cutoff, and confirm the inventory value still ties to the balance sheet.

Run Verify Data on the new file too. A fresh file that fails verification points at the import, not at QuickBooks, and it should be fixed before anyone works in it. Where a converted file keeps failing those checks, our Verify and Rebuild repair service deals with exactly that problem.

Roll the team onto the new file

Set up QuickBooks users and permissions, then test multi-user mode from every workstation before go-live day, not on it. Multi-user problems are much cheaper to find on a quiet afternoon than on go-live morning.

Take a verified backup of the finished file and store it away from the host machine. Keep BusinessVision frozen and read-only for a defined stretch so its history stays available.

For the first week, reconcile new-file activity against source documents: one deposit, one customer payment, one supplier bill. Small proofs catch mapping mistakes while they are still cheap.

What does a clean cutover look like?

The trial balance at the cutoff matches BusinessVision exactly, account for account. The agings reconcile to it in detail, not just in total. Banks and credit cards reconcile through the cutoff, and the inventory value on the balance sheet equals the valuation report.

The sequence also leaves evidence: the restored backup, the frozen reports, the mapping spreadsheet, the matching trial balances. Any number in the new file traces back to a legacy report without guesswork. That traceability is what separates a migration from a leap of faith.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.