How to Manage a Multi-Company Sage 200 to Xero Migration

Moving a large Sage 200 group to Xero is not simply the same migration repeated many times. The challenge is to create a repeatable group method while keeping enough entity-level control to explain, reconcile and sign off every company.

We use that approach on large multi-company projects, moving through the group in a controlled sequence rather than relying on one oversized cutover.

Choose the migration sequence before the first import

A multi-company migration is easier to control when the order is deliberate. The first entity can be selected to test the agreed mapping and process, while later companies follow once the method is proven. Sequence can also reflect year ends, VAT deadlines, currencies, entity size and operational priorities.

For larger groups, this reduces the pressure to solve every possible exception at once. Lessons from the early entities can be applied to the remainder of the programme without losing control of what changed and why.

Standardise what should be consistent, not everything

Group migrations usually benefit from common rules for Chart of Accounts mapping, contacts, reporting structure and the way departments or cost centres are treated. That consistency can make both migration and future group reporting easier.

But entities are rarely identical. One may use foreign currency, another may have unusual control-account history, and another may need a different reporting treatment. A good group process makes the standard decisions repeatable while recording the exceptions rather than forcing them into the same shape.

Keep reconciliation evidence at entity level

Scale should not weaken the accounting evidence. Each company still needs source reports, mapping decisions and reconciliation checks that can be traced back to that entity and period.

Depending on scope, this can include Trial Balance comparisons, Aged Receivables and Payables, VAT checks, transaction sampling and documented explanations for material differences. The group may be managed as one programme, but sign-off remains understandable company by company.

Resolve foreign-currency differences early

Foreign-currency entities can introduce additional differences because Sage 200 and Xero do not necessarily calculate or present revaluation in the same way. These are much easier to investigate while the entity is being processed than after dozens of companies have already moved.

Agreeing the source reports, exchange-rate treatment and expected reconciliation before import helps separate genuine migration issues from differences caused by the two systems' accounting behaviour.

Keep the finance team operational during a phased migration

A group project has to work around the finance team's real deadlines. VAT returns, month end, year end and day-to-day processing continue while the migration is happening. A phased plan makes it possible to hand over completed entities while the remaining companies continue through extraction, transformation and validation.

Clear cut-off dates and responsibilities matter here. Everyone should know which system is authoritative for each entity, what changes are still allowed in the source and when final adjustments will be reflected in Xero.

Use a repeatable migration cycle

1. Confirm scope and evidence. Agree history, entities, currencies, mappings and source reports.
2. Extract and validate. Check that the Sage 200 data and reports needed for reconciliation are complete.
3. Transform. Apply the agreed group mapping and any entity-specific restructuring.
4. Import to Xero. Move the historical data using the agreed migration method.
5. Reconcile. Compare Xero back to the source evidence and investigate material differences.
6. Hand over and repeat. Document the entity, capture any lessons and apply the controlled process to the next company.

A real-world example: Care Concern Group

Care Concern Group is one example of this methodology in practice: 33 companies and around 2.6 million historical transactions were migrated from Sage 200 to Xero in under four months.

The full project story belongs on the Care Concern Group case study; here, the point is simply that large group migrations remain manageable when sequence, mappings, reconciliation and exceptions are controlled entity by entity.

For the client story and wider project context, see the Care Concern Group case study.