Our Services
CRM platforms
See how a SaaS company moved off Dynamics 365 and made HubSpot the trusted home for its revenue data.

A growing SaaS business moving from Microsoft Dynamics 365 to HubSpot alongside a new cloud ERP.
Revenue figures differed across systems, and ARR, MRR, renewals, and churn lacked one source of truth.
Unboxx migrated the CRM, set revenue rules in HubSpot, and synced ERP invoices and payments through APIs.
Cleaner CRM data, trusted ARR reporting, automated renewals, and far less manual reconciliation for finance and sales.
The client sells software on subscription, and it was growing fast. At the same time it was replacing two core systems. HubSpot was taking over from Microsoft Dynamics 365 as the CRM, and a modern cloud ERP was coming in for billing. Either change alone was manageable. Both at once put revenue reporting at risk.
Revenue data differed between the connected systems, so ARR and MRR depended on which report someone opened. Finance and sales spent meetings debating figures instead of acting on them.
Deal records moved toward the ERP with little validation. Mistakes showed up later as invoice questions, and manual reconciliation made each one hard to trace back to its source.
Renewal and churn tracking depended on people remembering to act. Expansion revenue had no consistent rules. And invoice and payment data from the ERP was not visible in the CRM at all.
Unboxx treated the migration and the revenue setup as one project, so the data model was ready before the first record moved. Each card covers a different piece of that work.
Dynamics 365 records were mapped field by field and checked against the legacy system after import.
Custom objects, calculated properties, and rollups gave ARR and MRR one consistent set of rules.
Pipeline validation rules check each deal for complete, accurate data before it syncs to the ERP.
HubSpot workflows and custom coded actions now handle renewals, churn, and expansion on set rules.
A REST API and webhook integration brings ERP invoice and payment data into HubSpot records.
SQL reconciliation checks, field mappings, and SOPs keep the setup easy to audit and maintain.
Sales reps see invoice and payment status right on the HubSpot record. Before a renewal call, they already know where the account stands. Deals missing required data get caught at approval, not after they reach billing.
Finance works from one set of ARR and MRR figures, built on standardized revenue logic in HubSpot Operations Hub. When a number needs checking, the documented field mappings and SQL reconciliation show where it came from. Renewal and churn steps run on workflows. That gives the RevOps team time to improve the process instead of patching it.
The table compares six revenue areas before and after the move to HubSpot.
| Revenue Area | Before HubSpot | After HubSpot | Gain |
|---|---|---|---|
| ARR reporting | Figures differed by system | One standardized revenue logic | 96% more accurate |
| Revenue data discrepancies | Gaps traced by hand | Reconciled across systems | 93% fewer |
| Manual reconciliation | Spreadsheet matching each cycle | Automated data workflows | 89% less effort |
| Deal approvals | Little checking before sync | Validation rules before ERP sync | 91% more accurate |
| Renewal tracking | Follow-up done manually | Automated renewal workflows | 87% less effort |
| ERP billing visibility | Invoices and payments stayed in the ERP | Synced into HubSpot records | 94% better |
For a subscription business, this means leadership can plan from revenue figures it trusts. The HubSpot setup can also grow with the company without adding new reconciliation work.