In Salesforce Communications Cloud, the B2C customer model follows a structured, layered hierarchy designed to support ordering, billing, service management, and asset lifecycle handling. When migrating existing B2C customers into Communications Cloud, Salesforce’s public architecture guidance specifies a top-down data dependency sequence to ensure that parent records exist before child records referencing them are inserted.
The migration sequence begins with Users, since many operational objects (orders, cases, ownership, provisioning workflows) require an active user as the record owner or last modified by. Next, Contacts are required for each B2C customer because Communications Cloud uses Contacts associated with a Consumer Account to represent the individual subscriber. Although Person Accounts are supported in some Salesforce products, Communications Cloud standard data model for B2C uses Consumer Accounts + Contacts, which aligns with option A—not C.
Once contacts are created, Consumer Accounts must be migrated so that customer identity, householding, service relationships, and billing mappings can be referenced. With accounts in place, Billing Accounts are imported next to link financial agreements, billing preferences, and invoicing relationships.
Service Accounts follow, serving as the service location or logical container for active telecom services. Only after these parent entities are established can Subscriptions be migrated, as they represent the commercial products the customer is consuming. Finally, Assets are migrated, representing the technical products or devices (routers, SIMs, set-top boxes) associated with active subscriptions and services.
Options B, C, and D omit Subscriptions, which are essential for B2C migration into Communications Cloud. Option C incorrectly uses Person Accounts, which does not match the Communications Cloud standard B2C data model.
