Skip to content

A decision to migrate from Oracle BRM is usually made in finance or procurement. The work lands on the billing team, and the part that decides success isn't installing the new platform. It's proving, line by line, that the new system produces the same balances and bills BRM did.

We build OpenBRM, an open source billing platform, and we also provide Oracle BRM consulting, so we see these projects from both sides. This checklist applies whichever platform you move to. Where OpenBRM fits, and where it doesn't, is covered near the end.

Quick summary

  • Data, not software, sets the timeline. Extracting, mapping and reconciling accounts, balances and open items takes longer than configuring the new system.
  • Inventory customisations first. Custom opcodes, policy changes and extended storable classes are where hidden billing logic lives.
  • Never cut over without a parallel run. Bill the same customers in both systems for one or two cycles and explain every difference.

Before you start: three decisions

  • Why you're moving. Cost, upgrade effort, skills or fit. The reason sets what "done" means, and stops the project turning into a redesign of every price plan.
  • Your support deadline. Oracle gives Premier Support for five years from a release's general availability, then optional Extended Support for three more. Check where your release sits in Oracle's Lifetime Support Policy; BRM 7.5 reached the end of Extended Support in November 2021. A support end date is the real deadline for many migrations.
  • Big bang or phased. Moving everyone at once is simpler to run but riskier. Moving one brand, product line or segment first is safer, at the cost of running two systems for longer.

What has to move from Oracle BRM

BRM stores everything as objects built from storable classes, and most deployments have customised some of them. Map each one to its home in the target system before you write any extraction code.

DataWhere it lives in BRMWhat to check
Accounts and contacts/account, with hierarchy and contact detailsParent–child hierarchies, closed accounts, duplicates
Bill units and cycles/billinfoBilling day of month, accounting type (open item or balance forward)
Balances/balance_group; in ECE too, if you charge in real timeCurrency and non-currency balances, bucket expiry dates
Bills and A/R items/bill and /itemOpen, disputed and partly paid items
Usage/event subclasses (the event_t tables)Unbilled usage for the current cycle; how much history you need
Products and price plansPricing Design Center (PDC)Discounts, proration rules, tax codes, bundles
Payment methodsPayment info objects linked to bill unitsCard tokens and debit mandates: who holds them, and can they move?
Custom dataCustom or extended storable classesWhat each custom field is for, and who still uses it

The 10-step Oracle BRM migration checklist

  1. Agree scope and sign-off. List the brands, products, customer types and countries in scope. Name who signs off reconciliation: billing, finance and customer care.
  2. Inventory every customisation. Custom opcodes, policy changes, extended storable classes, custom invoice templates and reports. For each, decide: rebuild, replace with configuration, or retire.
  3. Choose an extraction route. SQL against the BRM schema is fastest for bulk data. The PCM API and opcodes respect BRM's business logic. BRM REST Services Manager exposes TM Forum Open APIs for accounts, bills, payments, payment methods, prepaid balances and usage (TMF666, 678, 676, 670, 654 and 635), and BRM 15.2 adds TMF637 for product inventory. They suit smaller, incremental pulls; the exact set varies by release, so check your version's documentation.
  4. Map price plans before data. Rebuild each PDC plan in the new catalogue and rate a sample of real events through both. A plan that rates differently will make every bill differ.
  5. Decide what history moves. Usually open balances, unbilled usage for the current cycle and open items. Archive older rated events in a reporting store for disputes and audits.
  6. Plan balances and open items. If you use ECE, balances are written back to the BRM database through Rated Event Loader, so freeze charging before you take the final snapshot. Carry prepaid buckets over with their expiry dates.
  7. Rebuild integrations. CRM, provisioning, payment gateways, mediation, general ledger and reporting. List every system that calls BRM today, and how: SOAP, REST, PCM or files.
  8. Test with production-shaped data. A copy of real accounts and a full day of real CDRs. Include boundary cases: mid-cycle plan changes, refunds, suspensions, rejected and duplicate records.
  9. Run in parallel and reconcile. Bill the same customers in both systems for one or two cycles. Compare rated events, invoice totals, taxes and closing balances, and explain every material difference.
  10. Cut over, then decommission. Agree a data freeze, a rollback point and a support rota. After go-live, keep BRM read-only until the first new-system bill run is reconciled and the data you need is archived.

How to validate migrated billing data

