Technology

Migrating From Legacy Migration Software: Data Mapping and Cutover Plan

Most migration plans test whether the data arrived. The better test is whether the new system can still hold everything the Code requires a client file to contain.

LodgeHQ

Compliance Team

•14 November 2026•7 min read

Software migrations are usually planned as a data problem: export from the old system, import into the new one, check the counts match.

For a migration practice there is a better framing. Changing systems is a retention event. The Code requires you to take all reasonable steps to ensure a client file is kept for seven years after the last action on it, and the file has a defined content. A cutover that loses part of that content has not just inconvenienced you — it has broken an obligation that runs for years afterwards.

Which means the acceptance test for the new system is not "did the data arrive". It is "can this system hold a compliant client file".

Use section 56(2) as the specification

Before evaluating any system, write down what a client file must contain under the Code of Conduct:

  • a copy of the client's application or other immigration matter
  • copies of all service agreements and any variations
  • copies of all written communications, including electronic ones, between you and the client, and between you and anyone else to the extent they relate to the client
  • contemporaneous written records of oral communications with the client
  • records of material oral communications with third parties about the client
  • copies of all invoices and receipts
  • copies of the client's personal documents
  • evidence of the safe return of any original documents

Now check each against the candidate system. Most handle documents, matters and invoices well. The three that expose gaps are records of third-party calls, evidence of returned originals, and the "any variations" limb of the agreement requirement — a system that stores only the current agreement has lost the history you may need to show which version was in force when.

If the new system cannot hold something on that list, you need to know before the cutover, not after. Our comparison of software for registered migration agents covers what to look for.

What is actually in the legacy system

The inventory is longer than the export.

Structured data — clients, matters, deadlines, invoices, payments. This is what exports cleanly and what everyone plans for.

Documents — usually the bulk by volume, and where the traps are: filenames that carry meaning, folder structures that encode status, and version relationships that exist only as naming conventions.

Notes — frequently the most valuable and least portable. Note history with its original timestamps is what makes a record contemporaneous, and an export that stamps everything with the migration date has destroyed exactly the property that mattered.

Correspondence — often not in the system at all, but in mailboxes. Deciding whether it comes across is a decision about whether the file is complete.

Configuration — templates, checklists, permissions, deadline rules. Rebuilding these is usually the largest hidden cost.

The things nobody mentions — the spreadsheet the bookkeeper maintains, the shared calendar, the folder on someone's desktop.

Timestamps and attribution are the migration's real risk

Two properties matter more than any field mapping.

When a record was created. Section 55 requires records of oral communications with clients to be contemporaneous. A note migrated with today's date is no longer evidence of anything about when the conversation was recorded. Insist that original creation timestamps survive; where a system cannot preserve them, preserve them in the note body rather than losing them.

Who created it. Attribution is what lets you answer who did what on a matter, which section 24's responsibility for others' work and section 12's responsible-agent definition both depend on. An import that attributes every record to "system" or to whoever ran it has flattened the practice's history.

Cleansing: less than you think

The temptation on migration is to clean everything. Resist most of it.

Worth doing: de-duplicating clients, because duplicates break conflict checking and section 34 depends on it; and reconciling client money, because you should never migrate a ledger you cannot prove.

Worth leaving alone: historical data that is imperfect but true. Correcting a closed matter's record is editing a file you must retain, and the corrected version is not the record of what happened.

Worth deciding deliberately: what does not come across. Old matters past every retention period may be candidates for disposal rather than migration — and Australian Privacy Principle 11, where the Privacy Act applies, expects personal information to be destroyed or de-identified once it is no longer needed and no law requires retention. A migration is a natural moment to run that disposal, with a record of what was disposed of. Our guide to file retention covers the schedule.

The vendor is a third person

Two provisions bear on the transfer itself.

Section 35 prohibits disclosing personal information about a client or former client to a third person without written consent, except as required by law. A vendor performing a migration handles the entirety of your client data. Where the APPs apply, the Act's rules on use and disclosure and on offshore arrangements apply too.

Section 53 requires documents belonging or relating to a client to be kept securely while in the possession of you or anyone in your business. In practice that means: a written agreement with the vendor covering confidentiality and what happens to the data afterwards, knowing where the data is processed and stored, encrypted transfer, and — the one most often forgotten — confirmed destruction of the working copies once the migration is signed off. Extract files sitting on a consultant's laptop six months later are a breach waiting to be discovered.

Rehearse, then cut over

Rehearsal is the whole plan. Migrate a representative sample — twenty matters spanning a simple case, a complex sponsored case, a family unit on one file, a closed matter, and one with a messy history. Then check each against section 56(2), item by item, not against a record count.

Reconcile things that must reconcile. Client money, invoice totals, open matter counts, deadlines. A number that does not match is a finding, not a rounding difference.

Avoid a long parallel run. Running both systems "for a while" is intuitive and produces the worst outcome available: a period where the client file is split across two systems and neither is complete. If you must overlap, make one system authoritative and the other read-only from a fixed date, and write that date down.

Cut over when it is quiet. Not at end of month, not before a fee change, and not when someone is on leave.

Keep the old system readable. Not as a rollback plan — a genuine rollback is rarely possible once work has been done in the new system — but as a reference for at least a full cycle. And do not decommission it until you have restored something from the new system's backup.

The migration test

  • Can the new system hold every item in section 56(2)?
  • Do note timestamps survive, or become the migration date?
  • Does attribution survive?
  • Does the agreement history, including variations, come across?
  • Does email correspondence reach the file?
  • Is client money reconciled on both sides?
  • Is there a written confidentiality agreement with the vendor, and a destruction step for working copies?
  • Which system is authoritative on which date?

Where a system helps

The reason migrations are painful is usually that the practice was never in one system to begin with. Exporting from a case management tool is straightforward; assembling a complete client file from a case management tool plus three mailboxes plus a shared drive plus a spreadsheet is a project.

The upside is that a migration done properly ends that fragmentation. It is the one moment when consolidating is easier than not, because you are moving everything anyway.

LodgeHQ holds matters, documents, correspondence, notes and billing in one place, with attribution and timestamps preserved. Our guides to software for registered agents and AI tools cover what to evaluate before you commit.

Verify before you rely on it

Vendor export capabilities vary and marketing claims are not a specification. Ask for a sample export before signing anything, and test the import against the section 56(2) list rather than a record count.

This is general information for migration practices, not legal or IT advice. Where a vendor will process client data offshore, or where you plan to dispose of records as part of the migration, get advice before proceeding.

Tags:Software MigrationData MigrationRecord KeepingCase ManagementImplementation