← The Practice Ledger

Switching Legal Software: Migrating Off Spreadsheets Without Losing History

The fear is the record, not the features

Firms rarely stay on a spreadsheet, or an ageing system, because it serves them well. They stay because the record of years of work lives inside it, and moving that record feels like risking it. The features of the new system are almost beside the point; the question is whether the history survives the move.

That fear is reasonable, and it is exactly why the migration has to be planned as carefully as the choice of system — sometimes more.

Decide what actually has to move

Not everything in an old system is worth carrying. The useful distinction is between the record — clients, matters, issued invoices, receipts, the fiscal sequence — which must move intact, and the scaffolding — half-built drafts, abandoned notes, duplicate contacts — which is often better left behind.

Issued fiscal documents are the non-negotiable part. Their numbers, dates and amounts are a legal record; they have to arrive in the new system unchanged, not re-created with today's settings.

Retention obligations do not reset

Leaving a system does not end your duty to retain what it held. Fiscal and client records usually have to be kept for years after a matter closes, and that obligation follows the data, not the software contract.

So two questions matter before you switch: can the old system export what you are obliged to keep, in a form you can actually read later; and does the new system have a place for it. A migration that quietly drops the archive has not saved you work — it has created a compliance gap.

Move without a gap

The dangerous moment in any migration is the overlap, when some work is in the old system and some in the new and nobody is sure which is authoritative. The way through is a clear cutover: a date after which the new system is the record, with the old one kept read-only as an archive rather than run in parallel.

Numbering is the detail that catches firms out. Fiscal sequences have to continue without a gap or a collision across the cutover, or the first audit after the move becomes a forensic exercise.

How Mersal does this

Mersal imports clients and financial records from a spreadsheet, mapping columns to fields, so the move off a spreadsheet is a structured step rather than months of re-keying. Issued documents keep their own stored rates, currency and amounts, frozen — so a migrated invoice says exactly what it said before, regardless of the firm's current settings.

The three serial books number independently and without gaps, so a cutover does not fracture the fiscal sequence, and every imported record lands under the firm's own numbering with access filtered in the database. An active firm can export its data at any time, and we say plainly what a lapsed account can and cannot do — because your retention obligations outlive any software, ours included.

You are not moving software; you are moving a record you are obliged to keep. Decide what must transfer intact, cut over cleanly, and the history survives the switch.

Read on
See how Mersal keeps this on the record.

Matters, conflicts, VAT billing, sealed receipts and the docket, in one defensible system.

See a Real MatterSee pricing
On this same topic