Moving from spreadsheets to accounting software

Moving from spreadsheets to accounting software requires a defined cutover date, reconciled opening figures and a plan for historical evidence. Map accounts and tax codes before importing so errors are not multiplied across the new ledger.

Keep the original spreadsheet version and document transformation rules. Test a small representative import before moving all records and switching reporting responsibility.

Choose a cutover that preserves continuity

Agree the date from which the new system will become the authoritative ledger and identify the last period completed in the spreadsheet. List outstanding invoices, bills, bank balances and unresolved adjustments at that point. A cutover in the middle of a VAT period is possible to plan, but it needs a clear explanation of how the full period's records and return will be assembled without gaps or duplicated figures.

For a VAT-registered business, the migration must preserve the required records and the appropriate digital journey through the reporting process. HMRC's record-keeping guidance allows different system arrangements, but the complete setup must meet the applicable requirements. Moving totals into a new package does not automatically demonstrate that the transaction evidence or digital links have been preserved. Review the proposed path before the old spreadsheet is retired. ^[1]

Clean the source data without rewriting history

Save a dated copy of the original workbook and identify the sheets used for sales, purchases, bank records and adjustments. Resolve obvious duplicates and unexplained balances with supporting evidence. Keep a log of changes rather than silently modifying historic figures until they match the desired opening position. The migration should make the records clearer, not conceal discrepancies that still require an accounting or tax decision.

Check dates, decimal formats, currency and whether amounts include VAT. A column headed 'total' may mean gross sales in one sheet and net receipts in another. Document the mapping for each source field before import. If the workbook contains formulas, preserve the relevant calculation evidence and check whether the export contains values, formulas or both, so the receiving system gets the intended information.

Map accounts and tax treatment deliberately

Create a mapping table from the spreadsheet categories to the new chart of accounts and tax codes. Review unusual items separately, including owner transfers, loan payments, assets and mixed-purpose costs. Do not assign every unmapped item to a general expense code merely to complete the import. A small exception list is preferable to a clean-looking ledger containing decisions that nobody has actually reviewed.

Agree whether historical transactions or only opening balances and outstanding items will be imported, based on reporting and access needs. Keep the remaining history in a usable archive. If customer or supplier balances are brought across, ensure the individual items reconcile with the control total. Importing both a balance and the same underlying invoices without the correct method can duplicate the amount owed.

Test a representative sample first

Use a small set containing an ordinary sale, credit note, supplier bill, part payment and transfer. Check the resulting accounts, VAT amounts and document links. Compare the new system's totals with the source before scaling up. A successful upload message only confirms that the file was accepted; it does not prove the fields were interpreted correctly or that the transactions landed in the right reporting period.

Keep the test separate from the live ledger or use the provider's supported rollback process. Record what was changed in the mapping after the test and use the corrected version for the full import. Avoid repeated live imports without a reconciliation, because each attempt can introduce duplicates or leave only part of the dataset updated. The business should know which import is the final accepted version.

Reconcile and hand over the new routine

After migration, compare bank balances, receivables, payables and the VAT control position with the agreed cutover schedule. Trace several transactions back to their original evidence. Investigate differences before the first return or management report is approved. Assign responsibility for new entries, corrections and any remaining historic questions so the spreadsheet and software do not continue as competing versions of the same books.

Use Keeping audit trails when correcting entries for maintaining a correction trail and Accounting software migration support to discuss a spreadsheet migration. Provide the workbook structure, reporting deadlines and the proposed cutover date, initially without unnecessary personal data. A useful scope identifies data cleaning, mapping, import, reconciliation and archive access as separate tasks, making the completed transition reviewable rather than relying on the statement that the software is now live.

Retain the mapping table and final reconciliation with the archive. They explain why an old category appears under a different name in the new system and help future advisers trace opening balances. Close the old entry process explicitly so staff do not continue recording new transactions in a workbook that is no longer reviewed.

Illustrative scenario

A consultancy migrates a year of spreadsheet entries. A trial import shows that credit notes have the wrong sign, so the team corrects the mapping before loading the full dataset.

Preparation checklist

• Choose the cutover date
• Reconcile opening figures
• Test mapping and signs
• Archive source records