---
title: "Revenue systems migration: CPQ, CRM and Dynamics | Rig"
description: "Revenue systems migration for Salesforce CPQ, CRM and Dynamics: map deals, quotes and contracts, keep history in your warehouse and check reports before cutover."
canonical: "https://rig.so/use-cases/revenue-systems-migration"
format: markdown
---

Hub

# When you move the revenue systems, bring the history

A revenue systems migration moves the CRM, CPQ and ERP data that sales, finance and customer success depend on, from accounts and deals to quotes, contracts and invoices. After cutover, the reporting history and the rules that read those records are what usually break, so Rig maps them before anything moves.

By [Rig](https://rig.so/about) · Last updated 20 November 2026

[Request a migration readiness check](https://rig.so/book-demo)

[Download the migration checklist](https://rig.so/downloads/migration-checklist.csv)

## At a glance

- CRM moves between Salesforce, HubSpot, Attio and Dynamics 365.
- Salesforce CPQ to Revenue Cloud, with quote and contract history kept.
- The NetSuite and Dynamics data finance reports revenue from.
- Reporting history stays queryable in your warehouse throughout.

01**Inventory**

Records, logic and owners

02**Map and rebuild**

Source to target definitions

03**Run in parallel**

Counts, totals and access

04**Accept and switch**

Sign-off and rollback plan

Each wave ends with an acceptance check. This diagram shows the delivery process.

## What counts as a revenue system

A revenue system is any system whose records end up in a pipeline, bookings or ARR report. That usually means the CRM and the quoting tool, plus the ERP or billing system finance uses to close the month.

| System | Typical move | Read next |
| --- | --- | --- |
| Salesforce, HubSpot or Attio | One CRM to another, in either direction | CRM data migration services and the pair pages |
| Dynamics 365 Sales | To or from Salesforce or HubSpot | Dynamics 365 CRM data migration |
| Salesforce CPQ | To Revenue Cloud, after end of sale | Salesforce CPQ to Revenue Cloud |
| NetSuite | To another ERP, or history into the warehouse | NetSuite data migration |
| Dynamics GP and Business Central | GP to Business Central or Dynamics 365 | Dynamics GP and Business Central pages |
| Dynamics 365 Finance and Operations | To another ERP, or a warehouse export | Dynamics 365 Finance and Operations data migration |

## Bring the history with you

The target CRM needs open deals, live contracts and recent activity. Closed deals, old quotes, stage changes and retired fields can live in your warehouse, joined to the new records by their source IDs. Reports read the warehouse, so pipeline, win rate and ARR keep their trend lines on the day you switch systems.

## Map what reads each field before you change it

Flows, validation rules, commission calculations, reports and integrations all read CRM fields, and a migration changes many of those fields at once. Rig Map traces which rules, flows and reports read each field, so the rebuild list is complete before the first load. At an education software company, Rig mapped every custom Salesforce field and what read it, which made a planned cleanup safe to run.

## Salesforce CPQ is end of sale

Salesforce no longer sells CPQ to new customers, and existing customers can keep using it, renew and get support. Salesforce has not announced an end-of-life date. The move to Revenue Cloud is an application redesign as well as a data migration, so plan the quote, contract and subscription history before the configuration work starts.

## Keep the access rules through the move

During a migration, people and AI agents query both the old data and the new. Gateway gives each person and each agent its own role, limits the rows they can see, and records every call in an audit trail. Sales teams that must stay apart, such as two sales teams after an acquisition, stay apart in the warehouse too.

## When the job is a cleanup and the CRM stays

Some revenue projects keep Salesforce and remove what nobody uses. The legacy system cleanup page and the Salesforce change page cover that work, using the same field map.

## Agree a timeline against the actual scope

The table gives a planning allowance for each phase, and the assessment turns it into a dated plan for the whole project. Large estates need several waves, and application configuration can add time.

| Phase | Initial planning allowance | Exit check |
| --- | --- | --- |
| Assessment | 3 to 5 working days | Owners, access and inventory agreed |
| Sample and mapping | 5 to 10 working days | Sample records and exceptions reviewed |
| Build and parallel validation | 2 to 6 weeks per wave | Counts, totals and permissions accepted |
| Final sync and cutover | 1 to 3 working days per wave | Business owner signs off; rollback remains available |

## Keep the evidence for each migration wave

For each wave you receive the source-to-target mappings, a reconciliation report, an exception log and a cutover checklist. The checks cover duplicates, missing relationships, deleted records, time zones and permissions as well as headline totals, and the old system stays available until the agreed retention and rollback checks pass.

Inside Rig Migrate

## Run the migration in Rig, from the systems map to cutover

Rig natively maps systems and data across your IT estate, connects source and target systems, scopes the move and maps one schema to another. The same migration workspace tracks destination preparation, rehearsals, reconciliation, sign-off and the work after cutover, so your team can review the decisions and progress in one place.

1. ### Map the IT estate
   
   Map systems, data and integration flows across the IT estate. See which reports, processes and teams depend on the systems you plan to change.
2. ### Set up the migration
   
   Create the migration in Rig and record the source, destination and work to deliver. Keep the migration tasks and progress together.
3. ### Connect and discover
   
   Connect the source and target systems, then inspect their schemas and available data. Confirm access before deciding how each object will move.
4. ### Scope the work
   
   Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.
5. ### Map schema to schema
   
   Map source objects and fields to the target schema. Preview records and review rules to copy, translate, calculate, link, look up and match owners.
6. ### Prepare the destination
   
   Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.
7. ### Rehearse the load
   
   Dry run the whole load and rehearse it in the destination environment. Review the results and resolve issues before the production cutover.
8. ### Reconcile and sign off
   
   Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.
9. ### Cut over
   
   Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.
10. ### Check after cutover
    
    Track the checks after the switch, confirm that reporting and processes work, and resolve outstanding issues before retiring the old setup.

[![Rig migration task list showing the systems map, setup, connection, scope, design, destination preparation, rehearsal, reconciliation, cutover and after-cutover stages](https://rig.so/migration-stages.png)](https://rig.so/migration-stages.png)

Migration stages and task progress in Rig. [View the full-size screenshot](https://rig.so/migration-stages.png).

### Inspect source values and target previews

The migration workbench shows source fields, target previews and the rule for each mapping. Your team can review translated values, linked records and calculated fields before signing off the mapping and rehearsing the load.

[![Rig Migrate workbench mapping a Dynamics 365 CE quote to Salesforce CPQ, with source values, target previews and translation, link and calculation rules](https://rig.so/migration-workbench.png)](https://rig.so/migration-workbench.png)

A D365 CE to Salesforce CPQ example. The workbench shows mapping decisions and migration tasks; this is not a completed cutover. [View the full-size screenshot](https://rig.so/migration-workbench.png).

### Reporting migration at Birdie

Birdie reports rebuilding sales and marketing reporting in less than a day. Its team kept Snowflake and the existing Fivetran pipelines; retirement of the Looker licence is not confirmed.

[Read the migration case study](https://rig.so/case-studies/birdie)

![Salesforce permission set object settings used when reviewing migration access](https://rig.so/salesforce-permission-set-object-settings.png)

Review source permissions before extracting CRM data.

## Common questions

What is a revenue systems migration?

It is a move of the CRM, CPQ or ERP records that feed revenue reporting, such as accounts, deals, quotes, contracts and invoices. Rig includes the reporting history and the automations that read those records in the scope.

Is Salesforce CPQ end of life?

Salesforce describes CPQ as end of sale. It no longer sells CPQ to new customers, existing customers can keep using it, and Salesforce has not announced an end-of-life date.

Do we lose pipeline history when we change CRM?

No. History that the target CRM does not need day to day stays in your warehouse, joined to the new records, so your reports keep their trend lines.

Do you replace our Salesforce or Dynamics partner?

No. Your application partner can own configuration, while Rig owns the data mapping, the history, the reporting and the checks. Rig engineers can also do the data work alongside your own admins.

How much does a migration cost?

Rig maps the work and agrees a fixed delivery price before the migration starts. Source access, custom logic, history and the number of integrations affect the scope. Platform and third-party licence costs are agreed separately.

How do you check that the data matches?

Rig compares record counts, identifiers, relationships and business totals for each wave. Every exception goes in a log, and the business owner has to accept the results before cutover.

Will both systems run during the move?

Yes, where the systems and licences allow it. Before the parallel run starts, you agree which system is the source of truth, how final changes are handled, the rollback conditions and the point at which users switch.

## Related guides and services

[Salesforce CPQ end of life? Plan a Revenue Cloud migration](https://rig.so/migrate/salesforce-cpq-to-revenue-cloud)[CRM data migration services: Salesforce, HubSpot and Dynamics](https://rig.so/services/crm-data-migration)[HubSpot to Salesforce migration](https://rig.so/migrate/hubspot-to-salesforce)[Salesforce to HubSpot migration](https://rig.so/migrate/salesforce-to-hubspot)[Attio to Salesforce migration](https://rig.so/migrate/attio-to-salesforce)[Attio to HubSpot migration](https://rig.so/migrate/attio-to-hubspot)[HubSpot to Attio migration](https://rig.so/migrate/hubspot-to-attio)[Salesforce to Attio migration](https://rig.so/migrate/salesforce-to-attio)[Dynamics 365 CRM data migration: to and from Salesforce](https://rig.so/migrate/dynamics-365-crm)[Dynamics 365 Finance and Operations data migration](https://rig.so/migrate/dynamics-365-finance-operations)[Dynamics GP end of life: plan the data migration](https://rig.so/migrate/dynamics-gp)[NetSuite data migration and reporting history](https://rig.so/migrate/netsuite)[dynamics business central](https://rig.so/dynamics-business-central)[salesforce change](https://rig.so/salesforce-change)[legacy system cleanup](https://rig.so/use-cases/legacy-system-cleanup)[crm migration checklist](https://rig.so/blog/crm-migration-checklist)[salesforce cpq to revenue cloud migration guide](https://rig.so/blog/salesforce-cpq-to-revenue-cloud-migration-guide)[rig map](https://rig.so/products/rig-map)[gateway](https://rig.so/products/gateway)[education software group](https://rig.so/case-studies/education-software-group)

## Sources and product details

Vendor information checked on 20 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.

- [Salesforce: what CPQ end of sale means](https://www.salesforce.com/sales/cpq/end-of-life/)
- [Microsoft Dynamics GP lifecycle](https://learn.microsoft.com/en-us/dynamics-gp/terms/lifecycle)

Talk to Rig

## What work do you want to improve?

Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.

[Request a migration readiness check](https://rig.so/book-demo)Use the platform with your team, or add our engineers.

---

- [This page as HTML](https://rig.so/use-cases/revenue-systems-migration)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
