HubSpot → Clarify

Catalog plan outline

General guidance from the Afterstack catalog for HubSpot → Clarify. Not HubSpot or Clarify vendor documentation.

Migration friendliness

HubSpot 7/10 · Clarify 6/10

Speed to live

HubSpot 6/10 · Clarify 7/10

Catalog migration difficulty

HubSpot high · Clarify not set

Data to export from HubSpot

• pipeline and deal records
• custom objects
• sequences and cadences
• call and voice logs
• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: inbound, pipeline, accounts

How the catalogs differ

• Clarify is flagged for custom objects. Collapse unused fields before loading them.
• Clarify is not flagged for: call and voice logs, campaign and automation records, installed marketplace apps.
• HubSpot is flagged with an open API, which is the export path to test.
• Clarify is flagged with an open API for the load.
• HubSpot is cataloged as a fit for: Inbound-led teams that want marketing and sales in one suite.
• Clarify is cataloged as a fit for: Teams leaving Pipedrive.

Phases

1. Export

   Take HubSpot as the source of truth for this pair. Export pipeline and deal records; custom objects; sequences and cadences; call and voice logs; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: inbound, pipeline, accounts. The inbound suite that became a CRM — free to start, pricey once you grow up.

2. Map

   Load into Clarify only after the field map is written down. The AI CRM that fills the pipeline so reps do not have to. Clarify is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Clarify scores 7/10 on speed to live and 6/10 on migration friendliness. Run one sample load and one report the team already uses in HubSpot before a full cutover.

4. Cut over

   HubSpot scores 7/10 on migration friendliness and is marked high difficulty in the catalog. Keep HubSpot readable until the team is working in Clarify. HubSpot’s free CRM pulled a generation of marketers off spreadsheets. The paid Hubs are where the lock-in lives: marketing, service, commerce, and a Breeze AI layer. It is friendly on day one and a platform negotiation by year three.

HubSpot to Clarify: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not HubSpot or Clarify vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from HubSpot

The HubSpot page used for this cutover is Export your records, last updated April 2, 2026, and opened again on October 12, 2026. It is not the account-wide content export. It downloads current property values plus associations for the view you choose. Activity such as calls and notes is called out as a different job: an individual contact download, certain activity reports, or the engagements API. Export permission is required. The index pages named in the steps include appointments, calls, contacts, companies, courses, custom objects, deals, listings, marketing events, payments, and tickets. A board export exists for deals, tickets, admin-activated objects, and custom objects. By default the file contains only the properties and associations already on that view. Association columns include up to one thousand associated record IDs plus the associated record name, unless you switch a CSV to all associated records. A customize step can add every email on a contact and every domain on a company. Choosing all properties puts Record ID first and the rest of the columns in alphabetical order, with associations at the end when you asked for them. The mailed download dies after thirty days. The export log keeps historical jobs for three years and then removes them. The technical-limits section queues work beyond three jobs at once and stops a portal at three hundred jobs inside a rolling day. A CSV or XLSX past one million rows, or an XLS past 65,535 rows, arrives as more than one file. A CSV bigger than two megabytes is zipped. XLS stops at 256 columns and XLSX at 16,384. CSV is the format the article recommends when the column count would blow those caps. Clarify is not mentioned.

• HubSpot export records — checked 2026-10-12
• HubSpot import objects — checked 2026-10-12

How Clarify imports

Clarify's spreadsheet article, reopened on October 12, 2026, accepts companies, people, and deals only. Each upload is one entity, CSV, with a header row, and the file cap is 30MB. If you map a Company column, that company has to exist already or the row fails, so the company file goes first. Leave that column unmapped and the person still lands, after which Clarify tries to attach a company from the email domain. Addresses at free providers such as Gmail are skipped for that domain guess. You can create fields during the upload except Relationship fields. A Unique checkbox updates a matched record instead of inserting another one, and only non-empty cells are written, so a blank cell does not wipe a value already stored. A deal upload can set the company and the owner. It cannot attach people. Add those contacts on the deal afterward. Invalid values block the rows that contain them. The summary lets you download the failed rows. Finished imports are labeled, listed under Settings, and dropped into a new list. Enrichment later fills blanks when a person has an email or a LinkedIn handle, or a company has a domain. It does not overwrite values your file already set. The API guide, also opened that day, is explicit that it is for CRM-shaped data from anywhere, not a HubSpot button. Unique fields are email addresses on a person, domains on a company, and the name on a deal. Meetings and tasks have no unique field, so every API create inserts another one. Pass match_on to upsert. Without it, a colliding email or domain returns 400. People belong to at most one company, so company_id can be set on create. People on a deal are many-to-many, and the API rejects that association on create with a 422. The relationships endpoint is a later PATCH. Batches are atomic: one bad record rejects the batch. The guide says to start with five to ten records. One email address can belong to only one person, so a cell of comma-separated emails has to be split. Domains need the scheme and www stripped. The pricing comparison, same day, lists HubSpot among integrations next to Google, Microsoft, LinkedIn, and Zapier, and it marks CRM migration blank on Free and Starter and Talk to sales on Growth. The spreadsheet article does not say the uploader is Growth-only. Both sentences stay, because they are not the same claim. The Growth card says unlimited records and unlimited custom objects, while the comparison table on that page says 750k records and 10 objects. This cutover does not pick a winner between those two lines.

