Contacts
Every contact comes across with email, phone, lifecycle stage, owner, the original creation date and every custom property. Duplicate detection runs on email so re-imports never double up.
Move from HubSpot
Your deals, contacts and pipelines — alongside the books that fund them.
Export your HubSpot contacts, companies and deals, upload them to YionStack, and the AI-assisted Import surface maps every record into the unified CRM tables — pipelines, stages, owners and custom properties preserved. See every supported source →
File-based — you upload an export from your old system, we map it. No connection to your old account.
At a glance
crm- From
- HubSpot
- How
- Upload an export
- Records
- 7 types come across
- Steps
- 3-step migration
- Stays put
- 5 items intentionally
- Residency
- UK (europe-west2)
What lands in your business
The records you depend on, in their right places.
Companies
Company records collapse into the unified companies table. Domain, industry, revenue band, employee count and custom properties all come across, with Companies House enrichment (UK companies only) on the way in.
Deals and pipelines
Every deal lands with its pipeline, current stage, owner, amount, expected close date and full custom-property set. Pipelines and pipeline stages are recreated in YionStack with the same order and probabilities.
Pipeline definitions
HubSpot pipelines and stages come across as YionStack pipelines and pipeline stages, with stage names, order and per-stage default probability — so existing deals land in the right place automatically.
Tasks and notes
Open and completed tasks attach to the right deal or contact; freeform notes preserve their author, date and body text so the activity history is intact from day one.
Email send history
One-to-one email history attached to deals and contacts comes across as activity records. Templates and sequences re-author inside the YionStack marketing module rather than being imported as opaque blocks.
Custom properties
Every custom property maps to a YionStack custom field on the matching record type, preserving its label, data type and historical values across every contact, company and deal.
How it works
Three steps. Reversible at any point.
- 1
Export from HubSpot
From HubSpot, use Settings → Export → All data (or per-object export for contacts.csv, companies.csv, deals.csv). The Import surface auto-detects the HubSpot format and selects the right mapping template.
- 2
Review the mapping
YionStack’s AI-assisted mapper reads the column headers (including HubSpot’s underscore-prefixed property keys) and suggests where each one lands. You approve or adjust before any data is written.
- 3
Run the import
The job runs in the migration dashboard. Open deals land in the right pipeline stage immediately; closed deals preserve their close date and outcome.
What stays where it is
We are honest about scope.
A migration is not the same as a clone. The records below are intentionally out of scope — either because they belong with the system that produced them, or because their meaning changes once they live inside an operating system instead of a point-tool. You can still reference the originals while you run YionStack alongside.
- —Marketing automations and workflows — re-authored inside the YionStack marketing module so triggers can fire from CRM, accounting and projects events, not just CRM.
- —Landing pages and forms — re-built with the YionStack Builder so the public website and the lead capture share one design system and one analytics layer.
- —Email templates and sequences — re-authored inside the YionStack marketing module on top of the imported contact list, taking advantage of the unified contact record.
- —HubSpot Ads connections — re-authorised in YionStack’s marketing module under your own ad-platform credentials (Google Ads, Meta Ads, LinkedIn Ads all supported).
- —HubSpot Service Hub conversations — moves separately through the YionStack support module if you used the helpdesk side of HubSpot.
Common questions
Straight answers.
Does this work for HubSpot Free, Starter, Professional and Enterprise?
All four. The CSV export is available on every tier. Custom properties (more numerous on Professional/Enterprise) all carry across. Object-level permissions are recreated on the YionStack side using its built-in role model rather than imported as-is.
What about my workflows and sequences?
These re-author inside the YionStack marketing module and the new Operator Builder (queued under YAE-3). The reason for re-authoring rather than importing is that YionStack workflows can fire on accounting and projects events too, not only CRM — so the equivalent in YionStack is usually richer than a one-to-one copy.
Will my reports come across?
Saved reports re-author once inside YionStack’s reporting layer, where they can pull from CRM, accounting and projects in one query. The custom-property values are all present, so the report definitions are the only thing being rebuilt.
Can I keep HubSpot live while we transition?
Yes. The migration is a one-time copy by default. Your HubSpot account continues to operate normally; YionStack does not write anything back. Most teams run both for a month, agree the cutover date, then disable new HubSpot writes.
What about deal-stage history?
Every stage transition with its date is preserved on the imported deal so the historical funnel reports continue to work. New stage transitions in YionStack continue the same event log.
Ready to run your business smarter?
Join thousands of UK businesses already running on YionStack.
- No credit card
- 14-day free trial
- Cancel anytime