Keeping Migration Exceptions Separate From Clean Asset Records
Design a migration exception queue that preserves rejected records, assigns evidence owners and prevents unresolved data from disappearing during import.
How should unresolved asset records be handled during migration?
Keep unresolved records in a controlled exception queue linked to the source extract, with a reason, owner and defined resolution condition. Migrate an approved population only when excluded records remain visible and reconciled. A successful import must account for accepted, rejected and deliberately deferred records rather than reporting only the rows that loaded.
A migration tool may reject an asset because its location code is invalid or its identifier is duplicated. The project team can often fix the import by deleting that row from the file. The software then reports success, but the organisation has lost sight of a record that may represent a real asset and a financial balance.
Give each exclusion a reason that can be resolved
Create a queue entry with the source row reference, asset identifier, issue type, affected fields and evidence needed. Distinguish technical rejection from business uncertainty. An invalid date format can be corrected from a reliable source; an unknown acquisition date needs a different decision. Avoid a single miscellaneous category that hides why records are waiting.
Assign the issue to the person able to resolve it. Facilities may confirm a location, procurement may provide a purchase line, and finance may decide treatment of a duplicate financial record. Name one coordinating owner when several departments are involved. Add a target review date without treating the date itself as authority to guess missing data.
Reconcile the queue with the migration population
Keep an immutable source reference for every record through successive file versions. For each migration attempt, count accepted, rejected, deferred and intentionally excluded rows, with reasons. Reconcile financial totals separately where the file contains values. A row-count match can conceal a duplicated high-value record and a missing low-value one.
Do not mix unresolved records into production using invented defaults merely because the software demands a field. If a temporary value is approved, make its provisional status visible and define how it will be replaced. Confirm that users and reports can distinguish the temporary record from a verified one, especially where location or custody drives operational action.
Define evidence-based closure
Close an exception only when its agreed resolution is supported and the corrected record has passed the relevant import check. Record the reviewer and resulting destination identifier. For deferred items, retain the operational arrangements that keep them under control until migration finishes. A record outside the new application should not become an asset without a responsible department.
Use a short review meeting to unblock the oldest or most consequential cases. Report movement between queue states, not just a declining total. A bulk status change to resolved without destination readback can make the project look finished while leaving the same broken records waiting in another spreadsheet.
Practical Example
Illustrative example: an import contains 500 source rows. It accepts 486, rejects eight malformed location references and defers six disputed duplicates. The team reports all three groups and assigns separate resolution owners. After location evidence is approved, eight records load successfully; the six identity disputes remain visible instead of being erased from the project totals.
Action Checklist
- 1.Create a queue reference for every rejected, deferred or deliberately excluded source row.
- 2.State the evidence needed to resolve each issue and assign an appropriate owner.
- 3.Reconcile counts and relevant values between source, accepted records and the queue.
- 4.Require destination readback before closing an imported correction.
- 5.Keep deferred assets under an explicit operational control until their records are accepted.
Resolve migration exceptions against a traceable source baseline with Fixed Asset Register Reconciliation.