POS Customer Data Migration

Customer contacts need identity matching, useful fields, and an explicit decision about duplicates. Purchase history and customer balances are separate requirements.

Agree the rules for shared email addresses, missing contact details, and existing destination records. Flag uncertain matches for review instead of merging people on a name alone.

• Source customer ID → retained identity crosswalk
• Name, email, and phone → supported contact fields
• Address and consent fields → separately reviewed values
• History and balances → individual data decisions

Two illustrative customers share a family email but have different names and store credit balances. Treating the email as a unique key could assign the balance to the wrong person.

Provide a representative sample through an agreed secure process after the initial assessment. We compare the available fields with the destination requirements and document the accepted treatment.

The test and handover should show expected records, actual results, unresolved exceptions, and the retailer’s approval. Inclusion is confirmed before booking.