ACCOUNTING & OPERATIONS

Switching accounting software: opening balances and the cutover plan

Moving the customer list is usually easier than deciding which records belong in the old books and which belong in the new system. A successful switch starts with an agreed cutover and a way to prove the new starting position.

Two open ledgers connected by a bridge of index cards carrying invoice folders across a blue date marker.
The cutover should preserve the starting position and the detail needed to explain outstanding work.
In this guide
  1. Agree the cutover before exporting files
  2. Distinguish opening totals from supporting documents
  3. Create a record inventory the team can review
  4. Prevent bank-feed overlap and duplicated history
  5. Use the destination product’s conversion rules
  6. Keep the old system accessible for a defined purpose
  7. Sign off the starting position and the daily routine

Agree the cutover before exporting files

A cutover date separates the work maintained in the previous system from the work maintained in the new one. Without that boundary, two people can record the same receipt in different places or neither person records a late supplier bill. Choose the date with the accountant and the people who actually maintain invoices, purchases and bank activity.

Write down what happens to work arriving around that date. An invoice raised earlier but paid later needs an understood home. So does a refund, credit note or supplier bill that arrives after the transition. The date is a shared operating decision, rather than a setting one administrator chooses alone.

Distinguish opening totals from supporting documents

Opening balances establish a starting position. Outstanding invoices and bills provide detail about who still owes or is owed money. Importing a contact list does not recreate those obligations, and copying documents without reconciling their totals does not establish a correct starting position.

Xero’s conversion guide explicitly connects conversion balances with outstanding customer and supplier documents. Treat that as a requirement to resolve with the accountant, not a reason to improvise adjustments. The exact migration route can depend on the software, source records, organisation and agreed history scope.

Create a record inventory the team can review

Suggested migration inventory; values remain for your team to confirm
Record groupWhat to preserveWhat acceptance should establish
Accounts and balancesApproved account mapping and dated balancesStarting totals agree with the reviewed source
Unpaid invoices and billsIdentifiers, remaining amounts and counterpartiesDetail reconciles with the agreed starting position
Bank recordsAccount, currency and import start dateNo unexplained gap or overlapping import
Attachments and historyRequired documents and usable archiveThe team can retrieve a known older record
Operational settingsRoles, invoice layouts and recurring workNormal work can continue in the retained plan

Keep source exports unchanged and create working copies for transformation. Record the extraction date and what each file contains. If a supplier says historical data is included, ask which periods, record types, attachments and relationships are covered. A single headline about years of history is too vague for an acceptance check.

Prevent bank-feed overlap and duplicated history

A common transition risk is importing activity already represented in the opening position or in an earlier import. Intuit’s opening-balance guidance warns that adding earlier transactions without the necessary adjustment can count amounts twice. The linked instructions concern the US product; use the local product’s documented migration process for a real implementation.

For a fictional move, suppose the agreed opening position is at 31 October and routine new activity begins on 1 November. Write down the exact bank-import window and inspect the first imported statement period against that decision. If a late item belongs to the earlier period, route it to the accountant rather than quietly shifting the agreed boundary.

Use the destination product’s conversion rules

Xero’s conversion-date guidance says its conversion date is the first day of a month and explains handling of invoices and bills unpaid at conversion. Another product or managed migration route can have different requirements. Keep general project planning separate from the destination’s actual import rules.

Ask the migration owner to demonstrate a small sample first. Include one unpaid customer document, one supplier document, an attachment and a bank account. Review identifiers, remaining amounts and the resulting reports before authorising a larger import. The presence of rows in a screen is a weaker check than a reviewed relationship and total.

Keep the old system accessible for a defined purpose

A move need not place every historical transaction inside the new application. The business may retain an organised archive or another agreed access arrangement. Decide what must remain available, who can retrieve it, which format is usable and what happens when the old subscription ends. Confirm the required retention approach with the business’s accountant.

Test retrieval while the old service is still available. Ask someone other than the person performing the migration to locate a known invoice and its attachment. If they cannot do it from the retained handover notes, the archive is not yet ready for ordinary use. Include archive access or export work in the migration proposal.

Sign off the starting position and the daily routine

Before switching normal work, review the starting balances, outstanding-document totals, a bank reconciliation and the first invoice produced by the new setup. Assign owners to unresolved differences and record whether they prevent cutover. Keep payment instructions and live financial operations under the company’s established approval process.

Then test the everyday handover: who raises the next invoice, who reviews the next supplier bill and who answers a query about the old period? Use our first-year accounting cost guide to budget overlap, setup and training. Browse the accounting profiles once the data and operating requirements are clear, rather than treating a lower introductory price as a complete migration plan.

Frequently asked questions

Are opening balances the same as historical transactions?

No. Opening balances establish a starting position. Historical records and outstanding invoices or bills contain supporting detail and require a migration scope that reconciles with that position.

Should I import all bank transactions before the cutover?

Use the import period agreed with the accountant and the destination product’s migration rules. Overlapping opening balances and transaction history can duplicate amounts.

Do I need every old transaction in the new system?

That depends on the reporting, operational and retention requirements. Define a usable historical archive or migration scope and verify retrieval before ending old-system access.

Put the guide into practice

Explore accounting tools, then compare your shortlist.

Explore the category →