Xero Conversion Balances vs Historical Transactions: What Happens to Your Accounting History?

What are Xero conversion balances?

When a business starts using Xero, conversion balances establish the opening financial position at the chosen conversion date. They are not a recreation of every invoice, payment, bank transaction or journal that produced those balances.

Depending on the conversion date and setup, these figures can include bank accounts, VAT, loans, fixed assets, retained earnings and year-to-date profit and loss. Outstanding customer and supplier invoices and credit notes need particular care: the control account total must agree with the individual outstanding items entered in Xero.

For example, a £150,000 trade debtors balance shows the total outstanding. It does not identify the individual unpaid invoices or recreate all the invoices customers paid in previous years. Entering outstanding invoices can provide the open-item detail without reconstructing the complete historic sales ledger.

Year-end point: Xero presents prior-year profit and loss within retained earnings in balance sheet reporting. This does not mean earlier profit and loss transactions exist in Xero. Conversion figures should agree to the appropriate approved closing position, including relevant year-end adjustments, with the conversion date and financial year carefully considered.

What is a full historical transaction migration?

A full historical migration recreates agreed accounting transactions in Xero, rather than importing only their net effect. Scope may include sales and purchase invoices, credit notes, payments and allocations, bank transactions, general ledger journals, VAT information, foreign currencies and departmental classifications.

The value is the ability to investigate the transactions behind a figure and report on past periods within the new system. But an ERP and Xero do not necessarily process accounting periods, tax or allocations identically. Records must be mapped and reconciled; not every source-system field or operational feature can be reproduced.

For a practical explanation of the controls involved, see our Xero migration reconciliation guide.

Five ways to retain accounting history

1. Keep the old accounting system read-only

Keeping an existing Sage, Exchequer or other ERP system available can preserve familiar reporting and original records. It can also be expensive: licences, hosting, servers, reporting modules and technical support may remain necessary. Finance teams may have to combine reports from two systems for trends and year-on-year comparisons. Confirm that “read-only” still permits the reports and attachments you need.

2. Import monthly historical movements

Monthly nominal movements, potentially split by department, can support trend reporting without recreating every older transaction. This is useful when finance needs to compare monthly results but does not need invoice-level drill-down for older years. Import design matters: balances, movements and opening positions must not overlap or duplicate one another.

3. Preserve Excel reports and exports

Trial balances, general ledgers, aged reports, VAT workings and bank reconciliations can be retained as controlled Excel or PDF archives. This may be inexpensive, but producing an unexpected audit report later can be difficult if the necessary detail, attachments or report parameters were not exported. Secure storage, version control and retention arrangements are essential.

4. Migrate historical transactions into Xero

Moving the agreed individual transactions makes recent and past periods easier to compare and investigate within one accounting environment. It can reduce dependence on old software and allow a review of reporting structures. It takes more preparation, testing and reconciliation, and specialist ERP functions may remain outside scope.

5. Combine detailed history and monthly comparatives

A hybrid approach can bring recent periods across transaction by transaction and older periods as monthly comparative movements. It balances drill-down where needed with long-term trends. The finance team must understand which periods are detailed and which are summary-only.

Comparison: what each approach gives you

None is universally cheapest over the lifetime of a business. Compare initial migration cost with the time and software cost of accessing and combining historical information later.

Why monthly comparisons are not the same as transaction history

Suppose a monthly marketing report shows £5,100 in February last year and £6,400 this year. A monthly movement can show the £1,300 increase, and departmental totals may show where it happened. It cannot tell you which suppliers, invoices or adjustments created that change.

For those questions, you need underlying records in Xero or an accessible archive. Summary reporting shows what changed; transactional history helps explain why.

Real example: Exchequer to Xero with five financial years of departmental reporting

In an Exchequer to Xero migration for a waste management solutions business, the client wanted detailed recent accounts and the ability to compare departmental performance over several years. They did not need individual transaction drill-down for the three oldest financial years.

We designed a hybrid migration around the reporting requirement:

• Current financial year: full transactional history, including departmental reporting.
• One previous financial year: full transactional history for investigation and drill-down.
• Three earlier financial years: monthly comparative movements mapped by department, enabling historical trends and departmental comparisons without recreating each transaction.

That provided five financial years in total, including the current year — two detailed years and three summary-comparative years. The client could split and compare departmental results across the five-year span while retaining transaction-level detail where it mattered most.

The business also used an external CRM to manage older customer history. Because those records remained accessible there, the team did not need to recreate every older customer transaction in Xero purely for customer-reference purposes.

The lesson: the right migration is not necessarily the one that imports the most records. It is the one that preserves the detail needed for reporting, investigation and compliance.

Based on a real Exchequer to Xero migration completed by Migrate My Accounts for a business in the waste management sector.

Can you improve historical data during migration?

