Rescue · Legacy system → CRM
The import ran. The result is not usable.
Partly loaded, partly not, and no reliable account of which is which.
We establish what actually transferred, what did not, and what is still recoverable from the source — then quote a fixed recovery scope against that evidence rather than against a guess.
- Profiled first
- Rules agreed up front
- Every change logged
- Counts reconciled
Price cue, ex GST
Assessment from $750
Check what is recoverable Or call 1300 652 280A written finding on what transferred, what is missing, what is recoverable and what it will take. Yours to keep, whether or not you engage us for the recovery.
- Australian managed
- Delivered remotely
- Source data never deleted
- Verification report at sign-off
What goes wrong on this route
The old system holds twenty years of customer history and there is no export button
The vendor is gone, or wants a five-figure fee to produce a data extract
A CRM has already been bought and is sitting empty because nobody can fill it
The export that was produced is a fixed-width text file nobody can read
Only one person understands what the codes in the system mean, and they are retiring
The old system has to keep running because nothing usable has come out of it yet
Why re-running the import usually makes it worse
A second pass against the same rules produces the same result on top of the first one. These are the things that have to be settled before anything is loaded again.
- Extraction feasibility established against your actual system first, because nothing else can be promised until it is
- The system's own codes, flags and abbreviations decoded, since these are meaningless once separated from the original screens
- Customer, contact and organisation separated out, which legacy systems routinely hold as one flat record
- Job and transaction history assessed for what belongs in the CRM and what belongs in an archive
- Duplicate customers accumulated over decades merged against rules you agree
- Documents and correspondence held inside the system extracted as real files with a resolvable naming scheme
- Records that are historically interesting but commercially dead identified, so you do not carry them into the new system
The proof you keep
You will know exactly what came back, class by class.
Recovery is reconciled against the original source, not against the half-loaded destination. That is the only comparison that tells you whether anything is genuinely gone.
Migration Verification Report
Legacy system to CRM recovery · Example format
| Extraction class | Source | Destination | Status |
|---|---|---|---|
| Customer records extracted | 24,118 | 24,118 | Verified |
| Customer records after agreed merge | 24,118 | 21,806 | 2,312 merged by agreed rule |
| Job & transaction history | 418,206 | 418,206 | Verified |
| Notes and correspondence | 96,884 | 96,884 | Verified |
| Documents extracted from the system | 31,442 | 31,442 | Verified |
| Screens, codes and reports documented | 142 | 142 | Documented, not migrated |
Accepted exceptions are itemised individually with a reason, never summarised as a total. Anything genuinely unrecoverable is recorded as unrecoverable.
Free · About three minutes · No sales call required
Tell us what happened. We will tell you what is recoverable.
The route is already filled in. Four steps, and an engineer reviews every answer — a failed import never receives an automated number, it receives an assessment.
Questions we get on this route
How is this different from your Access and FileMaker work?
Same extraction, different destination. Those routes end in a database or a searchable archive, which is right when the obligation is to answer questions about the past. This route ends in a CRM you will work in every day, so the data has to be reshaped into contacts, companies and deals rather than preserved as it was. If you are not sure which you need, the assessment answers it.
The vendor wants a large fee for an export. Should we pay it?
Sometimes, and the assessment will tell you which. A vendor extract is occasionally the cheapest path available and occasionally worthless — a dump with no schema, no decode and no relationships costs more to interpret than reading the underlying data directly. We establish what is obtainable and what it is actually worth before you commit to the fee.
How much history should come across?
Less than most people expect, and it is a commercial decision rather than a technical one. Contacts and companies come across in full. Job and transaction history usually splits: recent history into the CRM where people will use it, the rest into an archive that stays queryable. Carrying everything into the CRM is the most common reason a new system feels slow and cluttered from the first week.