Define a business-approved customer model
Separate legacy account IDs from future target identifiers. Agree roles such as sold-to and related parties, including organization-specific business rules.
Work through duplicate candidates
Review matching organizations and reference values with business owners. Treat a matching score as a suggestion, never a reason to silently merge two accounts.
Validate relationships and critical fields
Resolve broken sold-to links, missing legal names, invalid country codes and unsupported payment terms before considering source data ready for a pilot.
Obtain SAP target proof
After an approved nonproduction load, re-read created Business Partner identifiers, organization and finance attributes, and reconcile to accepted source records.
Frequently asked questions
What information should a Customer Master migration contain?
At minimum, establish business identification, legal name, address and country information, relevant customer roles, partner relationships and financial sales-area details required by the target migration object. Exact required fields differ by SAP edition and customizing.
Can the migration assistant automatically merge duplicate customers?
The current YapMigrate demo can identify local duplicate candidates, but it does not automatically merge customer records or create golden records. A steward must decide survivorship.
How can I try Customer Master migration without an SAP system?
Open the guided preparation demo, select the synthetic dataset, review six conceptual field mappings, run quality checks and download a reconciled export. No SAP credential is needed.