A B2C migration must respect the dependency order of the Communications data model. Identity and customer records are established first, followed by the Consumer Account and its Billing and Service Account hierarchy. Subscriptions then represent the continuing service relationship, while Assets are loaded after the account and service context exists so that installed products can be associated correctly and later participate in lifecycle operations. The recommended configuration follows the native Communications Cloud responsibility boundary: catalog and CPQ determine the commercial request, while Order Management, OmniStudio, or the relevant platform service performs the downstream processing required by the use case.
Loading downstream records before their parent or reference records creates broken relationships and complicates reconciliation. The sequence therefore follows parent-before-child dependencies rather than simply loading objects in any convenient order. Avoiding duplicate logic is important because repeated rules across catalog, integration, and orchestration layers quickly become inconsistent as products evolve. The selected approach keeps the authoritative data in the correct object model, supports later lifecycle operations, and minimizes additional processing or manual intervention. It should be implemented declaratively wherever the platform feature can express the requirement, with customization reserved only for behavior that genuinely falls outside the supported framework.
Study Guide Reference:Communications data model; Consumer Accounts; Billing Accounts; Service Accounts; Subscriptions; Assets; migration sequencing.