Switching · From HubSpot

Map the real HubSpot setup before deciding what should move.

A responsible move starts with the HubSpot objects, properties, histories, workflows, forms and connections the business actually uses. Current export access, destination compatibility, service differences and migration scope must be verified before a cutover is promised.

Subscribe to 121 CRM Seller, billing and cancellationUse the migration checklist

Customer Thread

HubSpot migration decision path

Illustrative example

Discover
Objects and dependencies
Map
Fields and lifecycle meaning
Sample
Controlled import
Accept
People reconcile results
Human decision
Cut over
Fallback retained

Illustrative plan. No completeness, timescale, automated migration or feature-equivalence claim is made.

HubSpot mapping evidence

Map objects, properties and relationships before the wider import.

The field-level view reinforces why contacts alone are not a complete migration specification.

121

Northstar Joinery

Fictional

Move customer records with checks in place

DiscoveryInventoryMappingSample testCutover

See where each HubSpot record will go

A controlled fictional sample — no migration is running

3 decisions open

Sample records

145

Fictional

Mapped objects

Draft mapping

Open exceptions

Review required

Proposed destination	Sample	Exceptions	Result
People and organisations	40 records	0	Passed
Organisations	12 records	2	Review
Opportunities	18 records	3	Review
Timeline entries	75 records	4	Sampled

Sample → reconcile → approve → rehearse cutover → retain fallback

Illustrative CRM interfaceAll people, organisations, dates and activity are fictional. Availability depends on verified configuration and scope.

What the destination needs

Move the relationships, not just the rows.

A useful migration preserves the meaning of contacts, active work, ownership and next actions. It also records what cannot move cleanly and who decides the treatment.

Capability 01

Import and export

Moves supported records through structured files, with mapping and validation needed before relying on the result.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Supports controlled migration and operational extracts when the data is prepared and reconciled.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 02

Custom fields

Adds structured fields to supported record types so a business can capture information it actually needs.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Replaces important notes and spreadsheet columns with searchable, reusable data.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 03

Companies

Groups people and related information around an organisation rather than treating every person in isolation.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Helps business-to-business teams see contacts in the context of the company they work for.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 04

Opportunities

Represents a potential sale or deal linked to a contact, value, owner and pipeline position.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Shows which customer conversations are active commercial work rather than general contacts.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 05

Linked contacts

Associates relevant people with an opportunity so communications and responsibilities can be seen together.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Keeps the buying group and deal context connected where more than one person is involved.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 06

Testing and execution logs

Supports test runs and operational evidence used to diagnose why a record did or did not follow a path.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Gives a human a way to verify automation and investigate exceptions.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Before comparison

Compare the work you need, not two feature lists in the abstract.

Document why the organisation is considering change and which customer journeys must continue during and after the move.

Business jobs

Name the teams, pipelines, forms, campaigns, reports and hand-offs that matter to current operations.

Source ownership

Confirm the account owner, subscription, connected domains, inboxes, calendars, numbers and third-party applications.

Human decision

Difference register

Record what will be retained, redesigned, replaced, left behind or cannot yet be verified.

Object and history mapping

Contacts are only one part of the migration.

The source may contain companies, deals, activities, owners, custom properties, consent context and associations with different destination meanings.

Records and relationships

Inventory contacts, companies, deals, activities, notes, tasks, owners and the associations the team relies on.

Properties and stages

Map definitions, formats, option values, lifecycle stages and pipeline stages rather than copying labels blindly.

History and evidence

Decide which communication, consent, activity and change history is required, exportable and appropriate to retain.

Controlled cutover

Place data, workflows, forms and connections inside one acceptance path.

Discovery, representative testing, reconciliation and fallback precede operational handover.

121 CRM · Onboarding control room

Discover

Goals and dependencies

Prepare

Data and workflow inputs

Configure

Account and journeys

Customer tests the result

Handover

Owners and next review

Open decision

Migration history depth

Customer owner

Operations lead

Acceptance gate

Representative journeys pass

Illustrative exampleSequence only. Deliverables, timings, support and cost require an agreed scope.

Workflows and connections

Rebuild deliberately; do not assume automations translate.

Triggers, branches, suppression, scoring, forms, lists and integrations may have no direct destination equivalent.

Workflow specification

Document entry rules, actions, delays, stop conditions, ownership and exceptions before any rebuild.

Forms and pages

List embedded assets, domains, redirects, tracking and lead-source dependencies that could break at cutover.

Integration inventory

Re-authorise and test each required email, calendar, advertising, payment or external-system connection separately.

Sample, reconcile, cut over

Prove the migration on controlled data before the wider move.

A completed import is not evidence that relationships, meaning and operating journeys survived.

Representative sample

Include active, inactive, duplicate, incomplete, associated and exception records in a reversible test.

Reconciliation

Compare counts, required fields, owners, relationships, histories and representative user journeys.

Cutover and fallback

Agree freeze time, final delta, DNS/form changes, user access, validation, source retention and rollback authority.

Questions about this page

Useful answers, without the sales fog.

1. Can every HubSpot record and feature move to 121 CRM?

No completeness or feature-equivalence promise is made. Export availability, object support, associations, histories, workflows and connected assets must be assessed against the current source and destination accounts.

2. How long does a HubSpot migration take?

No standard timescale is approved. It depends on objects, data quality, history, workflows, integrations, assets, testing, decisions and user readiness.

3. Will 121 rebuild our workflows and forms?

That work is not stated as included by the CRM checkout. Any analysis, rebuild, content, testing or cutover support requires an agreed scope.

4. When should we cancel the source account?

Only after contractual, export, retention, reconciliation, user-acceptance and fallback needs are resolved. This page does not recommend a universal cancellation point.

Read all CRM questions

Continue the journey

Migration checklist CRM integrations Onboarding responsibilities

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing