Accounting data migration cost is not a fixed figure. It depends on the system you are moving from, the volume and quality of your historical records, whether integrations are involved, and the level of support you need once you are live on the new platform. A quote that treats every migration as the same job is unlikely to reflect the work actually required.

Moving to cloud accounting can make financial information easier to access, reconcile and manage. But the migration itself needs careful planning. Before you move records from old software, spreadsheets or desktop systems, you need to understand what is driving the cost, what a realistic timeline looks like, how data quality affects both, and what should happen after go-live. This post works through each of those areas.

A meaningful quote should always be based on the records being moved, not just the name of the software. For a simple migration, the work may involve exporting core records, importing contacts, setting opening balances and checking that the trial balance agrees. For a more involved migration, you may need to clean historic transactions, rebuild bank reconciliations, map old nominal codes, review VAT treatment, test integrations and support the first reporting cycle. Those are very different jobs, and the price should reflect that.

The main cost drivers are:

• The current accounting system or spreadsheet format
• The number of bank accounts, credit cards and loan accounts
• The number of customers, suppliers and nominal codes
• The volume of transactions being moved
• Whether the business is VAT registered
• Whether payroll, stock, projects or departments are involved
• Whether there are multi-currency transactions
• How many years of history need to be migrated
• Whether old reconciliations are complete
• Whether the business needs new reports, dashboards or integrations

The biggest single cost difference usually comes from data quality. A business with clean bookkeeping, reconciled bank accounts and tidy contact records is straightforwardly easier to migrate than one with duplicated contacts, unreconciled items, old suspense balances and inconsistent VAT codes. When we scope migration work through our data migration services, we review the current records, preferred cloud platform, reporting needs and files for upload first. That gives a clearer basis for pricing the work properly.

How much history to move

Historic data adds time because every additional period means more records to export, import, map and check. Moving two years of transactions is very different from moving ten, especially where there are old bank accounts, closed suppliers, archived products or historic VAT adjustments. There are three common approaches:

1. Move opening balances only
2. Move opening balances plus selected historic reports
3. Move full transaction history for a defined period

The right option depends on how often historic information is used, what the budget allows and whether full historic detail is genuinely useful in the new system. In some cases, keeping archived reports from the old system is more practical than migrating every old transaction.

Why spreadsheets add time

Spreadsheet records often lack the structure that cloud accounting software needs. You may find inconsistent account names, missing supplier details, mixed VAT treatment, duplicate invoice numbers or no clear separation between business and personal transactions. Before a spreadsheet can be imported, the records typically need standardising: dates and descriptions aligned, sales and purchases separated, VAT codes checked, payments matched to invoices where possible, duplicates removed, a usable chart of accounts created, and opening balances confirmed. That preparation adds time, but importing unreliable data into a new system and trying to fix it afterwards is more disruptive.

Integrations

Many businesses use more than one system: payment platforms, e-commerce tools, payroll software, stock systems, job management apps or direct bank feeds. If those need to connect to the new cloud accounting platform, the migration becomes more than a data transfer. Each integration needs to be set up, tested and reviewed. An e-commerce integration may need correct VAT treatment, payment fee coding and a sales clearing account. A payroll integration may need wages, PAYE, pension and net pay liabilities to post correctly. A bank feed may need rules, account mapping and reconciliation checks. This can make the migration more valuable, but it also needs careful planning.

A proper migration is not simply an upload. It should move through scoping, data review, mapping, test migration, reconciliation, final migration and post-go-live support so that the new system starts with reliable records. A rushed migration can create problems that surface later in VAT returns, management accounts, debtor reports or year-end accounts.

Most cloud accounting migrations follow a similar sequence, with timing determined by complexity:

1. Discovery and scoping
2. Review of existing records
3. Data clean-up
4. Chart of accounts mapping
5. Test import
6. Reconciliation checks
7. Final migration
8. Bank feed and VAT set-up
9. User training and post-migration support

A clean, simple migration can move more quickly. One involving several years of data, multiple bank accounts, VAT issues, stock, payroll or reporting redesign will take longer.

Discovery

Discovery is where scope is defined: current software, target cloud platform, number of entities, VAT position, payroll links, bank accounts, reporting requirements and preferred migration date. It also helps to be clear about what the business wants from the new system. Better project reporting, cleaner debtor tracking, automated bank rules — if those needs are clear from the start, the migration can be built around them rather than simply copying the old structure.

Test migration

A test import highlights problems before the final move: missing data, incorrect mappings, formatting issues, duplicate contacts, VAT coding problems or reports that do not agree. It is particularly useful where current records are old, complex or incomplete, and it gives the business an early view of what the new system will look like before it goes live.

Timing

