Move off Excel without losing your history

What comes across

The whole record, not a starting balance. A trust that migrates only its closing figures cannot answer a member query about 2019, and cannot show an inspector how a balance was arrived at.

Member records

Employee master data, nominees, and the identifiers your payroll system keys on.

Pay data and historical transactions

Contribution history period by period, not a single opening figure with the detail thrown away.

Attendance history

Carried across alongside the pay data it belongs to.

Member ledgers and opening balances

Loaded and reconciled, because every figure above them depends on these being right.

Interest history

Validated against your prior declarations rather than recomputed and hoped over.

Where we have migrated trusts from

If your system is not on this list, it is very likely still fine — the extraction work is driven by the shape of your data, not the badge on the software.

• Raycomputech
• Vista
• PROMIS
• C-Quel
• Excel-based setups

How a migration runs

The honest version, because an underestimated migration is the most common reason these projects go badly. A standard implementation runs to roughly 30 days; a trust with messy legacy data should plan for longer.

1. 1

   Weeks 1–2

   Data extraction and mapping from existing spreadsheets or the outgoing administrator. This is where most of the real work sits, and where legacy inconsistencies surface.

2. 2

   Weeks 2–4

   Installation on your infrastructure, member ledger load, opening balance reconciliation, and interest history validation against prior declarations.

3. 3

   Month 2

   Parallel run. The old process and the new one produce the same period, and the outputs get compared line by line before anything is switched off.

4. 4

   Ongoing

   Archive the legacy files — they remain part of your compliance record and should not be deleted — and move filings, statements and minutes onto the platform.

Start with the free data assessment

Nobody can quote a migration honestly without seeing the data first. The assessment is free and independent of any purchase.

1. 1You send us a sample of what you hold today — a spreadsheet export, or a report from the outgoing administrator.
2. 2We look at the shape of it: how many members, how many years, where the gaps and inconsistencies are.
3. 3You get the scope, the timeline and the quote in writing, before you commit to anything.

Questions we get asked

How long does a migration take?

A standard implementation runs to roughly 30 days, covering data migration, installation and training. Complex multi-location implementations may take 45–60 days. Trusts carrying years of inconsistent spreadsheet history should plan for longer — the extraction and reconciliation is the variable, not the software. The timeline is confirmed in writing after the free data assessment.

We use Raycomputech, Vista or C-Quel. Can we migrate?

Yes. We have migrated clients from Raycomputech, Vista, PROMIS, C-Quel and a range of Excel-based setups. Migration is a professional service, scoped and quoted after a free data assessment where we confirm scope and timeline before you commit.

Is the migration free?

No. The data assessment that precedes it is free and carries no obligation, but the migration itself is a paid professional service. We scope and quote it once we have seen your data, because an estimate given before that is a guess.

What happens to our legacy files?

They are archived, not deleted. Legacy files remain part of your compliance record. Once the parallel run has matched old and new outputs line by line, filings, statements and minutes move onto the platform and the old files are retained as history.

If we ever surrender exemption, can we take our data with us?

Yes, and because the deployment is on-premise it never left your servers to begin with. Member ledgers, contribution history and statutory filings export to Excel and PDF at any point.