---
title: "What Rig helps you change, and what stays afterwards | Rig"
description: "Revenue systems migration, reporting systems migration, PE integrations and data context and governance: four ways in to Rig, and the layer that stays afterwards."
canonical: "https://rig.so/use-cases"
format: markdown
---

Use cases

# The useful layer should still be there after the migration

Most companies call Rig when a system has to change: a CRM, a reporting tool, a warehouse or a whole company after a deal. Each of these four ways in ends in the same place, with Rig Map and Gateway running on your warehouse.

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

## Revenue systems migration

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

CPQ, CRM and Dynamics data moves keep the quote history and the reports that use it.

[Salesforce CPQ to Revenue CloudRead](https://rig.so/migrate/salesforce-cpq-to-revenue-cloud)[CRM data migration servicesRead](https://rig.so/services/crm-data-migration)[HubSpot to SalesforceRead](https://rig.so/migrate/hubspot-to-salesforce)[Dynamics 365 CRM data migrationRead](https://rig.so/migrate/dynamics-365-crm)[Clean up legacy systemsRead](https://rig.so/use-cases/legacy-system-cleanup)

## Reporting systems migration

[Reporting systems migration](https://rig.so/use-cases/bi-migration)

For Power BI, Tableau, Qlik and SSRS, we inventory what people use, rebuild the metrics once and run old and new side by side.

[SQL Server 2016 end of lifeRead](https://rig.so/migrate/sql-server-2016-end-of-life)[Tableau to Power BIRead](https://rig.so/migrate/tableau)[Migrate off QlikViewRead](https://rig.so/migrate/qlikview)[SSRS end of lifeRead](https://rig.so/migrate/sql-server-reporting)[Tableau vs Power BIRead](https://rig.so/compare/tableau-vs-power-bi)

## PE integrations and reporting layer

[Post-merger IT and data integration](https://rig.so/use-cases/ma-systems-integration)

Each acquisition joins one group reporting layer, and each buy-and-build add-on starts from the same map.

[Rig for private equityRead](https://rig.so/for/private-equity)[Buy-and-build integrationRead](https://rig.so/use-cases/buy-and-build)[Portfolio company reportingRead](https://rig.so/use-cases/portfolio-reporting)[Case study: one reporting layer for a merged groupRead](https://rig.so/case-studies/education-software-merger)

## Data context and governance

[Data context and governance](https://rig.so/use-cases/data-context-and-governance)

Rig Map, Gateway and Ingest stay after each migration, so people and agents query the same definitions under the same rules.

[Rig MapRead](https://rig.so/products/rig-map)[GatewayRead](https://rig.so/products/gateway)[AI agent governanceRead](https://rig.so/use-cases/agent-data-governance)[Company brainRead](https://rig.so/use-cases/company-brain)[Managed data stackRead](https://rig.so/use-cases/managed-data-stack)

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=%2Fuse-cases)[Talk to Rig](https://rig.so/book-demo?offer=talk_to_rig&from=%2Fuse-cases)

---

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