Map meanings before column names
Two systems can both have a field called “delivered” and mean different things. One may describe the carrier’s delivery to the property; another may mean staff handed the parcel to its recipient. Copying the word without checking its meaning can make a waiting parcel disappear from the operational queue.
Create a short mapping worksheet before any authorized transfer or manual recreation. For every source field, write its meaning, the supported destination, any transformation, how uncertainty is represented and who verifies the result. A destination that cannot preserve essential meaning is a question to resolve, not a blank to fill creatively.
Give identifiers the most conservative treatment
Keep the original source record reference wherever the approved workflow permits, or in a controlled cross-reference. Treat carrier tracking references as identifiers, not quantities. Check that leading zeros, long digit strings and meaningful characters survive the chosen transfer method. If a spreadsheet is involved, verify it has not rounded a value or converted it into a date.
Keep a cleaned comparison value separate from the original evidence when possible. Removing spaces may help identify a possible match, but it should not silently rewrite what the original source contained. An internal reference should identify a record; it should not contain unnecessary personal information.
- Retain building context where unit numbers repeat across sites.
- Distinguish a shipment reference from the identity of an individual piece.
- Record alternative identifiers without assuming they describe another parcel.
- Use a documented exception for missing identifiers instead of a shared placeholder that looks unique.
Translate status and time as separate facts
For each old status, write the action that actually occurred. “Pending return” means the parcel may still be in custody. “Notified” describes communication, not collection. A blank release timestamp does not prove the parcel is waiting, and a populated field does not prove its contents are reliable.
Separate original receipt time, collection time, source-entry time and replacement-entry time. Specify the time zone. If only a date is known, retain that limitation rather than creating an exact midnight event. When the destination cannot hold a relevant original fact, agree on an approved supporting reference.
The active-and-historical scope guide helps determine which facts are needed for current work and which belong with historical evidence.
Classify possible duplicates instead of deleting by similarity
A repeated recipient name is common. A repeated tracking reference may be a duplicate, a copied value or a reference shared across a multi-piece shipment. Start with a candidate pair and examine the actual items and source history available to you.
- Same parcel, repeated record: Confirm the match using more than a name. Identify the operational record and preserve the approved cross-reference.
- Different parcels, similar details: Retain separate identities and enough distinguishing evidence to avoid a wrong pickup.
- One parcel, conflicting facts: Keep the disagreement visible until the responsible reviewer determines what can be supported.
- Insufficient evidence: Leave the case unresolved. Similarity alone does not justify merging.
If the system has no supported merge or linked-history function, do not improvise a destructive cleanup. Ask the provider how to represent the decision while preserving required evidence.
Work through a duplicate that hides a live event
In a fictional example, two source rows carry the same tracking reference. One says “received,” while the other records a later pickup. If both describe the same physical parcel and the release evidence is verified, recreating the first row alone would reopen it incorrectly. If the pickup belongs to a second piece, merging the rows would be equally misleading.
The reviewer should record which evidence supported the decision, which source references were considered and which current identity resulted. Do not overwrite the disputed source facts simply to make the new list appear consistent.
Verify the result at record level
Compare representative difficult cases after transfer, including long identifiers, same-name recipients, non-ASCII names, multi-piece shipments, corrected entries and unknown dates. Check the rendered record, not only a successful transfer message. An equal row count cannot reveal that one parcel was duplicated while another was omitted.
The UK government’s Data Quality Framework distinguishes completeness, uniqueness, consistency and accuracy. Those general concepts help frame this review; they do not prescribe a package-software mapping or certify a product.
Continue with the physical opening baseline before the live-transaction switch. For the full sequence, return to the replacement decision guide. The worksheet and examples here are original operational suggestions, not claims of built-in TrackNest migration features.
