Migrate your Digital BSS data

Subscribers in Digital BSS carry nested properties for service type, plan assignment, status, and balance. We map these to the target platform's account or subscription object, preserving plan-to-plan mappings and flagging any inactive subscribers that should not carry over.

Service plans include rating rules, chargeable events, and bundle allowances. We extract the plan hierarchy and map it to the destination's product catalog, noting which bundle components may require manual reconfiguration in the target.

Billing accounts link subscribers to payment methods, invoicing preferences, and AR records. We map account balances and credit limits, though tax configuration must be rebuilt in the destination environment.

Call Detail Records and usage events are typically archived rather than migrated live. We flag the last-billed usage date and ensure no gap in rating when the new system goes live.

Prepaid balance buckets are critical real-time records. We export current bucket balances with timestamps and replay them into the destination OCS with a consistent balance-verification step after cutover.

The 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 the destination product or offer object, flagging any deprecated service codes.

Policy and Charging Rules Function (PCRF) rules govern QoS, data caps, and policy enforcement. These are operator-specific and require manual translation because rule syntax varies between vendor implementations.

Authentication, Authorization, and Accounting records plus Home Subscriber Server data manage device-level and subscriber-level network access. We map subscriber IMSIs and credentials, but final network provisioning must be coordinated with the target operator's core network team.

Order records for plan changes, activations, and cancellations map cleanly between BSS systems using standard order schemas. We preserve order history and status timestamps.

Historical invoices can be exported as PDFs or structured records. We map invoice line items to the destination accounting object and flag any open AR balances that must transfer before cutover.

BSS platforms frequently use custom fields for operator-specific data. We detect all custom field definitions, export their values per subscriber or account, and map them to equivalent custom fields in the destination.

Mapping between BSS records and physical or virtual network elements (e.g., MSC, GGSN, PGW identifiers) is platform-specific and not portable across BSS vendors. We do not migrate these records and recommend rebuilding network element associations in the destination.