A consultant has completed an implementation and needs to import order data into the Manufacturing Cloud.
Which steps must the consultant follow to import all of the relevant data?
A.
Request an extract of the data from the legacy system and import as-is without transformation. Disable irrelevant automations/rules.
B.
Provide the client with a data template file reflecting the data mapping and identify related records (that is, accounts, sales agreements). Disable irrelevant automations/rules.
C.
Provide the client with a data template file limited to required fields and identify required related records (that is, accounts, sales agreements). Disable irrelevant automations/rules.
A controlled Manufacturing Cloud migration should load only the data required by the target solution and preserve the relationships on which the imported records depend. Salesforce's Manufacturing CSV data-management capability is specifically designed to normalize information from external systems into a defined target structure, map source columns to Salesforce fields, and validate the resulting import.
For Order data, required related records must already be identifiable. An Order commonly depends on records such as Account and related commercial structures, while Order Products depend on Products and Price Book information. Salesforce migration guidance emphasizes loading records in dependency order and correctly remapping relationship identifiers so related records remain associated after migration.
A template containing only required fields minimizes unnecessary transformation, reduces validation errors, and prevents obsolete legacy information from being transferred simply because it existed in the source system. Automations or validation logic that would incorrectly interfere with controlled migration should also be identified and temporarily managed according to the deployment plan.
Importing a legacy extract “as-is” is inappropriate because source and Salesforce schemas rarely align directly. Option B is less precise because a migration template should deliberately contain the required target fields rather than unnecessary data.
Study Guide references/topics: Validate and Deploy — Data Migration; Data Templates; Data Mapping; Record Dependencies; Data Validation.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit