This gap analysis is part of recovery loops: five questions for introducers. The worked import example shows a complete loop of three runs. This page sets that ideal against what a company that migrated years ago usually still has, so you can predict the shortfall and say so plainly.
The evidence a review expects for each loop
A reviewer replaying a loop needs six kinds of record. The first and last frame the loop; the four in between are the loop itself.
| Evidence | Reviewer's question it answers | If absent, the reviewer concludes |
|---|---|---|
| Control | What was the target? | Nothing can be called short or over |
| Failed-run logs | How far did each attempt miss? | Only a success is visible |
| Diagnosis notes | Why did it miss? | Retries look random |
| Fix records | What changed before the retry, and who changed it? | Repair and luck look the same |
| Authority record | Was that person allowed to change it? | Controls may have been bypassed |
| Signed final check | Did a named person confirm the pass? | The end point is unverified |
What usually survives, and what usually does not
The pattern below is a typical shape, not a measurement. It is what a reviewer should expect at a mid-sized company that finished an ERP migration two or more years ago without planning to keep the trail.
| Evidence | Usually kept | Usually missing | Why it goes missing |
|---|---|---|---|
| Control | Legacy aging report or trial balance at cutover | Rarely missing | Auditors want it |
| Failed-run logs | The final successful run | Earlier failed runs | Tool purges history on a schedule |
| Diagnosis notes | Scattered emails | A note tied to each failed run | Analysts fix and rerun without writing |
| Fix records | The final mapping | Earlier mapping versions and the date each changed | Files saved over |
| Authority record | The cutover plan | Who approved each master data change | Access was granted informally under deadline |
| Signed final check | A final balance in the ERP | A bucket-by-bucket comparison with a named approver | "Looks fine" in an email |
The failed-run row is the one to ask about first, because the loss is often automatic. Microsoft's documentation for Dynamics 365 Finance and Operations says each import job run records succeeded and failed counts per entity and an execution log, and that by default job history and related staging data older than 90 days are deleted. Other products have their own rules; ask rather than assume.
How each gap breaks the loop
Using the three-run example from the workflow page:
- Failed runs purged. Runs 1 and 2 disappear. The archive shows one successful import, with no failure to learn from.
- Fix not recorded. The change between runs 2 and 3, reversing the sign on credit memos, leaves no trace. Run 3 looks like luck. Worse, a reviewer cannot rule out that someone forced the balance with an adjusting entry instead.
- No authority record. Nobody can say who created the 31 missing customers or whether they were allowed to. The loop may have broken the company's own controls.
- Vague final check. Without a bucket comparison and a named approver, the loop has no verified end.
Research on agents shows why the diagnosis gap hurts most. The Reflexion paper describes agents that keep written reflections on failed attempts in a memory buffer and use them on the next try. Without the reflection, a sequence of attempts is just repetition, and the same is true of a company whose analysts never wrote down why a run failed.
| Gap | Run it erases in the example | Where the evidence may still be | Metadata question |
|---|---|---|---|
| Tool purged job history | Runs 1 and 2 | Exported error files, project shared drive | "Were import error reports saved outside the tool?" |
| Fix not recorded | The change between runs 2 and 3 | Change tickets, mapping version history | "Were mapping changes logged during the cutover?" |
| No permission record | Who loaded 31 customers | Access review, cutover RACI | "Who signed the cutover plan, and is it kept?" |
| No final check | Run 3 sign-off | Reconciliation workbook, controller email | "Is there a signed reconciliation for each migrated balance?" |
Describing the gap honestly in an introduction
Name what the contact confirmed, what is probably missing and who can check. Three Illustrative examples:
| Situation | Honest wording |
|---|---|
| Tool purged, files kept | "The controller says the import tool no longer shows failed runs, but error reports were emailed to a project mailbox that IT archived. The CIO can confirm what the archive holds." |
| Fixes undocumented | "Two ERP migrations since 2019 with signed reconciliations. Mapping changes between attempts were not logged, so fixes may be hard to trace." |
| Implementer holds the files | "The implementation partner ran the loads and kept the working files. Whether the company can obtain them depends on the engagement contract." |
Avoid estimating completeness, calling a gap minor before anyone has looked, or suggesting the review will find a workaround. Vendors such as Appen market agent data built on failure-mode taxonomies and verifiers, which shows buyers care about failures. It does not show that any particular company's partial records are wanted.
Where missing evidence sometimes turns up
Some gaps close when the right place is checked. Backups and restored systems may hold old import staging tables; the page on ransomware-restored records explains why gaps in restored data should be described honestly. Process mining tools may have captured event logs from the cutover period. If an agency or implementer did the work, the guide on separating a firm's own operating records from client-owned work helps settle who holds what. In a sale or wind-down, an assignee may hold the systems as estate assets; see ABC assignee intangible asset recovery. The controller who signed the cutover usually knows where the reconciliation workbooks went.
The company still needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The review packet contents list shows what the company would assemble later. More record families are in data types.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If you can describe a client's migration records and their gaps in three honest sentences, register as a partner, check who qualifies, and read the program terms before introducing the CFO or CIO.