Migrate from Digital BSS to HighLevel

Digital BSS subscriber records carrying name, MSISDN, service type, plan assignment, and status map to GoHighLevel Contacts. The subscriber MSISDN becomes the primary phone field. Subscriber status (active, suspended, terminated) maps to a custom contact field rather than a native GoHighLevel status. Subscriber IMSI and SIM card identifiers are stored in a custom field since GoHighLevel has no IMSI concept. We resolve the mapping from subscriber service type (voice, data, IPTV, IoT) to a GoHighLevel contact tag for segmentation.

Digital BSS tariff plans include rating rules, chargeable events, and bundle allowances that map partially to GoHighLevel Products. Plan name and base pricing migrate as Product name and price. Bundle allowances (voice minutes, data volume, SMS count) become custom fields on the Product record since GoHighLevel Products lack native quota tracking. Rating rules and chargeable event definitions are documented in a separate specification for the operator's product team to configure as GoHighLevel pricing tiers or add-on Products.

Digital BSS billing accounts link subscribers to payment methods, invoicing preferences, and AR records. The account holder name and billing address map to GoHighLevel Company name and address fields. Open AR balance is stored as a custom field on the Company record for reference. GoHighLevel does not include a native invoicing or accounts receivable module; invoice history migrates as PDF attachments or structured notes on the Company record, and any open balances require manual confirmation post-migration.

Digital BSS order records for plan activations, plan changes, and service cancellations map to GoHighLevel Deals. The active service plan becomes the Deal name, and the order status maps to a GoHighLevel pipeline stage. Order history timestamps are preserved as Deal notes or custom fields. GoHighLevel's pipeline model is simpler than Digital BSS's order lifecycle, so complex multi-step provisioning states are flattened to the nearest available pipeline stage.

Prepaid OCS bucket balances are monetary records that carry live airtime and data credit value. GoHighLevel has no OCS equivalent. We flag the existence of a prepaid balance on the destination Contact record using a custom field, and we produce a written OCS bucket inventory with current balances and timestamps. The operator's finance or network team must decide whether to reconcile these balances through a separate payment gateway integration, a prepaid card issuance, or manual credit offset. This is not a FlitStack AI migration scope item.

Digital BSS product catalog defines which services are offerable, with relationships to plans, pricing, and bundle constraints. We extract the catalog tree and map active service offerings to GoHighLevel Products. Bundle constraints and cross-service discount rules are documented as a catalog specification for the operator's GoHighLevel admin to rebuild as product add-ons or bundle pricing configurations. The TM Forum SID-compliant catalog hierarchy does not map natively to GoHighLevel's flat product list.

Historical Digital BSS invoices migrate as PDF exports attached to the corresponding GoHighLevel Company record via the file attachment feature. Invoice line items are not individually mapped since GoHighLevel lacks a native invoicing object. Open AR invoices with outstanding balances are flagged as a custom field on the Company record for the billing team to follow up on post-migration. We do not migrate tax configuration from Digital BSS to GoHighLevel.

PCRF policy rules govern QoS, data caps, and policy enforcement in the telecom network. GoHighLevel has no PCRF or network policy equivalent. We do not migrate these records. We extract the raw PCRF rule definitions and deliver them as a written translation manifest for the operator's network team to evaluate whether equivalent rules can be configured in the destination network infrastructure or whether the policy enforcement model changes post-migration.