Quick answer
Migrating from Upsales to HubSpot takes 3–6 weeks for most B2B teams: companies, contacts and opportunities map cleanly onto HubSpot objects, but there is no native migration path — HubSpot's Smart Transfer tool does not support Upsales — so the move runs through structured exports or the APIs. The part that needs real planning is your subscription and recurring-revenue data, which has no direct import into HubSpot. This guide covers the full object mapping, a five-step plan, and when an integration is the smarter first step.
Upsales is a strong product. A Swedish revenue platform with CRM, marketing automation and subscription tracking built for Nordic B2B, it has earned its install base — which is exactly why the teams leaving it are rarely leaving in anger.
They're leaving because their go-to-market stack has outgrown a single-market platform. This guide is the migration playbook: what maps to what, what breaks, what to decide before you export a single row, and what a realistic timeline looks like.
Why teams move from Upsales to HubSpot
Three drivers come up in nearly every Upsales migration we run:
- Marketing depth. Upsales covers marketing automation basics; teams that live on segmentation, attribution, ads integration and content need Marketing Hub's range.
- A service motion. Upsales has no real ticketing. The moment customer success becomes a funnel of its own, teams want Service Hub on the same customer record as sales and marketing.
- Ecosystem. HubSpot's App Marketplace has over 1,500 native integrations. When the rest of your stack is global, a Nordic-first CRM becomes the odd one out.
If none of these describe you, keep Upsales — it's a good tool. If two or three do, read on.
There is no native migration path — and that shapes everything
HubSpot's own migration tooling, Smart Transfer, supports 13 source apps — Pipedrive, Zoho, Dynamics 365, Salesforce, ActiveCampaign, Marketo and others. Upsales is not one of them.
That means no one-click importer, no automatic field mapping, no guided sync. An Upsales migration runs through one of three routes:
- Structured exports — CSV/Excel out of Upsales, mapped imports into HubSpot. Fine for straightforward datasets.
- API to API — scripted transfer via the Upsales and HubSpot APIs. Needed when volume, associations or activity history make flat files impractical.
- Partner-led — usually a combination of both, with the field mapping, deduplication and validation done for you.
The practical consequence: the field mapping is manual, so the mapping document is where the migration is actually won or lost.
What maps to what: Upsales → HubSpot
| Upsales | HubSpot | Watch out for |
|---|---|---|
| Companies | Companies | Org numbers land in a custom property; plan re-enrichment, since Upsales' built-in Nordic company data doesn't travel |
| Contacts | Contacts | Company relationships are rebuilt as associations — validate them after import |
| Opportunities | Deals | Build pipelines and stages in HubSpot first, then map old stages to new |
| Activities, notes, files | Calls, meetings, notes, tasks | Import with original timestamps so history reads correctly |
| Products | Products | Price lists map to the product library |
| Custom fields | Custom properties | Map deliberately — don't recreate every stale field |
| Marketing forms, events, automation | Forms, marketing events, workflows | Rebuilt in Marketing Hub, not imported |
| Subscriptions / recurring revenue | Line items + custom properties, or custom objects | No direct import — see below |
The subscription-data trap
This is the part of an Upsales migration that catches teams off guard. Upsales tracks subscriptions and recurring revenue natively; HubSpot has no direct import for historical subscription records — original start dates, renewal history and upgrade paths don't have a standard home, and HubSpot's community forums are full of teams discovering this mid-migration.
You have three workable options, and you should pick one before exporting anything:
- Line items on deals with custom recurring-revenue properties — the pragmatic default, and enough for MRR/ARR reporting.
- Custom objects (Enterprise) — a proper Subscription object with full history, renewals and associations, when recurring revenue is the business.
- Revenue Hub subscriptions for go-forward billing, with historical data preserved as reporting properties rather than live records.
The five-step migration plan
1. Audit and map. Inventory pipelines, custom fields, products, marketing assets and automation in Upsales. Write the mapping document. Decide the subscription model.
2. Clean before you export. Deduplicate companies and contacts, close or delete dead opportunities, archive fields nobody has filled in since 2023. Migrating garbage costs exactly as much as migrating gold.
3. Build HubSpot first. Pipelines, properties, lifecycle stages and core workflows should exist before a single record lands. Records imported into an unconfigured portal create cleanup work that outlives the migration.
4. Migrate and validate. Staged order: companies → contacts → deals → activities → products. Then validate record counts against Upsales and spot-check associations on real accounts.
5. Cut over and train. Switch on an agreed date, reconnect email and integrations, and train the team in week one — adoption is won or lost in the first ten days.
How long does it take, and what does it cost?
Most Upsales to HubSpot migrations take 3–6 weeks. The variables that stretch the timeline are marketing-automation volume, the number of products and custom fields, and how many integrations need reconnecting on the HubSpot side.
Superwork runs Upsales migrations as part of a fixed monthly subscription — no one-off project fee, cancellable anytime, separate from your HubSpot licence.
Migrate or integrate? An honest answer
There's a middle path some Nordic teams take: keep sales in Upsales and connect it to HubSpot for marketing. It works, and for a sales team deep in Upsales mid-contract it can be the right first step.
Go in with open eyes, though: two systems means two sources of truth, a sync to maintain, and two licences to pay. In our experience most Upsales–HubSpot integrations end up as staged migrations — the integration buys time while the marketing team proves out HubSpot, and sales follows at renewal. If that's your plan, design the integration with the migration in mind: consistent IDs, clean field mapping, no throwaway sync logic.
Considering the move? Our Upsales to HubSpot migration service covers the mapping, the build, the migration and the training — or talk to sales and we'll scope your dataset first.
Frequently asked questions
Does HubSpot have a native Upsales importer?
No. HubSpot's Smart Transfer supports 13 source apps — Pipedrive, Zoho, Dynamics 365, Salesforce and others — but not Upsales. An Upsales migration runs through structured CSV exports, the Upsales and HubSpot APIs, or a partner who combines both.
How long does an Upsales to HubSpot migration take?
Most take 3–6 weeks. The timeline depends on how much marketing automation you've built in Upsales, how many products and custom fields you use, and how many integrations need reconnecting in HubSpot.
Can I migrate my Upsales subscription and recurring-revenue data?
Not directly — HubSpot has no standard import for historical subscription records. The workable patterns are line items with recurring-revenue properties on deals, a custom Subscription object on Enterprise, or Revenue Hub subscriptions for go-forward billing with history kept as reporting properties. Decide which before migrating.
Will we lose our activity history?
No. Calls, meetings, notes and files migrate into HubSpot with their original timestamps, so account history reads correctly. The mapping work is making sure each Upsales activity type lands as the right HubSpot engagement type.
Can we keep Upsales and integrate it with HubSpot instead?
Yes — running sales in Upsales with HubSpot for marketing is a workable transition. But two systems means duplicate licences and a sync to maintain, and most of these integrations end up as staged migrations. If you go this route, design it so the eventual migration is easy.