Six rows in. Six rows out. Five still need a decision.
A fictional acceptance packet, generated by the Migration Acceptance Kit.
Free evaluation sample · actual tool output · fictional data
A client migration has reached sign-off. Both exports contain six rows. That sounds reassuring until you compare the keys and values. This example shows the evidence you can hand to the person making the acceptance decision.
Open the complete sample report
No account, email address or upload. The report is a self-contained HTML file you can save and inspect offline. Publication adds a security policy; the generated report content is unchanged.
What the six rows actually say
| Key | Result | Decision to investigate |
|---|---|---|
| 101 | Matched | $10.00 and 1,000 cents agree after the declared conversion. |
| 102 | Missing | The source row has no target row and no declared rejection. |
| 103 | Changed | $30.00 became 3,200 cents. That is a different value. |
| 104 | Rejected but present | The review said to exclude this row. It still arrived. |
| 105 | Unverified | Both balances are blank. This example treats that as unknown. |
| 106 | Ambiguous target | Two target rows share this key. Neither is chosen silently. |
The source accounts for one row in each of these six categories. The target accounts for four attributable rows and two duplicate-key rows. Both totals equal six. The duplicate finding is evidence about the same key on the other side, not another source row.
The run exits with code 1 under --strict. A report was produced, but this comparison is not clean. Equal row counts did not make it safe to accept.
Inspect the evidence, not just this explanation
- Source CSV and target CSV: six fictional rows each.
- Declared rejection and this example’s mapping: the decisions the comparison was told to apply.
- Findings CSV: the fix list with source/target side, bucket, key, line and detail.
- Report JSON: input fingerprints, complete accounting and a reproducible result hash.
- Download the whole evaluation packet, including an interpretation note. This contains sample data and outputs; the paid tool’s source is not included.
Result content hash: d6e0d47a686e6ad49102aa0338286a66162844dd26ed756c1f44b6542e9c145f
Where the review still needs you
This example compares keys and one balance field. It does not inspect a live database, prove that an export is complete, check every business rule or approve a migration. The exclusion and blank-value policy are fictional choices—not recommendations for your data.
Before accepting real work, agree the scope and exceptions, investigate findings, rerun the comparison after changes, and keep the unresolved scope visible in the sign-off. The complete free acceptance checklist explains that process.
Use the kit on your own migration
The paid kit supplies the Python tool, tests, procedure and sign-off template. It runs locally with the Python standard library. You prepare the exports and declare the mapping; no database credentials or customer data are uploaded to us.
Single-organisation licence
US$240
One company, migrating its own data.
- unlimited migrations for that organisation, forever
- any number of machines, laptops, servers and CI runners
- full source, modifiable, no licence key and no expiry
- the reports it produces are yours outright
Consultancy licence
US$600
An agency or consultancy migrating data for clients.
- everything in the single-organisation licence
- use on paid client engagements, on client data
- hand the reports, findings and sign-off memos to your clients
- clients receive the outputs; the kit itself stays with you
One payment, perpetual licence, no automatic renewal. Consultancy buyers can use the kit on paid client work and hand clients the outputs; the kit’s source stays with the licensee. Read the complete licence and 30-day refund terms and product and delivery details before deciding.
Questions about purchase or access: hello@toledotechnologies.com. The existing licence’s contact and rights are unchanged.
Made by Toledo Technologies. Explanation prepared with AI assistance; sample output generated and checked with the shipped tool.