Yes. A migration can be an opportunity to map old nominal codes to a cleaner Chart of Accounts, consolidate duplicate contacts where appropriate, standardise descriptions and plan more useful departmental reporting. This can improve how historic information is analysed alongside new transactions.

However, restructuring must not rewrite accounting facts. Amounts, tax treatments, source references and the accounting substance need to remain traceable; authorised changes should be documented and reconciled. The goal is a clearer reporting structure, not an unexplained adjustment that makes the trial balance appear to agree.

For example, Xero supports two Tracking category dimensions. A source ERP with a more complex department and cost-centre hierarchy needs a reporting design before the import begins; it cannot be assumed that every dimension will transfer one-to-one.

Why moving to Xero mid-financial-year needs more planning

Consider a business with a December year-end that starts using Xero on 1 July. January to June have already been processed elsewhere. If only opening balances are transferred, the finance team may not have transaction-level year-to-date reporting inside Xero for those six months.

It must decide whether to bring across year-to-date transactions, import appropriate monthly movements or combine reports from two systems. It must also decide how to handle adjustments posted to the source after extraction and how to maintain a clear cut-off.

VAT periods crossing the migration date

A VAT quarter may include months processed in both systems. The business needs a documented plan for returns already submitted, outstanding VAT, late invoices and credit notes, cash or invoice accounting and Making Tax Digital obligations. Importing a historic invoice does not automatically recreate its previous VAT return status. Care is needed to prevent duplicated or omitted VAT.

Audits and year-end

Auditors may need evidence from both systems, including reconciled trial balances, general ledger detail, aged receivables/payables, VAT workings and bank reconciliations. A migration reconciliation pack and retained supporting records help establish a traceable link between the old system and Xero.

What should be retained for VAT, audit and outstanding items?

At a minimum, plan how the business will retrieve source-system reports and supporting evidence, even when historical transactions have been migrated. Individual invoices, approvals, attachments, bank statements and contractual records may still need to be retained.

Check that trade debtors and creditors reconcile not only at trial-balance level but also to the outstanding invoices, credits and allocations. Bank balances need supporting reconciliations. VAT transaction amounts and VAT return reporting status are distinct, and each needs appropriate review.

Retention obligations vary by country and record type. UK businesses should check the applicable HMRC and statutory record-keeping rules with their professional advisers rather than assuming a Xero migration replaces those obligations.

Can you add years of transactions after going live?

Xero can accept transactions dated in earlier periods subject to permissions, locks and other restrictions. But adding years of history to a live organisation is not simply an extra upload. Imported records can duplicate conversion balances or interfere with VAT reporting, bank reconciliations, receivables, payables and allocations already in use.

For some businesses, starting a fresh Xero organisation and planning a second migration is the safer route. This is not an absolute Xero technical prohibition; it is a practical consequence of the accounting and reconciliation risks. If detailed history might be needed later, decide before the first go-live.

How to choose the right migration approach

Ask how often you compare historical months, whether your team needs to investigate individual transactions, what it costs to retain the old system and whether the new Chart of Accounts or departments will differ. Consider the timing of VAT periods and the financial year, the reliability of source data, and the reports you might need three to five years from now.

For broader planning, see our Xero data migration guide and historical data migration service.

For system-specific guidance, explore our Sage 200 to Xero, Sage 50 to Xero, Access Dimensions to Xero, Exchequer to Xero, Business Central to Xero and Sage Intacct to Xero service pages. Each system has different migration and reporting considerations.

Frequently asked questions

Do I need to migrate every previous financial year?

No. Opening balances, monthly comparatives, a controlled archive or a hybrid approach may be suitable depending on the reporting and audit needs.

Can monthly movements provide previous-year comparisons?

Yes, if the monthly and departmental figures are imported and mapped appropriately. They will not give invoice-level drill-down for those summary periods.

Will a full migration reproduce historical VAT returns?

Not automatically. Historical transactions and VAT return reporting status require separate review and reconciliation.

Can I close the old system after migration?

Potentially, once you have confirmed required records and evidence are retained and can be retrieved, and contractual, audit and statutory obligations have been addressed.

Is a mid-year migration possible?

Yes, with careful planning for year-to-date reporting, VAT periods, cut-off transactions and reconciliation.

Does full history include all ERP features and attachments?

Not necessarily. Stock, projects, orders, fixed assets, attachments and specialist functionality must be assessed and scoped separately.

Final thoughts: plan for the reports you will need tomorrow

Conversion balances can be entirely appropriate. Monthly movements can provide meaningful trends. Read-only systems and Excel archives can preserve important evidence. And full historical migrations can make investigations and multi-year reporting easier.

The best approach depends on what the business needs to compare, investigate and retain — not simply how many years can be imported.

Think about the reports you will need tomorrow, not just the balances you need on day one.