Migrate from Digital BSS to Microsoft Dynamics 365 Sales

Digital BSS Subscriber records carry nested properties for service type, plan assignment, status, and balance. We map these to Microsoft Dynamics 365 Sales Contact records, preserving plan assignment as a custom field on Contact (e.g., current_plan__c, service_type__c) and status as the Contact's Status or a custom field. The subscriber MSISDN or IMSI becomes a unique identifier field for reconciliation. Where the BSS subscriber represents a household or account holder rather than an individual, we map to Account first with a primary Contact beneath.

Digital BSS Service Plans include rating rules, chargeable events, and bundle allowances that define what a subscriber can consume. We extract the plan hierarchy and map each plan to a Dynamics 365 Product2 record. Allowance formulas (voice minutes, data volume, SMS count) migrate as custom fields on Product (e.g., data_allowance_mb__c, voice_allowance_min__c). Bundle constraints and cross-service discounts require a separate translation document for the product manager to configure in Microsoft Dynamics 365 Sales or a CPQ tool because they involve conditional logic that does not port as field data alone.

Digital BSS Billing Accounts link subscribers to payment methods, invoicing preferences, and AR (accounts receivable) records. We map billing account balances and credit limits to Microsoft Dynamics 365 Sales Account records, preserving account status and credit limit in custom fields (e.g., credit_limit__c, billing_status__c). Tax configuration must be rebuilt in Dynamics 365 because tax codes are destination-specific and not portable across BSS vendors.

The Digital BSS product catalog defines which services are offerable, with relationships to plans, pricing, and bundle constraints. We extract the full catalog tree and map it to Dynamics 365 Product2 with corresponding PricebookEntry records in the standard price book. Bundle relationships with parent plans and cross-discount rules are documented in a product mapping specification for the customer's product manager to review before activating the catalog in Microsoft Dynamics 365 Sales or a connected CPQ system.

Order records for plan changes, activations, and cancellations map from Digital BSS subscriptions to Microsoft Dynamics 365 Sales Opportunity records. Order history and status timestamps preserve as Opportunity description fields or custom fields. Open orders with pending activation migrate as Opportunities in the appropriate stage, with the original plan name carried as a custom field. Closed orders migrate as historical Opportunity records with a Closed status, preserving the original order ID as a reference field.

Prepaid balance buckets are real-time OCS records carrying live monetary value. These do not map to any Microsoft Dynamics 365 Sales object because Sales Cloud has no Online Charging System. We export current bucket balances with timestamps and deliver a written balance manifest for the operator's network team to replay into the destination OCS separately from the CRM migration. Two-phase cutover on the OCS side is managed by the network team, not inside Microsoft Dynamics 365 Sales .

PCRF (Policy and Charging Rules Function) rules govern QoS, data caps, and policy enforcement. Rule syntax is vendor-specific and does not port between BSS platforms or into Microsoft Dynamics 365 Sales . We export the raw PCRF rule definitions and present them as a translation manifest for the operator's network team to rebuild in the destination PCRF or network policy platform. This work happens outside the CRM scope.

Authentication, Authorization, and Accounting (AAA) records plus Home Subscriber Server (HSS) data manage device-level and subscriber-level network access. We map subscriber IMSIs and credentials to a reference export document, but final network access configuration requires manual work by the operator's network team in the destination HSS or AAA platform. Microsoft Dynamics 365 Sales does not manage network-layer access records.

Call Detail Records (CDRs) and usage events are typically archived rather than migrated live. We flag the last-billed usage date to establish a cutover checkpoint and ensure no gap in rating when the new system goes live. Historical usage data remains in the source BSS archive or a separate data warehouse; it does not migrate into Microsoft Dynamics 365 Sales as operational records.

Historical Digital BSS invoices can be exported as PDFs or structured records. We map invoice line items to Microsoft Dynamics 365 Sales Opportunity records with custom fields for invoice number, invoice date, and total amount. Any open AR (accounts receivable) balances are flagged as Opportunity or Account records with a custom field ar_balance_outstanding__c that must transfer before cutover. Tax and regulatory fee line items cannot be migrated as tax codes and must be rebuilt in Dynamics 365 Finance or a connected accounting system.