• Clarify CSV import — checked 2026-10-12
• Clarify API import guide — checked 2026-10-12
• Clarify pricing — checked 2026-10-12

Object and field mapping

• HubSpot contacts are the people file. The API matches a person on email addresses. HubSpot can include every email on the contact. Clarify stores one email on one person, so a secondary address is a second decision, not an automatic extra column.
• HubSpot companies are the company file. The API matches on domains. Strip https and www before that match. HubSpot's own import article, used here only for rollback, says Company Domain Name stops at the top-level domain.
• HubSpot deals are the deal file. The API unique field is the deal name, so two HubSpot deals that share a name collide. The spreadsheet upload will not hang people on those deals. The relationships PATCH does that after both sides exist.
• HubSpot tickets, calls, courses, appointments, listings, payments, and marketing events can be exported as their own views. None of those names appear as Clarify spreadsheet objects.
• Custom HubSpot objects export from their index. Clarify's comparison table prints object counts of 3, 5, and 10 across Free, Starter, and Growth, while the Growth card says custom objects are unlimited. Build the destination on purpose. Do not assume the schema copies.
• Association IDs in the HubSpot file are capped at one thousand per column unless the CSV asks for every associated record. Clarify's many-to-many between people and deals is a separate call, so a truncated association column becomes a truncated relationship list.
• Owners do not transfer by HubSpot user name. The spreadsheet article maps an owner by email when you point a column at Owner, and the related person or company has to exist.
• Workflows, sequences, playbooks, and calculated properties are not columns in the export-records article. The engagements API is the activity path HubSpot names. Clarify meetings and tasks inserted through the API always create, because those objects have no match key.

What will not carry over

• The activity timeline. The record export is current properties and associations. Calls and notes are a different HubSpot path.
• People attached to deals, if you stop at the spreadsheet upload. That limit is written on the Clarify article.
• A second email living on the same Clarify person. The API guide says an email address belongs to one person.
• Tickets and the other non-CRM objects in HubSpot's export menu. They have no named spreadsheet destination.
• Workflow enrollment, sequence state, and marketplace apps. They are not rows in the export-records article.
• Updates to existing HubSpot emails, meetings, notes, and tasks if you roll back through HubSpot's importer. That importer says those activities cannot be revised.
• Association labels on the way back into HubSpot, unless the portal is Professional or Enterprise. Marketing-contact status needs Marketing Hub Starter or above plus the Marketing Contacts feature.
• A one-click HubSpot migration button. The pricing page names HubSpot as an integration and sends CRM migration to sales on Growth. The articles opened here do not document a connector.

Cutover checklist

1. Confirm the HubSpot user has export permission before the first job.
2. Export contacts, companies, and deals from the All records view, as separate jobs, and turn on every email and every domain.
3. Stay inside three simultaneous jobs and three hundred jobs in a rolling day, and download before the thirty-day link dies.
4. Use CSV when the property count would pass the XLS or XLSX column caps.
5. Export tickets, calls, and custom objects only if you have a written destination. Do not mix them into the people file.
6. Pull activity through the engagements API or accept that the timeline stays in HubSpot.
7. Split Clarify uploads at 30MB, companies before any mapped company column, then people, then deals.
8. Turn on Unique for email and domain on a pilot, and confirm blank cells did not erase values.
9. Repair deal-to-person links with the relationships endpoint or by hand. Expect a 422 if you try to set that link on create.
10. Sample ten records, including a Gmail address and two deals with the same name, before the full load.
11. Keep the HubSpot portal readable. A rollback import will not revise existing emails, meetings, notes, or tasks.
12. If the pricing table's CRM migration row is the path you want, talk to Clarify sales on Growth. Do not describe the spreadsheet article as that service.

Common pitfalls

• Treating the default view export as the whole portal. It contains the columns on the view, not every property, unless you change that option.
• Losing association IDs past the one-thousand cap and then blaming Clarify for a short contact list on a deal.
• Loading deals whose names collide. The API matches deals on name, which is a worse key than HubSpot's Record ID.
• Expecting a Gmail address to create a company from its domain. The spreadsheet article skips free-provider domains.
• Quoting one Growth record cap. The card and the comparison table on the pricing page disagree, and this page will not launder that into a single number.
• Reusing an Attio Import2 write-up as if it described Clarify. Attio's HubSpot source is a different vendor's article and is not a source here.
• Using HubSpot's multi-object importer as the Clarify field map. It is cited for rollback limits only.

Related catalog pages

• Best AI-native HubSpot alternatives (2026) — Which tool, compared
• What should replace HubSpot? — Switch narrative
• Clarify product page — The AI CRM that fills the pipeline so reps do not have to.
• Clarify vs HubSpot — Head-to-head already in the catalog
• CRM & sales category — Catalog hub for this category