A HubSpot migration partner can be an agency, an independent CRM migration consultant, or a CRM migration vendor with its own tooling. The labels overlap, and so do the pitches. What separates one from another is what they have actually done with your source system, how they test, and what they commit to in writing.
This guide covers what to look for, what to ask, and what a good answer sounds like. It does not rank providers. It gives you criteria you can apply to any HubSpot migration services provider, including ones you already know.
When Do You Need a Migration Partner?
Not every migration needs one. A move that involves standard objects, a source app HubSpot supports, and someone on your team who knows HubSpot can be done in house.
HubSpot’s Smart Transfer covers a fixed list of source apps. It moves data one way, is designed for a one-time migration, and can only be run by a Super Admin. Mapping your own custom fields through it requires a Data Hub subscription, and it does not support custom objects. If your project goes beyond that, a partner starts to make sense.
These are signs a partner is worth considering:
- Your source app is not on Smart Transfer’s list. The data then has to move another way, such as the source’s exports or API and HubSpot’s import tool.
- You use custom objects. HubSpot custom objects need an Enterprise subscription, so the design and the plan have to be settled together.
- You need activity history. HubSpot’s import tool can create emails, meetings, notes, and tasks, but it cannot update existing ones, so activity loads have to be right the first time.
- You have automations to rebuild. HubSpot workflows need a Professional or Enterprise subscription, and the logic has to be rebuilt, not copied.
- You have a fixed go-live date. A renewal or a launch date leaves little room for rework.
Experience With Your Source CRM
Experience with HubSpot is not the same as experience with your source CRM. Every source system has its own data model and its own export rules. Salesforce, for example, limits how often you can export your data and deletes the export files 48 hours after the notification email is sent. A partner who has moved data out of your source before knows where these limits appear.
Ask how many migrations the partner has done from your source system, what went wrong in them, and how it was fixed. Ask for a reference from a similar project, and ask to speak to that client.
What HubSpot tiers and directory profiles tell you
HubSpot groups Solutions Partners into Gold, Platinum, Diamond, and Elite tiers. Tiers are earned through partner points, and the top two also require a minimum customer retention rate. Partners also need a valid Solutions Partner Certification. A tier tells you how HubSpot classes the partner’s business. It does not tell you whether the partner has migrated from your source CRM.
The HubSpot Solutions Directory lets you filter by service, industry, and country. Profiles can show industry and app-specific badges and reviews from customers who worked with the partner. HubSpot’s review guidelines say only customers who meet them should leave reviews, and partners can ask HubSpot to remove reviews that break the guidelines. Treat directory ratings as one input, and check them against references you speak to yourself.
Data Mapping and Custom Object Capabilities
Mapping is where a migration is decided. A partner should be able to show you, before any data moves, how each source object, field, and relationship will land in HubSpot.
- Matching rules. HubSpot matches contacts by email address and companies by domain name, and an import without a unique identifier creates duplicates. Ask how the partner handles records that have neither.
- Custom objects. Smart Transfer does not move them and HubSpot limits objects, properties, and associations by subscription. Ask whether the partner designs for the limits of your plan, and which plan the design needs.
- Fields that do not map. Ask what happens to values that have no clean destination: converted, parked in a note, or left behind.
- Decisions you own. What to leave behind, which pipelines to keep, and which fields matter are your decisions. A good partner asks you for them and records the answers.
A useful test: ask for a sample mapping document from a past project, with client details removed. A partner who cannot show one may not have one.
Migration Testing and Quality Assurance
Testing is the difference between finding a problem on a sample and finding it in your live CRM. Because HubSpot’s import tool cannot update existing emails, meetings, notes, and tasks, a mistake in an activity load cannot be fixed by importing again. It has to be caught first.
Ask the partner to describe its pilot: which records, how many, and what the pilot will and will not prove. HubSpot’s standard sandbox needs an Enterprise subscription. It copies your setup and, if you choose, your 5,000 most recently updated contacts with a limited number of associated records. Deploying from a sandbox to production covers supported assets and configurations, not records, and integrations are not connected automatically. If your plan does not include a sandbox, ask where the pilot will run instead.
Agree on what done means before the project starts. At a minimum, that covers record counts reconciled against the source, associations checked, property values spot-checked, ownership confirmed, and workflows tested on test records.
Integration and Workflow Expertise
Most CRMs are connected to other tools, and most have automations built around them. HubSpot’s import tool loads records and activities. It does not carry over automation logic, so workflows are designed and built as a separate piece of work.
Ask who rebuilds the workflows, whether that is in the quoted scope, and how each one will be tested. Some partners use HubSpot configuration automation to deploy repeatable setup, such as properties, pipelines, deal stages, workflows, and permissions, instead of rebuilding it by hand for every client. Ask how a partner handles that part of the build, and whether what was built is documented for your team.
For integrations, ask the partner to list every tool that sends data to your source system or reads from it, and to say for each one whether it will be reconnected, replaced, or retired. If the partner does not ask you for that list, the scope may be missing something.
Security, Access, and Data Handling
A migration puts a full copy of your customer data in someone else’s hands for the length of the project. Ask about it directly.
Access to your HubSpot account
One way a partner gets access to a client account is an access link that the client approves. Partner Admins cannot add, remove, or downgrade Super Admins, change billing settings, make payments, or manage Sensitive Data. Separately, a Super Admin controls which product subscription and usage data is shared with the partner, and can change that at any time in Partner Data Access settings. Ask which of your people at the partner will have access, at what permission level, and when it will be removed after the project.
Data outside HubSpot
During a migration, data often passes through files, scripts, or migration tools before it reaches HubSpot. Ask where it is stored, who can open it, how long it is kept, and how it is deleted when the project ends. Ask for the data handling terms in writing.
Certifications
ISO/IEC 27001 is a standard for an information security management system, and certification is voluntary. A logo on a website does not show what a certificate covers. If a partner cites a certification or an audit report, ask for it and check which part of the business and which systems it applies to.
Pricing, Scope, and Support
Two quotes can only be compared if they describe the same work. Ask every provider to quote against the same written scope, and check that each quote names:
- The objects, record volumes, and custom fields included
- Activity history and attachments, and how much of each moves
- Workflows and integrations rebuilt, and how many
- The pilot, the validation steps, and what counts as done
- The HubSpot plan the design needs, since the subscription is a cost separate from the partner’s fee
- How changes to scope are priced
Productizing HubSpot services means standardizing the repeatable parts of a service and delivering them as defined modules. It does not make a quote better by itself, but a defined scope is easier to compare than an open-ended one. Whichever model a partner uses, ask what would cause the price to change.
Ask about support after go-live too: how long it lasts, what it covers, and how fast questions get answered.
Partner Evaluation Checklist
Once you have chosen, make sure these are in your hands before the project starts:
- A written scope listing objects, volumes, workflows, and integrations
- A source-to-HubSpot mapping, with your decisions recorded
- A pilot plan with success criteria
- Confirmation of the HubSpot plan the design needs
- An access plan: who, at what level, and the removal date
- Data handling terms
- A support period and what it covers
- A reference from a similar migration
Conclusion
The right HubSpot migration partner is the one whose experience matches your source system, whose scope is written down, who tests before touching your live data, and who is open about access and data handling. Tiers, badges, and reviews are useful starting points, but references and a written scope tell you more.
Frequently Asked Questions
01 When should a business hire a HubSpot migration partner?
When the project goes beyond what a one-time transfer and an import can handle: a source app outside Smart Transfer’s list, custom objects, activity history, automations to rebuild, or a fixed go-live date.
02 What should a HubSpot migration partner provide?
A written scope, a source-to-HubSpot mapping, a pilot, validation against the source, rebuilt workflows and integrations if they are in scope, documentation of what was built, and a defined support period.
03 How do you compare migration vendors?
Give each one the same written scope and ask the same questions. Compare what each quote includes and excludes, not only the total, and check each claim against a reference you speak to yourself.
04 Does a migration partner also rebuild workflows?
HubSpot’s import tool does not carry over automation logic, so workflows are a separate piece of work. They also need a Professional or Enterprise subscription. Ask for them to be named in the quote.
Manual migrations cost more than engineer hours.
Skip the QA cycles, data cleanup, and errors found weeks after go-live. SuprSwitch runs the full migration in 3-4 days, validated record by record.