Migrate from Digital BSS to Odoo CRM

Digital BSS Subscriber records map to Odoo CRM Contact records. We extract subscriber_id, msisdn, imsi, service_type, plan_assignment, status, and balance into Odoo custom fields (x_subscriber_id, x_msisdn, x_imsi, x_service_type, x_plan_code, x_subscriber_status). The Contact's email and phone pull from the subscriber's contact details if present. We do not map network authentication credentials (passwords, SIM keys) into Odoo because Odoo has no HSS equivalent and these must remain in the BSS or network element.

Digital BSS Service Plans map to Odoo Products. The plan name, plan code, bundle allowances (voice minutes, data volume, SMS count), and rating rules extract into Odoo product fields and product variant attributes. Cross-service bundle discounts and allowance rollover rules do not map automatically; we extract them as a bundle definition document for the customer's product manager to reconfigure in Odoo's pricelist and product bundle rules. Plan-to-product mapping is verified against the Odoo product catalog before import.

Digital BSS Billing Accounts map to Odoo CRM Company records. Account number, credit limit, AR balance, invoicing preferences, and payment method transfer to the Odoo Company (res.partner with customer=True). Tax configuration does not migrate because telecom tax rules vary by jurisdiction and must be rebuilt in Odoo's fiscal position and tax mapping. Open AR balances are flagged and reconciled before cutover.

Prepaid balance buckets are high-integrity monetary records. We export current bucket balances with timestamps and write them to a staging table in Odoo. Because Odoo does not have a native OCS wallet, we configure a custom wallet module (using Odoo's account.payment or a custom account.move journal) or use a dedicated accounting ledger to track prepaid credits. The balance is verified in Odoo before the source OCS is deactivated. We perform a two-phase cutover: shadow write with balance verification, then a brief read-only window on the source to prevent double-spending.

The Digital BSS product catalog hierarchy (services, plans, bundles, and constraints) maps to Odoo Product Categories and Product Templates. We preserve the catalog tree structure as a written mapping specification. Bundle constraints and cross-service discount formulas are extracted and presented as a reconfiguration guide for the Odoo product manager because Odoo's bundle rules (product variants, optional products, kits) handle these differently than OCS tariff formulas.

Digital BSS order records for plan activations, plan changes, and service cancellations map to Odoo Sale Orders. Order date, status, line items (plan assigned), and subscriber reference transfer. We preserve the order history timeline as closed Sale Orders so the customer has a full service-change record in Odoo. Active orders migrate as confirmed Sale Orders with their current status.

Historical invoices export as Odoo Account Invoice records (or Account Move in Odoo 17+). We map invoice number, date, line items, amounts, and AR status. Open invoices with outstanding balances are flagged for AR reconciliation before cutover. Invoice PDFs are stored as Odoo attachments linked to the corresponding invoice record. Tax configuration on invoice lines must be verified against Odoo's tax rules post-migration.

PCRF policy rules (QoS profiles, data cap enforcement, throttling policies) use vendor-specific syntax and have no Odoo CRM equivalent. We export the full PCRF rule set as a written translation manifest listing each rule's trigger, condition, action, and affected subscriber group. The operator's network team reviews and rebuilds these in the destination PCRF or network element. We do not migrate PCRF rules as code.

Authentication, Authorization, and Accounting records plus Home Subscriber Server data manage device-level and subscriber-level network access. Odoo CRM has no HSS or AAA equivalent. We extract subscriber IMSI and device identifiers as part of the Subscriber-to-Contact mapping but do not attempt to write network authentication data to Odoo. The HSS remains in the BSS or network element and is not part of this migration scope.

Mapping between BSS records and physical or virtual network elements (MSC, GGSN, PGW identifiers) is platform-specific and not portable. We do not migrate these records and recommend they remain in the network element management system or OSS/BSS integration layer.

Digital BSS custom fields for operator-specific subscriber or account data are detected during data audit, extracted per record, and mapped to equivalent Odoo custom fields (x_ prefix). We create the Odoo custom field definitions via Settings > Technical > Custom Fields before any data import. Any custom field with no Odoo equivalent is added to the custom field spec for the Odoo admin to review.

Call Detail Records and usage events are archived rather than migrated as live records. We extract the last-billed usage date and total usage summary per subscriber and write it to a custom field on the Contact record (x_last_usage_date, x_total_voice_minutes, x_total_data_mb). The full CDR archive remains in the source BSS or a data lake. No gap in rating occurs when the new OCS takes over because the balance verification step confirms bucket continuity.