For customer migration into Communications Cloud, Salesforce public documentation outlines a specific parent-child dependency order for customer-related data. The objective is to ensure that all parent records exist before loading child or dependent records (Billing Accounts, Service Accounts, Subscriptions, Assets).
(B) Business or Consumer Accounts should be loaded before Billing or Service Accounts
Accounts represent the parent customer entity. Billing Accounts and Service Accounts depend on the root customer account. Salesforce clearly emphasizes that Billing Accounts must have a parent Account, and Service Accounts must be tied to either the Billing Account or Consumer/Business Account. Therefore, loading Accounts before Billing/Service Accounts is mandatory.
(C) Premises should be loaded before Service Accounts
In Communications Cloud, Premises represent physical service locations. Service Accounts reference the PremiseId and cannot be created before the premise record exists. This dependency is frequently highlighted in Salesforce migration patterns, especially for broadband, fiber, and fixed-line providers.
Incorrect options:
A (Contracts before Accounts): Contracts depend on Accounts; Accounts must exist first.
D (Subscriptions before Accounts): Subscriptions require Accounts, Billing Accounts, and Service Accounts—therefore cannot be loaded first.
