CRM migration
Field-level mapping, validation, and rollback between Digital BSS and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Digital BSS
Source
monday CRM
Destination
Compatibility
9 of 10
objects map 1:1 between Digital BSS and monday CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Digital BSS to Monday.com CRM is a platform-category transition from a telecom-grade BSS stack to a board-based work OS. Digital BSS tracks Subscribers, OCS buckets, PCRF rules, and tariff plans as telecom-first objects; Monday.com CRM uses Items on Boards with customizable Columns as its record model. We map Subscribers to CRM Items on a Contacts board, Service Plans to Product board Items, and Billing Account balances to custom number columns with reconciliation before cutover. Monday.com CRM does not have native OCS, PCRF, or HSS equivalents; we extract those as structured data exports for the operator's network team to load into their charging platform. Workflows, automations, and PCRF policy rules do not migrate as code; we deliver a written inventory of each for the customer's admin to rebuild as Monday automations and integrations.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Digital BSS object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Digital BSS
Subscriber
monday CRM
CRM Item (Contacts Board)
1:1Digital BSS Subscriber records carry nested service type, plan assignment, status, and balance properties. We map these to CRM Items on a Contacts board, with the subscriber MSISDN as a unique identifier column and plan assignment as a Status or Dropdown column. Balance data migrates as a Number column for display only; Monday.com has no real-time charging engine so the OCS bucket must remain live in the operator's charging platform. We preserve the subscriber status and any custom fields in additional columns.
Digital BSS
Service Plan / Tariff
monday CRM
Product Board Item
1:1Digital BSS Service Plans include rating rules, chargeable events, and bundle allowances. We extract the plan hierarchy and map it to Product board Items in Monday.com CRM with pricing columns, allowance descriptions, and bundle components stored as text or multi-select columns. Bundle codes and cross-service discount formulas do not auto-map; we generate a Plan Translation Specification that the customer's product manager reviews before activating the product catalog. Allowance-based plans (data caps, voice minutes, SMS limits) require manual configuration in Monday.com since there is no native rating engine.
Digital BSS
Billing Account
monday CRM
CRM Item (Billing Accounts Board)
1:1Billing accounts in Digital BSS link subscribers to payment methods, invoicing preferences, and AR (Accounts Receivable) records. We map account balances and credit limits to number columns on a dedicated Billing Accounts board. Tax configuration, invoicing templates, and AR workflow rules do not migrate; these must be rebuilt in the customer's accounting or billing system (often a separate ERP or billing platform for MVNOs). We flag any open AR balance requiring settlement before cutover.
Digital BSS
OCS Bucket (Prepaid Balance)
monday CRM
External Export + Reconciliation Record
lossyPrepaid balance buckets are live monetary value records and cannot be treated as standard CRM data. We export current bucket balances with timestamps from Digital BSS and present them as a reconciliation manifest for the operator's charging team to load into the destination OCS platform. Monday.com CRM has no OCS equivalent and is not the system of record for prepaid balances. The migration deliverable is the balance manifest and a verification step that confirms all bucket records are confirmed loaded before the source OCS is deactivated.
Digital BSS
Product Catalog
monday CRM
Product Board
1:1Digital BSS product catalogs define which services are offerable with relationships to plans, pricing, and bundle constraints. We extract the full catalog tree and map offerable services to Monday.com CRM Product board Items with pricing, status, and linked subscriber boards. Bundle constraints and cross-service discount rules require manual reconstruction as Monday.com formulas or integrations with a pricing engine. We deliver a Catalog Translation Map that the product manager reviews before go-live.
Digital BSS
PCRF Policy Rules
monday CRM
External Export Only
1:1PCRF (Policy and Charging Rules Function) rules govern QoS, data caps, and policy enforcement per subscriber. These use vendor-specific syntax that does not port to Monday.com CRM, which has no network policy management capability. We export the raw rule definitions as a structured manifest for the operator's network team to rebuild in the destination network element or policy controller. This is a documentation deliverable, not a data migration into Monday.com.
Digital BSS
AAA / HSS Records
monday CRM
External Export Only
1:1Authentication, Authorization, and Accounting records plus Home Subscriber Server data manage device-level and subscriber-level network access (IMSI, credentials, location). These are network-layer records with no equivalent in Monday.com CRM. We extract a subscriber IMSI and access credential manifest as an export for the network team. CRM migration does not include HSS or AAA data.
Digital BSS
Usage Records / CDRs
monday CRM
Archived Export
1:1Call Detail Records and usage events are typically archived rather than migrated live because Monday.com CRM has no rating or usage tracking engine. We capture the last-billed usage date and export a CDR archive manifest. The new OCS or billing platform handles usage rating going forward. We flag the billing cutoff date to ensure no rating gap at cutover.
Digital BSS
Orders / Subscriptions
monday CRM
CRM Item (Orders Board)
1:1Order records for plan changes, activations, and cancellations map from Digital BSS to Monday.com CRM Items on an Orders board, preserving order history and status timestamps. We map order type (activation, upgrade, cancellation, port-in) to a Status column and preserve the original timestamp as a Date column. Order-to-subscriber linking uses the MSISDN as a lookup key.
Digital BSS
Invoices
monday CRM
External Export + PDF Archive
1:1Historical invoices from Digital BSS are exported as structured records and PDF files. Invoice line items map to a reconciliation manifest rather than live CRM records, because Monday.com CRM does not have a native invoicing engine. We map open AR (Accounts Receivable) balances to the Billing Accounts board and flag any outstanding invoices requiring collection before cutover. Tax configuration must be rebuilt in the customer's accounting system.
| Digital BSS | monday CRM | Compatibility | |
|---|---|---|---|
| Subscriber | CRM Item (Contacts Board)1:1 | Fully supported | |
| Service Plan / Tariff | Product Board Item1:1 | Fully supported | |
| Billing Account | CRM Item (Billing Accounts Board)1:1 | Fully supported | |
| OCS Bucket (Prepaid Balance) | External Export + Reconciliation Recordlossy | Fully supported | |
| Product Catalog | Product Board1:1 | Mapping required | |
| PCRF Policy Rules | External Export Only1:1 | Mapping required | |
| AAA / HSS Records | External Export Only1:1 | Mapping required | |
| Usage Records / CDRs | Archived Export1:1 | Mapping required | |
| Orders / Subscriptions | CRM Item (Orders Board)1:1 | Fully supported | |
| Invoices | External Export + PDF Archive1:1 | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Digital BSS gotchas
Legacy BSS data inconsistency blocks clean migration
PCRF and HSS rule translation requires manual work
Prepaid OCS bucket cutover must be atomic
Custom product bundles do not auto-map between vendors
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and data audit
We audit Digital BSS across subscriber records, service plan hierarchy, billing account structure, OCS bucket volumes, and any PCRF or HSS record exports. We identify duplicate subscribers, inconsistent plan assignments, and open AR balances requiring resolution before migration. We pair this with a Monday.com CRM workspace assessment: board count, column types in use, automation rules, and integration points. The discovery output is a written migration scope with record counts per object and a flag list of records requiring pre-migration cleanup.
OCS balance manifest and network team coordination
We export current OCS bucket balances with timestamps and run a pre-migration reconciliation pass to identify any subscriber with a balance discrepancy between Digital BSS and the network element. We generate the balance manifest in a format compatible with the destination charging platform. This step requires coordination with the operator's network or charging team to confirm the destination OCS API or import format. We do not write bucket records into Monday.com CRM.
Monday.com board structure design
We design the Monday.com CRM board structure: a Contacts board for subscriber profiles (MSISDN, plan, status, balance display), a Products board for service plans and tariff items, a Billing Accounts board for AR records, an Orders board for subscription changes, and a Deals board for service upgrade opportunities. We define column types, status values, and any integrations (email, forms) before data import. If the customer is on Basic or Standard and needs Chart views, we flag the upgrade requirement before migration begins.
Data cleansing and field mapping
We clean subscriber records: removing test accounts, resolving duplicates by MSISDN, standardizing date formats and country codes, and consolidating plan assignment inconsistencies. We map Digital BSS fields to Monday.com column types (text to Text, dates to Date, balances to Number, plan assignments to Status or Dropdown). Custom fields from Digital BSS map to custom columns in Monday.com. Any field without a clear Monday.com equivalent goes to a Long Text column with the original label preserved.
Production migration in dependency order
We run production migration in record-dependency order: first the Products board (service plans), then Billing Accounts, then Contacts (subscribers) with plan assignments linked, then Orders, then Deals. OCS bucket manifests, PCRF rule exports, and HSS manifests run as separate data extracts delivered to the network team. Each phase emits a row-count reconciliation report. We use Monday.com's CSV import and API where available, with batch chunking for volumes over 10,000 records.
Cutover, balance verification, and automation rebuild handoff
We freeze Digital BSS writes during cutover, run a final delta migration of any records modified during the migration window, and enable Monday.com CRM as the CRM system of record. We verify the OCS balance manifest has been loaded into the destination charging platform and confirm no subscriber has a missing balance. We deliver the Automation Inventory document to the customer's admin team. We support a one-week hypercare window for reconciliation issues. Workflows, PCRF rules, and HSS records do not migrate into Monday.com; the network team handles those separately.
Platform deep dives
Digital BSS
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Digital BSS and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Digital BSS and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Digital BSS and monday CRM.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Digital BSS: Not publicly documented; varies by deployment and operator contract.
Data volume sensitivity
Digital BSS exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Digital BSS to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Digital BSS to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Digital BSS
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.