Clari to HubSpot
Revenue platform for forecasting, pipeline inspection, activity capture and conversation intelligence (Copilot). It sits on top of a CRM and is not a CRM itself.
Clari data can move into HubSpot, landing mainly in Revenue Hub. 0 of 5 mapped objects move directly; 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Clari
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<10k activities, 1-2 Tabs
Mostly rebuilding forecasting.
Mid migration
10k-250k activities, several Tabs
Includes history archive and sequences.
Large migration
250k+ activities, many Tabs, transcripts
Copilot extraction and hierarchy redesign.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Clari: what you need to get in, what lands in HubSpot, and what will not.
REST (Export API v4 async bulk jobs, Ingest API, Copilot REST API)
A Clari API token for the Revenue API, and a Copilot API key and password for calls. Tokens are tied to the creating user. Deactivating that user, or revoking the token, breaks integrations.
Admin access to create API tokens. Exact role names were not confirmed.
Third-party review: Ingest API 100 req/sec per token. Copilot API 10 req/sec and 100,000 requests per week. Export API has org-level concurrent job and monthly quota caps that your CSM can adjust.
Choose your route
How will you move the data?
No native connector was found.
- You need: A Clari API token for the Revenue API, and a Copilot API key and password for calls. Tokens are tied to the creating user. Deactivating that user, or revoking the token, breaks integrations.
- Permission: Admin access to create API tokens. Exact role names were not confirmed.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Forecast Tab export via POST /export/forecast/{forecastId}, as JSON or CSV, with optional historical data
- Activity export via POST /export/activity (meetings, emails sent and received, attachments)
- Async job lifecycle: poll the job status, then download the results
- Copilot /call-details returns transcripts per call, and there is no single bulk transcript endpoint
Limits: Third-party review: Ingest API 100 req/sec per token. Copilot API 10 req/sec and 100,000 requests per week. Export API has org-level concurrent job and monthly quota caps that your CSM can adjust.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Clari
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Forecast tabs (forecast, quota, adjustments) | Custom objects | partial | Export data can be archived or loaded into a custom object or reporting. HubSpot forecast tool and categories must be rebuilt. |
| Opportunities (CRM-synced) and field history | Deals | partial | Deals already live in the CRM. Clari trend history per field is exportable but has no native HubSpot home. |
| Activities (meetings, emails, attachments) | Meetings | partial | Activity export can be loaded as Meetings and Emails engagements via the HubSpot API. Attachments would need to be handled as Files. |
| Copilot calls and transcripts | Calls | partial | Call metadata can be created as Calls. Transcripts could be stored in the call record or Notes. Recordings stay in Clari or external storage. |
| Accounts and contacts | Companies | no | Clari reads these from the CRM, so the CRM remains the source of truth. |
What to expect
These are proprietary Clari calculations and are not exposed as portable objects in the documented APIs.
The Export API returns data only, not the Tab configuration.
HubSpot has no equivalent import for them, so they can only be recreated as engagements.
Configuration is not exported.
Not covered by the export APIs.
Copilot has no bulk transcript endpoint.
Clari docs say a Tab must already exist before it can be exported.
Export with includeHistorical for every quarter before the contract ends.
Create the token from a stable service account.
Page through calls and throttle requests to stay under the limits.
Run both in parallel for one quarter.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
The export API and its endpoints are backed by Clari's developer docs and third-party reviews. Object mapping to HubSpot, governance and certifications rest on category-level knowledge. No HubSpot doc covers Clari-to-HubSpot migration.
Sources
Related migrations
Frequently asked questions
How do I migrate Clari to HubSpot?
1. Inventory Forecast Tabs and get each forecastId from the tab URL. 2. Ask your CSM to confirm export quotas and any missing Tabs. 3. Create an API token from a service account, and get Copilot key and password. 4. Decide which Copilot recordings and transcripts to keep, and where.
What does not move from Clari to HubSpot?
Deal risk and AI scores, and the forecast model, Forecast Tab and role-hierarchy configuration and Native Clari activity and conversation records as Clari objects. Plan to rebuild or retire these.
How long does a Clari to HubSpot migration take?
Small (<10k activities, 1-2 Tabs): 2-4 weeks. Mid (10k-250k activities, several Tabs): 4-8 weeks. Large (250k+ activities, many Tabs, transcripts): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Clari?
A Clari API token for the Revenue API, and a Copilot API key and password for calls. Tokens are tied to the creating user. Deactivating that user, or revoking the token, breaks integrations. Admin access to create API tokens. Exact role names were not confirmed.
What compliance issues apply when moving Clari data?
Check: Call recordings may need two-party consent, Possible financial forecasting data and Sensitive information may appear in transcripts. Agree consent, retention and access rules before exporting.
Moving Clari into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner