Reconciliation report
Every record in scope, accounted for.
After each Full and Delta run, DataGrine builds a report that counts every record in scope across all your runs. It shows what arrived on the target, and names every record that did not, with the reason in words.
What it answers
The three questions before anyone says it’s done.
Did everything arrive?
Two numbers answer it. Accounted says whether every record in scope arrived or is named with a reason. Arrived says what share is on the target now, per object.
What did not, and why?
Every record that did not arrive is listed with its reason in words, such as “Excluded by your filter.”, and what to do about it. No error codes.
Can I show it to someone else?
Export it to Excel and hand it to your manager, your client or an auditor. Every record has its source id, its outcome and its reason.
The report
Accounted, arrived, and named with a reason.
Accounted
Every record in scope either arrived or is named with a reason. 100% means none is unaccounted.
Arrived
On the target now: created, updated, or already there. Counted per object: companies, contacts, tickets and knowledge base.
Named with a reason
Each record that did not arrive, in words: your filter, a setup gap, a limit of the new helpdesk, or a rollback.
The report starts with two numbers, then a line per object, how the numbers moved across runs, and the reasons, each with what to do next.
Reconciliation
Ledger-verified after Delta #3 · 25 Oct 2026, 16:40
Accounted
100%
22,950 arrived · 2,328 named with a reason (2,316 out of scope) · 0 unaccounted
Arrived
99.94%
22,950 of 22,962 in-scope records. Tickets: 12,132 created, 348 already on the target.
| Object | In scope | Arrived | Named |
|---|---|---|---|
| Companies | 1,204 | 1,204 | 0 |
| Contacts | 8,960 | 8,951 | 9 |
| Tickets | 12,480 | 12,480 | 0 |
| Knowledge base | 318 | 315 | 3 |
Across runs
- Full #299.89% arrived · 100% accounted
- Delta #399.94% arrived · 100% accounted
Why records did not arrive
- Out of scopeExcluded by your filter.Change the filter and run a Delta if it should be included.2,316
- FailedThe new helpdesk rejected the record.Fix the field named in the detail, then Retry failed.9
- FailedThe article’s category was not mapped to a place on the target.Map the category in the Knowledge base setup, then Retry failed.3
- DataGrine’s recordsAutomatic, no calls to your helpdesk
- Verified against source and targetAvailable after your first run
How it counts
Built to stand up to a second look.
Every run, one count
The report counts each source record once, across every run: Sample, Full, Delta and retries. The last outcome wins.
Your scope, not ours
It uses the filters you set and the moment each run started, so a record created after a run is not counted against it.
Per object
Companies, contacts, tickets and knowledge base articles each get their own line, so a gap in one is not hidden by the rest.
Nothing rounded up
Percentages are cut at two decimals, never rounded. 99.996% shows as 99.99%, not 100%.
Filter and export
Filter the records by object, family or reason, then export the whole report to Excel.
Open any record
The record view shows what was carried to the target, field by field, and any field that was not, with the reason.
Any run can be rolled back. The report then lists what was removed, and anything the rollback could not reverse, with the reason.
Available after your first run
Verified against source and target
After a run, DataGrine reads the records in scope from both helpdesks again and confirms that each one exists on the target. Before it starts, it shows how many API calls it will make and asks you to approve them. If a helpdesk’s rate allowance runs low, it pauses and picks up where it stopped. Nothing is changed in either helpdesk.
A record that is missing on the target keeps Accounted below 100% until you acknowledge it, for example because someone deleted it on purpose.
Where it fits
Sample, Full, Delta, then Reconciliation.
- 01
Sample
A few of your own records move into your new workspace. Keep them or roll them back.
- 02
Full
Everything else in scope moves, skipping what the sample already moved.
- 03
Delta
At cut-over, a last run moves only what was created or changed since.
- 04
Reconciliation
Built when each Full and Delta run finishes, or whenever you ask, and counting all of them.
See how a migration works, step by step, how Delta runs carry what changed up to cut-over, and how to roll back a run the report shows as rolled back.
Questions
About the reconciliation report.
When is the report built?
Automatically when a Full or Delta run finishes, and on demand at any time. It counts every run in the migration, the Sample included, so the latest report always covers the whole migration.
Does building the report use our helpdesk’s API?
The report itself does not: it is built from DataGrine’s own record of every write. Verifying against source and target does read both helpdesks, and it shows the number of API calls and asks you to approve them before it starts.
What happens to the report if we roll back a run?
Rolled-back records leave the Arrived count and are listed as “Removed from the target by a rollback.” Anything the rollback could not reverse is listed too, with the reason, because it is still on the target.
Is the report included when your team runs the migration?
Yes. You get the reconciliation report and its Excel export.
See the report on your own data.
Start with a Sample migration, then run the full migration and read the report.