Reconciliation is what proves the migration. For the parallel-run cycles, compare these for every account, not just in total:

  • Balances: opening and closing balances, by currency and by non-currency bucket.
  • Invoices: invoice totals and each invoice line, including discounts and prorated charges.
  • Taxes: tax amounts per line and per jurisdiction.
  • Payments: how payments, refunds and adjustments are allocated to open items.
  • Usage: unbilled usage for the cycle in flight, so nothing is billed twice or missed.
  • Dates: subscription start and end dates, and each account's next billing date.

Agree acceptable differences with finance before the first run, such as rounding, and treat anything else as a defect to explain.

Common Oracle BRM migration mistakes

  • Treating customisations as configuration. A policy opcode changed years ago may be the only place a regional tax rule or a loyalty discount exists.
  • Reconciling totals, not lines. Matching invoice totals can hide offsetting errors. Compare at the event and item level too.
  • Forgetting payment tokens. Card tokens usually belong to the payment gateway, not BRM. Check early whether they can be moved or customers must re-register.
  • Stopping support too early. Oracle's support policies require every licence in a licence set to stay on the same support level, and lapsed support can cost a reinstatement fee to restore. Plan the support end date with the cutover date, not before it.

For a cost view of the decision itself, see open source vs. proprietary BSS: total cost of ownership. If TM Forum APIs are part of your target architecture, see what TMF Open API means for a billing platform.

Migrating from Oracle BRM to OpenBRM

OpenBRM is an open source telecom billing and BSS platform on Java and PostgreSQL, with no licence or per-subscriber fee. If you're still choosing a target, our OpenBRM vs Oracle BRM comparison sets the two side by side. Here's how BRM data lands in OpenBRM:

Oracle BRMOpenBRM
Accounts and bill unitsCustomers and billing accounts, with billing cycles
PDC products and price plansProducts, plans and pricing
Purchased productsOrders and subscriptions
Usage events (Pipeline Manager or ECE)Usage rated by OpenRate, in batch or real time
Bills and itemsInvoices and invoice lines
Payments and payment methodsPayments and payment methods
Custom storable class fieldsMeta fields and plug-ins

Data can be loaded through OpenBRM's SOAP API, which covers customers, products, invoices, payments and mediation. Custom behaviour goes into plug-ins and meta fields rather than a modified core, so it carries forward when you upgrade.

Where it isn't the right target: OpenRate handles around 1,000 CDRs a second in our tests. Throughput depends on hardware, CDR format, rating complexity and database load, so treat that as a guide and test with your own records. It's plenty for most MVNOs, ISPs and regional operators, but not tier-1 real-time converged charging. If that's what you need, our guide to Oracle BRM alternatives covers the commercial options.

Our team knows both platforms, so we can scope a migration from your actual BRM schema and customisations. Tell us what you run today, or download OpenBRM and load a sample of your own accounts.

Disclaimer: Oracle BRM details are summarised from Oracle's public documentation and support policies, and vary by release and contract. Confirm support dates and licence terms with Oracle before you plan a cutover. Last reviewed: November 2026.

Oracle BRM migration: common questions

It depends on the number of price plans, customisations and integrations, not on subscriber count alone. Extracting, mapping and reconciling data usually takes longer than configuring the new system. Plan for at least one or two billing cycles of parallel running before cutover.

Usually not. Most operators move open balances, unbilled usage for the current cycle and open invoices, and archive older rated events in a reporting store for disputes, audits and regulatory retention.

Yes. Moving one brand, product line or customer segment first lowers risk. The cost is running two billing systems, and the integrations to both, for longer.

That depends on your contract. Oracle's support policies require all licences in a licence set to stay on the same support level, so dropping support for part of an estate usually means terminating those licences. Archive the data you need, and check the terms with Oracle or a licensing adviser, before you stop paying support.

For MVNOs, ISPs, VoIP providers and regional operators, often yes: OpenBRM covers rating, subscriptions, invoicing, payments, CRM and inventory with no licence fee. It is not built for tier-1 real-time converged charging, and its APIs are mapped to TM Forum entities rather than TMF-certified.

Sources

Planning your migration from Oracle BRM?

Try OpenBRM with your own accounts, products and billing data, or ask our team to assess your BRM customisations, integrations and migration scope.

Open source and self-hostable — no licence cost.