Migrate from Digital BSS to HubSpot

Digital BSS subscriber records map directly to HubSpot contacts. Each subscriber's MSISDN, email, name, and status migrate as contact properties. Subscribers without an email use MSISDN as a secondary identifier stored in a custom property. Primary company association maps to HubSpot Company lookup.

Each active service instance (voice, data, SMS) associated with a subscriber merges into a single HubSpot deal representing the subscriber's service relationship. Service status, plan type, and data usage flags become deal properties. Historical services become closed deals preserving activation and termination dates.

HubSpot has no native billing account object. We create a Billing Account custom object capturing account ID, balance, payment status, billing cycle, and invoice count. The custom object links to the Contact via a lookup relationship so billing context surfaces on the subscriber record.

Digital BSS rated product entries (plan name, speed tier, data cap, voice/SMS allowances) map to HubSpot Products with SKU and list price. The service instance links to the product via a Line Item on the subscriber's deal, preserving quantity=1 and the rated profile as a custom property on the line item.

Digital BSS plan types including Prepaid, Postpaid, Hybrid, and MVNO Share and their associated rating profiles translate to a HubSpot custom pick-list field called Plan_Type__c with value-by-value mapping. Speed tier, data cap, throttling policy, and fair-use thresholds are stored as additional custom properties such as Data_Limit__c, Speed_Tier__c, and Throttling_Flag__c to preserve plan granularity.

Service address maps to Contact address properties (street, city, state, postal code, country) for field tech dispatch. For B2B subscribers with multiple service locations, the primary location maps to Contact and additional locations map as Company records with a custom field linking back to the primary contact.

RADIUS authentication logs and session state have no HubSpot equivalent. We preserve the last authentication timestamp, access status, and session count as custom fields on the Contact record for reference. Full session history is archived separately since HubSpot is not a network access management tool.

Payment method type (credit card, direct debit, carrier billing) and status migrate to a Payment Method custom object linked to the Billing Account. HubSpot's native payment integrations do not apply to telecom billing; the custom object preserves this data for reference and reconciliation.

Digital BSS provisioning tickets and service change orders map to HubSpot Tickets. Ticket subject captures the order type (activation, port-in, plan change, termination). Ticket properties store order ID, subscriber ID, service type, and request timestamp. Status maps to HubSpot ticket pipeline stages (Open, In Progress, Waiting, Resolved).

Any Digital BSS subscriber-level custom fields — referral code, marketing segment, SIM type, device model — migrate as HubSpot contact properties. We create custom fields with the appropriate type (text, number, date, pick-list) matching the source field definition. Multi-value fields (e.g., add-on packs) stored as comma-separated text.

Call detail record summaries, data usage totals, and SMS counts do not fit standard HubSpot objects. We create a Usage Summary custom object linked to the Contact, with monthly period, voice minutes used, data consumed, and SMS count. This preserves usage history for retention and upsell reporting.

Digital BSS subscriber owner or account manager resolved by email match to HubSpot users. Unmatched owners flagged before migration — your team either creates HubSpot users first or assigns records to a fallback owner. No contact lands without a HubSpot owner assigned.