The timeline should be agreed around the quality of the records and the business calendar. Common migration points include the start of a new financial year, the start of a VAT quarter, or after year-end accounts are finalised. If the records are not ready, it is better to delay slightly and migrate cleanly than to force the move and spend months correcting errors.

What needs cleaning before migration

Data clean-up is frequently the difference between a smooth migration and a frustrating one. Good software helps, but it does not automatically fix old bookkeeping errors. The most common clean-up areas include:

• Duplicate customers and suppliers
• Old unreconciled bank transactions
• Incorrect VAT codes
• Suspense account balances
• Aged debtor and creditor errors
• Dormant nominal codes
• Unallocated payments
• Missing invoices or receipts
• Inconsistent product or service descriptions
• Old employee or payroll balances

If the aged debtors report includes invoices already paid, those items need correcting before migration — otherwise the new system may show money owed that is not recoverable. If supplier balances include old credits, duplicate bills or unallocated payments, the purchase ledger will not be useful after the move.

Bank reconciliations

Bank reconciliations are central to reliable accounting records. If the bank balance in the accounting software does not agree to the actual bank statement, you need to understand why before moving the data. Unreconciled transactions can affect cash balances, the sales and purchase ledgers, VAT returns, loan accounts, director's loan accounts and profit and loss reporting. Fixing this before migration gives the new system a much stronger starting point.

VAT and Making Tax Digital

VAT needs particular care because incorrect VAT coding can affect returns already submitted and future VAT reporting. A VAT-registered business should confirm the new system supports digital record-keeping and VAT return submission as required under Making Tax Digital.

HMRC's guidance on Making Tax Digital for Income Tax is relevant for sole traders and landlords moving towards digital record-keeping. MTD for Income Tax applies in phases: qualifying income over £50,000 in 2024 to 2025 means use from 6 April 2026; over £30,000 in 2025 to 2026 means use from 6 April 2027; and over £20,000 in 2026 to 2027 means use from 6 April 2028. Migration planning should account for both the current VAT position and any future digital reporting obligations.

Record-keeping obligations

For UK limited companies, GOV.UK guidance on company accounting records states that records must generally be kept for six years from the end of the last company financial year they relate to. A migration plan should not assume old records can be deleted once the new software goes live. Invoices, receipts, bank statements, payroll records, VAT workings, tax calculations and supporting documents all need to remain accessible. Every migration plan should answer two questions: what data needs to move into the new system, and what data can remain archived but still accessible.

What sits outside the migration fee

The migration fee is one part of the decision. Common costs outside the core quote include monthly cloud accounting software subscriptions, additional users, app integrations, bookkeeping clean-up, payroll set-up, training, custom reporting, ongoing support and historic data archive access. Some quotes include post-migration support; others stop once the import is complete. That difference matters. A low quote may not include the checks and guidance needed to make the system usable.

Poor migration can increase future costs through bookkeeping rework, VAT reviews, incorrect reports and year-end adjustments. If opening balances are wrong, every report after migration may need further investigation. If a bank balance is imported without resolving unreconciled transactions, the finance team may spend hours trying to understand differences. If old debtor balances are wrong, credit control reports may become unreliable. Preparing properly at the start is less disruptive than fixing problems later.

Before go-live checks

Before go-live, key financial checks should be completed: the trial balance should agree to the old system or agreed opening position; bank balances should match reconciled balances; debtors and creditors reports should be sensible; the VAT control account should have been reviewed; payroll liabilities should be reflected correctly where relevant; suspense account balances should be explained; and opening balances should be confirmed. These checks matter because the first reports in the new system will influence business decisions.

Post-migration support

Post-migration support should help the business use the new system properly. Useful support includes first-month reconciliation, an opening balance review, bank feed checks, a VAT return review where relevant, debtor and creditor report checks, user permission set-up, practical training and query support after go-live. The first month-end or quarter-end after migration is the first real test. If anything looks wrong, it should be investigated early — waiting until year-end makes issues harder to trace. Training should cover anyone who uses the accounting system regularly, and it should be role-specific: a director reviewing dashboards needs different guidance from a bookkeeper posting purchase invoices.

What to ask before accepting a quote

Before accepting a quote, ask: what data is included; how many years of history will be migrated; whether data clean-up is included; whether a test migration is included; who checks the balances; whether software subscriptions are separate; whether bank feeds and VAT settings are included; what post-migration support is included; and what happens if old data is missing or inconsistent. Those questions make it easier to compare quotes fairly.

Once set up correctly, cloud accounting can support bank feeds, invoice tracking, debtor management, VAT reporting, cash visibility and management accounts. We have explored this further in our guide on how SMEs can use accounting data to make smarter business decisions, because the real value comes from using the information properly after migration is complete.