Migrate from Digital BSS to Zoho CRM

Digital BSS subscriber records carry service type, plan assignment, subscriber status, and contact metadata. We map these to Zoho CRM Contacts attached to Accounts. The primary contact fields (name, email, phone, address) map to standard Zoho CRM Contact fields. Subscriber status and plan assignment are preserved as custom fields or as tags on the Contact record. We do not migrate IMSI numbers, ICCID values, or network-level identifiers because Zoho CRM has no fields for these and they represent subscriber SIM data that should remain in the network layer.

Digital BSS service plans include rating rules, chargeable events, and bundle allowances. We extract the plan name, description, pricing structure, and bundle components and map them to Zoho CRM Products. Bundle allowances (voice minutes, data volumes, SMS counts) are stored as custom fields on the Product record because Zoho CRM Products represent service offerings rather than subscriber entitlements. The customer's product manager reviews the bundle component mapping before activation because allowances may need to be represented as pricing tiers or add-on bundles in Zoho rather than a single product.

Billing accounts in Digital BSS link subscribers to payment methods, invoicing preferences, and AR records. We map account balances and credit limits to Zoho CRM Account fields, with payment terms and invoicing preferences stored as custom fields. Tax configuration is platform-specific and must be rebuilt in Zoho Books or the customer's accounting tool of record; we document the source tax rules as a separate handoff artifact for the finance team.

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 each offerable product to a Zoho CRM Product record. Where Digital BSS uses a hierarchical catalog structure, we use Zoho CRM's Product Categories or build a custom module for catalog hierarchy if the customer requires it. Bundle pricing formulas with conditional discounts are documented as a pricing rule inventory for the customer's admin to implement in Zoho CRM's Quote or Order pricing rules.

Order records for plan activations, changes, and cancellations map to Zoho CRM Sales Orders attached to Accounts and Contacts. We preserve the order creation date, status, and order line items referencing the mapped Products. Cancellations migrate as Sales Orders with a Cancelled status rather than deleted records. Order history is preserved as read-only records in Zoho CRM to maintain the audit trail for the customer-facing team.

Historical invoices can be exported from Digital BSS as PDFs or structured records. We map invoice header data (invoice number, date, amount, status, AR balance) to Zoho CRM Invoice records linked to the mapped Account. Line items map to Invoice Line Items referencing the mapped Products. Open AR balances that must transfer before cutover are flagged in the reconciliation report; closed invoices with zero balance migrate as historical records. We do not migrate PDF attachments as Salesforce-style ContentDocuments unless the customer specifically requests them, because invoice PDFs significantly increase import file size.

Digital BSS frequently uses custom fields for operator-specific data such as region codes, dealer identifiers, or subscription tier metadata. We detect all custom field definitions in the Digital BSS export, export their values per subscriber or account record, and map them to equivalent custom fields in Zoho CRM created during the schema design phase. Custom field types (text, numeric, picklist, date, checkbox) are matched to Zoho CRM field types during the mapping pass.

Prepaid balance buckets are real-time monetary records in the Digital BSS Online Charging System. These carry live airtime and data credit values that cannot be represented in Zoho CRM because Zoho CRM has no monetary balance or charging schema. We export a current snapshot of bucket balances with timestamps as a written inventory document for the customer's billing team. The customer's network or billing team is responsible for coordinating with their OCS vendor to ensure bucket continuity during the CRM migration window.

Policy and Charging Rules Function rules govern QoS, data caps, and policy enforcement at the network layer. They use vendor-specific syntax that does not port between BSS platforms. We export the raw rule definitions as a translation manifest for the operator's network team to review and rebuild in the destination OCS or PCRF environment. This inventory is a scoping artifact, not a data migration deliverable.

Authentication, Authorization, and Accounting records plus Home Subscriber Server data manage device-level and subscriber-level network access. We map subscriber IMSIs and credentials in the extraction pass but do not write them to Zoho CRM because they represent network-layer access credentials. We deliver a credential inventory document for the network team to handle separately.

Call Detail Records and usage events are typically archived rather than migrated live in telecom BSS contexts. We flag the last-billed usage date from the Digital BSS export to establish a clean cutover point for the destination system's rating. CDR archives remain in the source BSS or a data lake; they do not map to Zoho CRM because Zoho CRM has no usage event or rating schema.

Mapping between BSS records and physical or virtual network elements (MSC, GGSN, PGW identifiers) is platform-specific and not portable across BSS vendors. We do not migrate these records and recommend they remain managed by the network operations team independently of the CRM layer.