Moving accounting systems? Check these seven things first

Changing accounting software can promise a cleaner view of the business. It can also interrupt invoicing, payments, reporting, and the work people do every day. The safest starting point is a short plan for what must still be true after the move, not a list of features in the new product.

This checklist is for an owner or operations lead planning an accounting-system migration with a bookkeeper, accountant, or implementation partner. It applies whether you are moving from spreadsheets, changing cloud platforms, or bringing several disconnected processes into one system. Each product has its own conversion rules, so use its current documentation for the actual import steps.

1. Name the reason for moving

Write down the problem the new system must solve. Is month-end close too slow? Are invoices separated from project work? Are approvals and account access unclear? Choose two or three outcomes you can test. For example: the person approving a bill can see its supporting document, and the owner can review receivables without rebuilding a spreadsheet. A new subscription will not fix an unclear responsibility by itself.

2. Choose a cutoff and define what moves

Pick the date when the new system becomes the place for new transactions. Decide whether you are moving full transaction history, summary opening balances, or only selected lists and open items. Record that choice before importing anything. Xero's US conversion guide distinguishes the conversion date from the date an account is opened and uses the prior system's closing balances to establish the new starting point. The exact date rules depend on the platform.

Avoid a vague overlap in which someone enters the same invoice in both systems without knowing which is authoritative. If parallel entry is needed for testing, label the test records and agree on when it ends.

3. Preserve a readable copy of the old books

Before changing access or canceling a subscription, export the records your accountant and team may need later: financial statements, general ledger detail, customer and vendor lists, open invoices and bills, reconciliations, and supporting documents. Note which attachments and audit history are included. An export is useful only if someone can open it and locate a transaction afterward. Assign an owner for storage and access.

Do not assume every field, attachment, or workflow will convert. Intuit's US migration guidance has a pre-migration checklist and product-specific limits. Use the source and destination vendors' current instructions to make a written list of what transfers and what must be rebuilt.

4. Reconcile before import, then compare after

Close the period as cleanly as practical in the old system. Capture the trial balance, balance sheet, profit and loss, bank and credit-card reconciliations, and aging reports as of the chosen date. In the new system, compare the same date and accounting basis. Investigate differences in opening balances, unpaid invoices, bills, inventory, payroll, and tax accounts with the responsible finance professional before treating the move as complete.

A migration can appear successful while the first reconciliation is wrong. Intuit's first-reconciliation guidance explains why an incorrect opening balance can cause that problem. The practical lesson is to check the starting figures against real statements, not only against an import success message.

5. Test the work around the ledger

Run a small set of representative tasks with the people who will use the new setup. Create an invoice, apply a payment, approve and pay a bill, correct an error, and produce the report leadership expects. Include a recurring transaction and an unusual case. Check templates, payment links, customer communications, and integrations with payroll, time tracking, banking, or property systems. Document who owns each connection and what happens if it stops syncing.

6. Give access deliberately

Identify the business owner of the account, the person who administers users, and the outside professionals who need access. Give each person the access needed for their role and test who can approve, change bank details, export data, or view sensitive records. Keep a way to recover the account if a staff member or implementation partner leaves. A shared login may feel convenient during setup but makes the handover harder to audit.

7. Set a short stabilization period

Name who receives questions during the first close, who fixes import exceptions, and when the team will compare reports again. Keep the old system available according to the agreed record plan until the necessary history and attachments are confirmed. Document remaining work rather than hiding it behind a sign-off. A clean migration is one your team can operate after the implementation partner leaves.

What to bring to an implementation conversation

Bring the current platform, the target platform if chosen, the reasons for changing, the desired cutoff, a list of connected systems, recent reconciled reports, and a few examples of the daily work. Ask a prospective partner to define what they will migrate, what they will test, who resolves differences, what your team receives at handover, and what falls outside the scope. You should be able to compare proposals on those terms, not just the import fee.

Actif's finance consulting and automation and engineering work can connect the books with the systems and decisions around them. If you are weighing an accounting-system change, request a consultation with the problem you want the move to solve.