---
title: "Revenue systems migration: posts and guides | Rig"
description: "When CPQ, CRM or Dynamics data moves, the reporting history should move with it."
canonical: "https://rig.so/blog/revenue"
format: markdown
---

[Blog](https://rig.so/blog)

# Revenue systems migration

When CPQ, CRM or Dynamics data moves, the reporting history should move with it.

[Revenue systems migration](https://rig.so/use-cases/revenue-systems-migration)

[Migration guideReporting is the bit that usually breaks in a CRM migrationInventory objects, map customers and owners, run both CRMs in parallel and cut over with a row-level check. History, activity and permissions usually slip.Read](https://rig.so/blog/crm-migration-checklist)[Migration guideRevenue Cloud can wait five minutes while you find the quote historyInventory product, price and quote data, choose Revenue Cloud or another CPQ, run both in parallel, then cut over. Check Salesforce’s current CPQ status first.Read](https://rig.so/blog/salesforce-cpq-to-revenue-cloud-migration-guide)

Talk to Rig

## Talk it through with an architect

An architect spends 30 minutes with you on your systems, your data and what you want to change.

[Book a call with an architect](https://rig.so/book-demo?offer=architect_call&from=%2Fblog%2Frevenue)

---

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