Skip to content

CRM Migration RFP Template: What to Ask Potential Vendors

Vendors answer the question they are given. If your request for proposal says only that you want to move your CRM to HubSpot, you will get quotes for different projects, written in different formats, built on different assumptions. They cannot be compared, and the gaps show up later as change requests.

A CRM migration RFP template fixes that. It gives every vendor the same scope, the same questions, and the same format for the answer. This guide walks through each section of the RFP, what to put in it, and the CRM migration vendor questions that separate a vague proposal from a usable one. It ends with a scoring matrix and a list of questions for the demo. Where it helps, it also shows how SuprSwitch, SuprDense’s CRM migration platform, answers the same questions, so you can see what a specific answer looks like.

What to Include in a CRM Migration RFP

An RFP is a short, structured document. Most of the work is in being specific about your own situation, because the vendor can only be as precise as you are. A useful RFP has ten parts.

RFP sectionWhat you writeWhy it matters
1. Background and goalsWho you are, why you are moving, and what success looks likeVendors design for the outcome, not only the transfer
2. ScopeSource CRM, destination HubSpot plan, what is in and out of scopeKeeps quotes for the same work
3. Data and objectsRecord counts, custom objects, history to keepDrives effort and the HubSpot plan you need
4. Integrations and automationsConnected tools, workflows, reportsThese are rebuilt, not copied
5. Security and complianceAccess, certifications, data handling, privacy termsDecides who may touch your data
6. Testing and acceptancePilot, reconciliation, sign-off rulesDefines what done means
7. Timeline, roles, and pricingDates, your team, the format for the priceMakes quotes comparable
8. Response formatQuestions the vendor must answer, in orderMakes scoring possible
9. Evaluation criteriaHow you will score the responsesVendors see what you value
10. Process and deadlinesDeadline for questions, response date, demo windowKeeps the process on schedule

Send the same document to every vendor, and share any answer you give one vendor with all of them. This applies whether you are asking a freelancer, an agency, or a firm that offers CRM migration services. A vendor that cannot answer the questions in a structured way is telling you something before the project starts.

Define Business Goals and Scope

Start with why you are moving. A migration to cut license cost, a migration to unify marketing and sales data, and a migration forced by a contract end date lead to different priorities, and vendors should know which one is yours.

Then write the scope as a list of what is in and what is out. Name the source CRM and version or edition, the HubSpot subscription you have or plan to buy, and the teams that will use the new system. Say which objects must move, which data you are happy to leave behind, and whether anything else is part of the project, such as new pipelines, new properties, or training.

Decide early whether you want a pure migration or a migration plus a redesign. They are different projects with different quotes, and mixing them in one RFP is a common source of confusion. Our guide to CRM migration vs. implementation explains where they overlap and how to sequence them.

Include the constraints that vendors cannot guess:

  • A fixed go-live date, and the reason for it, such as a renewal or a launch.
  • A freeze period when nobody can change data in the source system.
  • The people on your side who can make decisions, and how quickly they can answer.
  • Budget range, if you are willing to share it. It lets vendors propose the right size of project.

Document Data and Object Requirements

This is the section that most changes the quotes. Give vendors numbers, not descriptions. A vendor who has to guess the size of your data will either quote high to cover the risk or quote low and revisit the price later.

Ask for a data inventory from your own team before you write the RFP, and include it:

  • Record counts. Contacts, companies, deals, tickets, and any other standard object, with the number of records for each.
  • Custom objects and fields. A list of custom objects, with record counts and the main relationships between them. HubSpot custom objects need an Enterprise subscription, so say which plan you are on.
  • History to keep. State how far back you need emails, calls, meetings, notes, and tasks, and whether attachments must move.
  • Data quality. Known duplicates, records with no email address or company domain, and fields nobody uses.
  • What you can leave behind. Closed records, old campaigns, and unused fields. Every record you do not move is time you do not pay for.

It helps vendors to know how the destination works. HubSpot matches contacts by email address and companies by domain name, and an import without a unique identifier creates duplicates. HubSpot also limits how much you can import at once. On a paid account, an import file can be up to 512 MB and 1,048,576 rows, with up to 10,000,000 rows and 500 imports in a rolling 24 hours. Large data sets are split and sequenced, and that planning is part of the vendor’s work.

Ask the vendor how it will move activity history. HubSpot’s import tool can create emails, meetings, notes, and tasks, but it cannot update the ones that already exist, so a mistake in an activity load cannot be fixed by importing the file again.

Finally, ask which method the vendor will use. HubSpot’s Smart Transfer is built for a one-time, one-way migration from a fixed list of apps, and it can only be run by a Super Admin. Mapping your own custom fields through it requires a Data Hub subscription, and it does not transfer custom objects. If your source app is on the list, ask how the vendor uses Smart Transfer and what it does outside it. If it is not on the list, ask how the data will move instead.

A migration platform is one answer to that question. SuprSwitch connects to the source CRM and to HubSpot through their APIs and maps any field or object that lives in the source CRM, including custom objects, along with activities, owners, and associations. Its Schema Analysis phase also produces much of the data inventory above: every custom field, record count, and property type, with duplicates, empty required fields, and broken associations flagged before any data moves.

List Integrations and Automation Dependencies

A CRM rarely works alone. List every tool that reads from or writes to it: email, calendar, billing, support desk, marketing platform, data warehouse, forms, and any custom API connections. For each, give the owner on your side and what would break if it stopped.

Automations need the same treatment. Workflows, assignment rules, scoring, approvals, and scheduled reports are logic, and logic is rebuilt rather than moved. HubSpot’s import and transfer tools carry data, not the rules around it. HubSpot workflows also need a Professional or Enterprise subscription, so the plan you buy affects what can be rebuilt.

Ask each vendor to respond to this table for your list:

DependencyWhat the RFP should sayWhat the vendor should answer
Connected appsName, owner, direction of syncReconnect, replace, or retire, and who does it
Workflows and rulesCount, purpose, ownerWhich are rebuilt, simplified, or dropped
Reports and dashboardsThe ones you rely on weeklyWhich are rebuilt and how they are checked
Custom code and APIsWhere it exists, what it doesHow it is reviewed and what it costs

Do not let the answer be that integrations are handled during the project. Each integration is either in the quoted scope or it is a change request, and you want to know which before you sign.

Specify Security and Compliance Needs

Your CRM holds personal data and often commercial data that competitors would value. The RFP should say plainly what you require, and it should ask for evidence, not only promises.

What to ask for

  • Access. Who will have access to the source CRM and to HubSpot, at what permission level, and when it will be removed. Ask for named people and a removal date.
  • Data handling. Where data is stored during the project, how it is transferred, whether copies are kept, and how they are deleted when the project ends.
  • Certifications. Ask for any security reports the vendor holds and when they were issued. A SOC 2 report comes in two kinds: Type 1 looks at controls at a single point in time, and Type 2 looks at whether they operated over a period. ISO/IEC 27001 is a standard for an information security management system, and organizations can choose to be certified against it. Ask what the certification covers, because it may not cover the team assigned to your project.
  • Privacy terms. If you process personal data about people in the EU or UK, the vendor will normally be a processor. Article 28 of the GDPR requires a contract that binds the processor to your instructions, covers subcontractors, makes information available for audits, and provides for deleting or returning personal data when the service ends. Ask to see the vendor’s data processing terms and subprocessor list before you sign.
  • Incident handling. How you will be told about a problem, and how fast.

Do not treat a certificate as a replacement for these questions. It tells you the vendor has a security program. It does not tell you how your data will be handled on this project.

Hold every vendor to this standard, including us. For SuprSwitch, the specific answers are that data moves directly from the source CRM to HubSpot under a no-storage architecture, so it is never held on SuprSwitch servers, and that on SuprDense’s Salesforce to HubSpot migrations the OAuth tokens used for access are revoked after each migration. Ask for the same detail, in writing, from every vendor you shortlist.

Set Testing and Acceptance Criteria

Testing is where a migration is proven. Write the acceptance rules into the RFP so that every vendor prices the same amount of testing, and so that you know in advance what you will sign off.

At minimum, ask for:

  • A pilot. A trial migration of a representative sample, with the records and the checks described. A pilot proves the mapping works, not that the full run will be perfect.
  • Reconciliation. Record counts compared against the source for every object, with differences explained.
  • Association and property checks. Spot checks that contacts, companies, and deals are linked correctly and that key properties carry the right values.
  • Workflow and integration tests. Each rebuilt workflow tested with test records before it is switched on.
  • User acceptance testing. Named people on your side test the daily tasks and sign off in writing.

As a reference point, SuprSwitch builds the pilot into its process. Its Pilot Validation phase runs a sample migration before the full run and checks relational integrity, activity history formatting, field truncation, and association chains. During Final Execution, real-time record validation flags any record that does not appear in HubSpot within the expected window, and a retry mechanism re-runs failed records without restarting the job.

Ask where the pilot will run. HubSpot’s standard sandbox needs an Enterprise subscription. It copies your setup and, if you choose, your 5,000 most recently updated contacts with up to 100 associated deals, companies, and tickets for each. Emails sent from a sandbox to people who are not sandbox users will not send, which keeps test data from reaching real customers. If your plan does not include a sandbox, ask where the vendor will test and how it will protect live data.

Also ask what happens if the migration fails acceptance. A good proposal says how problems are fixed, how long the vendor stays engaged, and what the rollback or correction path is.

Request Timelines, Roles, and Pricing

Ask for a timeline built from phases, not a single number: discovery, mapping, pilot, full migration, validation, go-live, and support. For each phase, ask what the vendor needs from you and by when. Most delays in migration projects come from waiting for decisions and access, so the vendor’s assumptions about your response times matter as much as its own work.

For comparison, SuprSwitch runs a migration in four phases, Schema Analysis, Mapping Logic, Pilot Validation, and Final Execution, typically over 3 to 4 days. A proposal laid out in phases like these makes it easy to see where your decisions are needed.

Ask for a roles table covering both sides: who leads the project, who maps the data, who approves the mapping, who tests, and who signs off. Ask the vendor to name the people it will assign, not just job titles.

For pricing, set the format so quotes line up. Ask each vendor to price separately:

  • Discovery and mapping
  • Data migration, by object where relevant
  • Workflow and integration rebuilds
  • Testing, pilot, and go-live support
  • Post-migration support, with the period and hours included
  • Any third-party software or licenses the vendor expects you to buy

Then ask for the assumptions behind the price: the record counts it used, how many workflows, how many integrations, and what happens if those numbers change. Ask how change requests are priced and approved. A fixed price with hidden assumptions is not cheaper than a time-and-materials quote with clear ones.

Record counts usually drive the price. SuprDense prices SuprSwitch migrations on the total number of records in the source CRM, with self-service, guided, and custom options, so the counts in your data inventory feed directly into the quote.

Do not forget your own costs. The HubSpot subscription, your team’s time for decisions and testing, and any overlap while both systems run are outside the vendor’s quote, but belong in your budget.

Vendor Scoring Matrix

Score every response against the same criteria, written before the proposals arrive. That keeps the decision about fit, not about the best presentation. Use two steps: a pass or fail gate, then weighted scores.

Step one: must-haves

Some requirements are not a matter of degree. If a vendor cannot meet them, it does not go through to scoring. Typical examples are accepting your data protection terms, naming the people with access to your data, and committing to a written scope.

Step two: weighted scoring

Give each criterion a weight that adds up to 100, then score each vendor from 1 to 5. The weights below are an example and should reflect your priorities.

CriterionWeightVendor A (1 to 5)Vendor B (1 to 5)
Experience with your source CRM2045
Data mapping and validation approach2053
Security and compliance1535
Integrations and automation rebuild1543
Testing and acceptance plan1043
Timeline and team1034
Pricing clarity and assumptions1053
Weighted total (out of 100)1008176

The weighted total is each score multiplied by its weight, added together, then divided by 5. For vendor A that is (20 x 4 + 20 x 5 + 15 x 3 + 15 x 4 + 10 x 4 + 10 x 3 + 10 x 5) divided by 5, which is 81. For vendor B it is 76. The numbers are illustrative, not a benchmark.

Two habits make the matrix more useful. Have two or three people score separately before comparing, and ask for references before the final decision. A reference from a project like yours, with a source CRM like yours, is worth more than a polished proposal.

Questions to Ask During Vendor Demos

A demo shows how a vendor communicates and what it has built before. Use it to test the answers in the proposal, not to repeat them. These questions work for any vendor.

AreaQuestions
ExperienceHow many migrations have you done from our source CRM to HubSpot? What went wrong on the last one, and how was it fixed? Can we speak to that client?
MethodWill you use Smart Transfer, imports, the API, or a mix? Why? What does each move, and what is left for manual work?
MappingCan you show a sample mapping document with client details removed? How do you handle fields that have no destination?
TestingWhere will the pilot run? How many records, and what will it prove? How do you reconcile counts against the source?
AutomationWhich of our workflows will you rebuild, and which will you advise dropping? How is each one tested?
SecurityWho will have access to our data? Where is it stored during the project? How and when is it deleted?
TeamWho works on our project day to day? What happens if that person leaves?
ChangeHow are scope changes raised, priced, and approved? What is outside this quote?
After go-liveWhat does support cover, for how long, and who answers when something breaks?

Pay attention to how specific the answers are. A vendor that has done the work can describe what went wrong. A vendor that has not will talk about its process in general terms.

The most useful demo uses your own data. SuprSwitch offers a free sample migration, so you can check the mapping on a slice of your records before you commit, and you can ask other vendors for the same.

Conclusion

A good CRM migration RFP is specific about your data, your integrations, your security requirements, and how the work will be tested. It asks every vendor the same questions in the same format, and it tells them how you will score the answers. That is what makes a CRM migration proposal comparable, and what protects you from a project that grows after the contract is signed.

Enterprise CRM Migration: Governance, Security, and Data Ownership

A small team can migrate a CRM by asking one person to do it carefully. An enterprise cannot. Several departments own parts of the data, regulations apply to some of it, dozens of systems read from it, and a mistake during cutover reaches many people at once. The technical transfer is often the smaller part of the project. The larger part is deciding who is allowed to decide, what must be protected, and how anyone will later prove that it was done properly.

This guide covers the governance, security, and ownership questions that an enterprise CRM migration has to answer before data moves, and ends with a readiness checklist you can use to test your own plan. Along the way, it shows where SuprSwitch, SuprDense’s CRM data migration platform, supports those controls.

Why Enterprise CRM Migrations Need Additional Governance

Governance means a written answer to four questions: who decides, who can see the data, what is recorded, and what happens when something goes wrong. In a small migration these answers sit in one person’s head. In an enterprise they have to be written down, because the people who decide are not the people who do the work, and because a regulator, an auditor, or a new team lead may ask months later.

Enterprise migrations also differ in the number of moving parts. There are usually several source systems or business units, custom objects and automations built over years, integrations with finance, support, and marketing systems, and legal duties attached to customer data. Each of these adds a stakeholder with a veto. Without a governance structure, those vetoes appear late, during testing or on the day of cutover, when they are most expensive.

Establish Data Owners and Decision Rights

Every data domain needs a named owner who can approve or reject decisions about it. A domain is a group of records with a business meaning, such as accounts and contacts, opportunities and pricing, support history, or marketing consent. The owner is accountable for what is kept, how it is cleaned, and whether the migrated result is acceptable. The migration team can advise, but it should not own those calls.

Write the decision rights down. A simple table is enough.

RoleDecidesDoes not decide
Executive sponsorScope, budget, cutover date, final go or no-goField-level mapping
Data owner (per domain)What is kept or archived, merge rules, acceptance of resultsTechnical method
Security and compliance leadData classification, access rules, vendor and tool approvalBusiness priority
System owner (HubSpot admin)Properties, permissions, pipelines, platform configurationWhether data is retained
Migration leadSequence, tooling, defect triageBusiness rules on the data
Integration ownersCutover of each connected systemCRM data rules

Decide in advance how disputes are settled and how fast. Two owners disagreeing about which of two duplicate accounts is correct is normal. A project that has no rule for settling it will stall.

Classify Sensitive and Business-Critical Data

Not all CRM data carries the same risk. Classify it before you decide how to handle it. A workable scheme has three or four levels, for example public or low risk, internal, confidential, and restricted. Typical examples of restricted data in a CRM are personal identification numbers, financial details, health information, contract terms, and notes that contain private conversations.

Classify by column and by record type, then record the result next to your field mapping so that each property carries its handling rule with it. Also identify business-critical data, which is not necessarily sensitive but would be costly to lose or corrupt: open deals, renewal dates, pricing, and customer hierarchies.

SuprSwitch’s Schema Analysis phase gives you the starting list for this work. It scans the source CRM and surfaces every custom field, record count, and property type, so each column can be classified before any data moves.

Classification has a direct effect on the HubSpot side. HubSpot lets Super Admins mark custom properties as Sensitive Data or Highly Sensitive Data, which adds a layer of encryption and restricts where the values can be used, and it requires an Enterprise subscription to configure. Properties marked this way are also unavailable in sandboxes, so a test in a sandbox will not exercise them. By default, HubSpot encrypts data in transit and at rest, so the extra setting is for data that needs more than the default. Decide which properties need it before the data is loaded, not after.

Plan Access Controls and Data Handling

A migration creates a copy of your data in places it does not normally live: export files, working spreadsheets, a mapping environment, the migration tool, and the destination. Each is an access point to control. Plan access for the people and for the data.

  • People: Give migration staff the minimum access for the minimum time. In HubSpot, permissions are set per user and cover actions such as import, export, and approving exports of others. Limit who can export records during and after the project, and remove temporary access at cutover.
  • Tools: HubSpot Smart Transfer is available only to Super Admins, so the number of Super Admins is itself a control. A Super Admin can also use many other settings, so keep the group small.
  • Files: Treat extracts as production data. Store them in an approved location, encrypt them, restrict who can open them, and delete them on a set date. Write that date down.
  • Vendors: If a third party touches personal data, you need a contract. Article 28 of the GDPR[1] requires that processing by a processor be governed by a contract that, among other things, has the processor delete or return personal data at the end of the services. Article 32[1] requires appropriate technical and organisational measures, including encryption where appropriate and regular testing of those measures.

Ask every vendor, including any CRM data migration platform you consider, the same questions: where is the data processed, who can access it, how long is it kept, and how is it deleted at the end. A good answer is specific. A vague answer is a finding.

For SuprSwitch, SuprDense’s answers are specific. Its no-storage architecture means data moves directly from the source CRM to HubSpot and is never held on SuprSwitch servers, and on SuprDense’s Salesforce to HubSpot migrations the OAuth tokens used for access are revoked after each migration. Confirm these points in your data processing terms, as you would with any vendor.

Map Integrations and Downstream Systems

In an enterprise, the CRM is rarely a standalone tool. ERP, billing, support, data warehouse, marketing automation, and single sign-on all connect to it. A migration that ignores them leaves systems pointing at a CRM nobody is updating.

Build an inventory of every connection: what system, what direction, what data, how often, who owns it, and what breaks if it stops. Then decide for each whether it is rebuilt against HubSpot, replaced, or retired. Pay attention to record identifiers. Record IDs in the destination will not match the source, so any system that stores the old ID needs a mapping, and a custom property that holds the source ID is worth creating for that reason alone.

The same goes for the source system’s own integrations. HubSpot notes that its Smart Transfer tool is designed for a one-time migration, and that if you keep using Salesforce alongside HubSpot you should use the HubSpot-Salesforce integration instead, because running both would create duplicate records. If your project is a Salesforce to HubSpot migration with a period of coexistence, that choice has to be made in the plan, not found out in production.

Set Validation and Audit Requirements

Decide before the migration what evidence you will need afterwards. Three kinds matter.

  • Reconciliation evidence: Record counts per object in the source and the destination, with every difference explained, plus value-level samples and totals that were checked and who signed them off.
  • Change evidence: A record of who did what during the project. HubSpot’s audit logs record user actions in the account, are available to Super Admins, and can be exported. The log in the interface covers only a recent period and records actions by HubSpot users, not changes made by other means such as form submissions, so export what you need on a regular schedule and keep your own project log for the rest. Enterprise accounts can filter by more categories than Starter and Professional accounts.
  • Decision evidence: Meeting notes, approvals, and exceptions. When someone asks why a field was dropped, this is the answer.

Part of the change evidence can come from the migration itself. SuprSwitch’s real-time record validation flags any record that does not appear in HubSpot within the expected window, and its status screen shows the records migrated so far. On SuprDense’s consolidation project for Salted Stone, validation and difference reports were archived as CSV files, which gives the audit trail a fixed record of what moved.

Also decide what a failed validation means. Set thresholds in advance, such as the share of records that may fail or the totals that must match, and who can approve an exception. Agreeing on the rule before the numbers arrive prevents arguing about it afterwards.

Coordinate Teams and Migration Waves

A single big-bang cutover is rarely the right choice for an enterprise. Waves reduce risk. You can move one business unit, region, or product line first, learn from it, and adjust. Choose the first wave to be representative but forgiving: a team that is willing to give detailed feedback and whose data is not the most critical.

A sandbox helps here. HubSpot offers standard sandboxes on Enterprise subscriptions. A sandbox copies supported assets from production when it is created, and you can include a set of recently updated contacts and their associated records. Record IDs differ between sandbox and production, integrations are not connected automatically, and workflow enrollment in a sandbox is capped, so treat it as a place to test configuration and mapping, not as a full rehearsal of volume. A full-volume rehearsal needs its own plan.

Configuration also has to reach production intact. Suprdense CONFIG’s sandbox-to-production deployment moves a validated configuration as a single unit, so the properties, pipelines, and workflows approved in the sandbox are the ones that go live. For data, SuprSwitch’s Pilot Validation runs a representative sample first, which suits a first wave you want to learn from.

Run each wave to the same script: freeze or define a change window for the source data, migrate, reconcile, review with the data owners, and then release to users. Publish the calendar, the contacts, and the escalation path early. Enterprise projects fail more often from people not knowing what happens on Monday than from technical errors.

Manage Cutover and Contingency Plans

Plan cutover as a sequence with times and owners, not as an event. It should cover when the source goes read-only, how changes made during the window are captured, when integrations are switched, when users get access, and who signs off at each step.

Changes made during the cutover window are where records often go missing. SuprSwitch supports delta migration, which moves only the records created or changed since the main run. On the Salted Stone consolidation, a final delta run captured the Salesforce activities created after the first extraction.

Write the rollback plan before you need it, and be honest about what it can do. For the migration tool, understand what reversing a step does. HubSpot Smart Transfer can revert a transfer, which removes the settings it created, such as properties, pipelines, users, currencies, and workflows, and deletes the records it created. It cannot delete records that were synced through a standard sync connection. A rollback plan for the business also has to cover the days after go-live, when users have already made edits in the new system.

Define the conditions that trigger rollback and who can call it. Keep the source system available, read-only, for an agreed period after cutover, so that anyone who finds a discrepancy can check the original. Decide in advance when that source system will be retired and how its data will be archived.

If you use a CRM data migration platform, confirm how it supports these steps, including logging of what was moved and what failed, because that record becomes part of your evidence. SuprSwitch logs failures through real-time validation and re-runs failed records with its retry mechanism, without restarting the whole job.

Enterprise Migration Readiness Checklist

Use this checklist before you approve the start of each wave. Each line should have a named owner and a yes or no.

AreaQuestionOwner
OwnershipDoes every data domain have a named owner with decision rights?Sponsor
OwnershipAre dispute rules and response times agreed?Sponsor
ClassificationIs every column classified, and does the handling rule travel with the mapping?Security lead
ClassificationAre sensitive properties set up in HubSpot before data loads?System owner
AccessIs migration access limited, time-bound, and approved?Security lead
AccessAre export files stored securely, with a deletion date?Migration lead
VendorsAre data processing terms signed with every party that touches personal data?Compliance
IntegrationsIs every connection inventoried with an owner and a plan: rebuild, replace, or retire?Integration owners
ValidationAre reconciliation thresholds and sign-off roles defined?Data owners
AuditIs the project log kept, and are platform logs exported on schedule?System owner
TestingHas the first wave been tested with realistic data, including awkward records?Migration lead
CutoverIs the cutover sequence written, with times, owners, and read-only source access?Migration lead
ContingencyAre rollback triggers, owners, and limits written down?Sponsor
CommunicationDo users know the dates, what changes, and where to get help?Change lead

Conclusion

An enterprise CRM migration succeeds when the decisions are made before the data moves: who owns each domain, how each field is classified, who has access to what, which integrations depend on the CRM, what evidence you will need, and how you can step back if something fails. The technology is the easier part.

Start with owners and classification, build the checklist into your plan, and run the first wave as a real test. If you are weighing a Salesforce to HubSpot migration, or any other move into HubSpot, and want to talk through governance for your own situation, get in touch with SuprDense. If you want a migration that is validated record by record, try a sample migration with SuprSwitch.

References

[1] Regulation (EU) 2016/679 (General Data Protection Regulation), Article 28 (Processor) and Article 32 (Security of processing). https://eur-lex.europa.eu/eli/reg/2016/679/oj

How to Map Salesforce Custom Objects to HubSpot

Standard objects are the more straightforward part of a Salesforce to HubSpot move. Accounts become companies, contacts stay contacts, and opportunities become deals. The custom objects are where the planning is. They hold the data that is specific to your business, they have relationships that only you defined, and HubSpot’s Smart Transfer does not move them.

This guide covers Salesforce custom object migration to HubSpot from the first decision to the final check: whether each object belongs in HubSpot at all, how fields and relationships translate, and how to confirm the result before anyone starts using it. It also shows how SuprSwitch, SuprDense’s CRM migration platform, handles each step through its four phases: Schema Analysis, Mapping Logic, Pilot Validation, and Final Execution.

How Salesforce Custom Objects Work

A custom object is a table your Salesforce admins built for data the standard objects do not cover. What matters for migration is how it connects to other objects. Salesforce has three ways to do that:

  • Lookup. Links two objects. The lookup field is optional by default, and what happens on delete is set per field: the lookup is cleared (the default), the delete is blocked, or the delete cascades.
  • Master-detail. A parent-child link in which the master controls the detail record. Deleting the master deletes its detail records, the detail record’s owner is set to the master’s owner, and it inherits the master’s sharing and security settings. By default a detail record cannot be moved to a different master.
  • Many-to-many. Built with a junction object that has two master-detail fields, one to each side.

Salesforce also has roll-up summary fields, which summarize the detail records of a master-detail relationship on the master record. They matter later, because a roll-up has no source data to copy: it is a result that HubSpot has to calculate again.

These differences decide what you have to rebuild. A lookup is only a link. A master-detail relationship also carries delete, ownership, and sharing behavior, and a junction object may hold data of its own. A HubSpot association is a link between two records, so any of that extra behavior you still need has to be designed on purpose.

Check HubSpot Object Compatibility

Before you map anything, confirm three things.

  • Your plan. Custom objects are available with Enterprise subscriptions. The number of custom objects and properties you can have depends on your subscription, and the Limits tab in your data model shows your own numbers. Association labels need Professional or Enterprise.
  • The migration route. Smart Transfer does not support custom objects. Custom object records get in through a file import, HubSpot’s Salesforce custom object sync, or the API. The sync needs Enterprise too, and the custom object must already exist in HubSpot before you set it up.
  • The object itself. Not every Salesforce custom object needs a HubSpot custom object.

SuprSwitch takes the API route. It maps any field or object that lives in Salesforce, and its contextual object mapping rebuilds custom objects as HubSpot custom objects. It does not change HubSpot’s plan rules: the objects are created in your account, so the Enterprise requirement and the limits below still apply.

Then check your design against HubSpot’s limits. The figures below come from HubSpot’s own documentation, listed in the references at the end, so confirm them against your own account before you commit to a design.

LimitWhat the catalog lists
Custom object definitions and recordsDepends on your Enterprise subscription. Check the Limits tab in your data model for your own numbers.
Custom propertiesDepends on your subscription. Check the Limits tab in your data model.
Values per picklist property1,000[1]
Associations for a custom object9 defined associations between each custom object type and other object types[1]
Associated records per record250,000 per association type on paid accounts[1]
Association labelsUp to 50 labels per object pair, on Professional and Enterprise[2]
Standard sandboxUp to 200,000 records per object type can be imported, on Enterprise[3]

For each Salesforce custom object, choose one of three outcomes:

What the Salesforce object isHubSpot optionCheck first
A thing with its own records, fields, and relationships, such as a subscription, an asset, or a projectA HubSpot custom objectDefinitions, records, and associations fit the limits above
Extra detail on one standard record, such as a few fields on an accountProperties on the matching standard objectWhether one record can hold the detail
Data nobody uses or reports onLeave it out, or keep an archiveWho signs off on dropping it

Rebuilding every Salesforce object as a HubSpot custom object can leave you with a model that is harder to use and to report on. Decide object by object.

If you are still planning the wider move, our Salesforce to HubSpot migration page covers the standard objects and how SuprSwitch handles the migration.

Inventory Fields and Relationships

Build the inventory from Salesforce before you open HubSpot. For every custom object you plan to keep, record:

  • The number of records, which you will use in the final check and to compare with your HubSpot record limit.
  • Every field with its type, whether it is required, and whether anyone uses it. Compare the total with the custom property limit shown in your Limits tab.
  • For every picklist, the values actually stored in records, not only the values in the setup list. Salesforce does not enforce the value list of an unrestricted picklist when data is created through the API, so records can hold values that are not on the list.
  • Whether multicurrency is on. If it is, each record has its own currency code, and the currency fields on that record are expressed in that currency.
  • Every relationship: the related object, the type (lookup, master-detail, or junction), and the direction. Compare the count per object with the 9 associations HubSpot allows for a custom object[1].
  • Who owns the records and how many owners there are.

Keep it as a single mapping sheet with a decision column for each field and relationship: map, convert, rebuild, or drop. Every later step works from this sheet, and it is the document you send for sign-off.

SuprSwitch’s Schema Analysis phase builds much of this inventory for you. It scans the Salesforce org and surfaces every custom field, record count, property type, and picklist value, and flags duplicates, empty required fields, and broken associations before any data moves.

Map Salesforce Fields to HubSpot Properties

Most fields have a clear HubSpot equivalent. This table shows the usual choices, using the property types HubSpot documents.

Salesforce fieldHubSpot propertyWatch for
TextSingle-line textHubSpot allows up to 65,536 characters in a property[4]
Long text areaMulti-line textSame limit; line breaks are not supported in some tools
Rich textRich textUp to 64 KB per value, including images[4]
CheckboxSingle checkboxImport values are True or Yes, False or No
PicklistDropdown select or radio selectImport values must match an option’s label or internal value. HubSpot lists 1,000 values per picklist property[1]
Multi-select picklistMultiple checkboxesSalesforce stores selections separated by semicolons, and HubSpot imports them the same way. The options must already exist in HubSpot
DateDate pickerHubSpot accepts day-month-year, month-day-year, and year-month-day[5]. Keep one order in the file
Date and timeDate and time pickerWithout a time the value defaults to midnight[5]. Records display in the user’s device time zone
NumberNumber (formatted or unformatted)Check scale and precision against the Salesforce field
CurrencyNumber (currency)Use a currency HubSpot accepts. With multicurrency, keep the Salesforce currency code in its own property
PercentNumber (percentage)HubSpot imports either 25% or .25[5]
EmailEmailCheck formatting in the file before import
PhonePhone numberSalesforce phone values can include letters. HubSpot expects +[country code][number], with ext for extensions
URLURLCheck formatting in the file before import
Auto numberSingle-line textKeep the existing numbers so references stay valid
Address, geolocationOne property per componentThese hold several values in one field
FileFile propertyUp to 10 files per property[4]
FormulaCalculation property, or a plain valueCalculation properties need Professional or Enterprise
Roll-up summaryRollup property, or a plain valueRebuild the logic and compare results
Lookup or master-detailAn association, not a propertyCovered in the next section
Salesforce record IDA custom text property with unique valuesStore the 18-character ID. It is case-safe, and the 15-character version is case-sensitive[6]

Three decisions come up on almost every project.

The primary display property. Every HubSpot custom object needs one. It names each record and is required to create a record. Pick a field that every Salesforce record has, and turn on the unique values option if it should never repeat. The internal name of the object cannot be changed after it is created, so settle names before you create it.

The Salesforce ID. Store it on every record as a property with unique values, using the 18-character form. Salesforce treats the 15-character ID as case-sensitive, so a tool that ignores case can treat two different records as the same one, and Salesforce recommends the 18-character ID in all API calls[6]. HubSpot can use a custom unique-value property to match custom object records, which lets you re-run an import as an update and match parents to children later. Without a unique identifier, an import creates new records and duplicates follow.

Picklists. Clean the values before the import, starting with the values found in the records. If two Salesforce values mean the same thing, merge them in the mapping sheet and not in the HubSpot property afterwards.

With SuprSwitch. In the Mapping Logic phase, SuprSwitch’s transformation layer maps Salesforce objects and fields to the HubSpot data model. If a matching object or property does not exist yet, you can create it from SuprSwitch in a single click. Keep each field on a property with the same data type, because a number stored as text can no longer be reported on.

Plan Associations and Record Ownership

Associations

Associations must be defined before records can be linked. You create them in the data model, between the custom object and the objects it relates to, and then add labels to describe the relationship. Labels need Professional or Enterprise, and they have to exist in HubSpot before an import uses them. Remember the limit of 9 defined associations for each custom object type[1] when you design the model.

Map each Salesforce relationship like this:

  • Lookup. Becomes an association. If the lookup identified a role, such as the primary contact, create a label for it.
  • Master-detail. Also becomes an association. Decide separately what to do about the behavior it carried: who owns the child records, who can see them, and what should happen to them when the parent is removed.
  • Junction object. HubSpot associations can link many records on each side, so a junction is not needed just to connect two objects. Keep it as its own custom object only if the junction record holds data, such as a role, a date, or a quantity, and associate that object with both sides.

You can also set limits on associations, both overall and per label, up to 10,000 for a custom limit[7]. Setting limits needs Super Admin permissions. If an overall limit is one, it takes precedence over any label limit, so a label set to allow many still permits only one.

Loading associations

Load parents before children. In a file import, associations can be created in one file, or across files that share a column which identifies the same record in both. This is where the stored Salesforce ID earns its place. Each row needs a unique identifier for each record. To link one record to several others, repeat the identifier on several rows, or put the related identifiers in one cell separated by semicolons. Without identifiers the import creates duplicate records instead of linking them. Several labels in one cell are separated by semicolons, and imported labels are added to the labels a pair of records already has.

SuprSwitch’s association integrity mapping takes care of this ordering. It preserves one-to-one and labeled relationships as records move, so child records arrive linked to the right parents.

If you use HubSpot’s Salesforce custom object sync, know its limits. Lookup fields cannot be mapped as fields, so relationships go through associations. Associations only sync between objects that already sync, so company sync has to be on before accounts can be associated with a custom object. A custom object cannot sync to both Salesforce contacts and leads.

Ownership

Custom object records can have an owner. To set owners through an import, include an owner column with each user’s name or email address and map it to the owner property. The user has to exist in HubSpot with a seat and permission to view that object, so create or assign users first. Imported assignees do not get a notification. For a Salesforce detail record whose owner followed its master, decide whether to give it the parent’s owner explicitly in the file.

SuprSwitch’s ownership transfer engine resolves records owned by deactivated Salesforce users before anything moves, and users whose email address matches in both systems are mapped automatically.

Handle Unsupported Fields and Data Types

Some fields do not fit a single HubSpot property type. Do not drop them silently. For each one, make an explicit decision and record it in the mapping sheet.

CaseOptionsNote
Formula fieldsRecreate as a calculation property, or import the current value as a plain propertyFormula fields are read-only in the Salesforce API. A plain value stops updating
Roll-up summary fieldsRecreate as a rollup property, or import the current valueCompare the result with Salesforce after the load
Lookup fieldsCreate an associationNative sync cannot map lookup fields
Text longer than the property limitSplit, shorten, or store as a file or noteSingle and multi-line text hold up to 65,536 characters[4]
Encrypted textDecide whether the value should move at allSalesforce encrypted text holds up to 175 characters[8]
Compound fieldsMap each component to its own propertyAddress and geolocation hold several values in one field
Time-only valuesCombine with a date, or store as textHubSpot documents date and date and time pickers
Attachments and filesA file property, or a separate transferA file property holds up to 10 files, and uploads to a record are limited to 50 MB on paid accounts[4]
Required fields with no valueSet a default before importThe primary display property is required to create a record

The goal is a record of what changed and why. When a user asks months later where a field went, the mapping sheet should have the answer.

Test the Mapping With Sample Records

Run the mapping on a small set of records before the full load. If you have an Enterprise plan, use a standard sandbox, where HubSpot lets you import up to 200,000 records per object type[3]. Record IDs in a sandbox differ from production, so a test proves the mapping and not the IDs.

Choose records that exercise the edge cases, not just typical ones:

  • A record for each relationship type, including a junction record with its own fields.
  • A record with the longest text, the most picklist options, and empty required fields.
  • A parent with many children, and a child whose parent is not in the sample.
  • Records with date and time values, percentages, and currency, including a record in a different currency if multicurrency is on.
  • A record whose multi-select picklist has several values selected.

Then check three things. Open each test record in HubSpot and compare it with Salesforce field by field. Open the associated records from both sides. Finally, run the same file again, matched on the Salesforce ID, and confirm it updates the records instead of creating duplicates. Fix the mapping sheet first, and only then change the import.

This is SuprSwitch’s Pilot Validation phase. A representative sample moves first, and the run checks relational integrity, field truncation, and association chains before the full load. If the mapping changes, the sample runs again.

Validate Records After Migration

Matching record counts is a start, not proof. A migration can have the right number of records and still have broken links or wrong values. Check each of these:

During Final Execution, SuprSwitch’s real-time record validation flags any record that does not appear in HubSpot within the expected window, and its retry mechanism re-runs failed records without restarting the whole job. Its no-storage architecture means your Salesforce data is never held on SuprSwitch servers. The checks below then confirm the result independently.

CheckWhat to compareWhat a gap means
Record countsRecords per object in Salesforce and in HubSpotRows were skipped, rejected, or duplicated
Association countsLinks per relationship in both systemsParents or children loaded in the wrong order, or the wrong key
Orphan recordsChild records with no parentA parent was missing from the load
Required fieldsRecords with a blank primary display property or other required valueA default was missed
Picklist valuesDistinct values per propertyA value did not match and was dropped
Multi-select valuesSelections on a sample of recordsAn option was missing or split incorrectly
CurrencyAmount and currency code on a sample of recordsA currency was dropped or defaulted
Dates, numbers, percentagesA sample of values against SalesforceA format or time zone changed
Calculated valuesCalculation and rollup results against Salesforce formulasThe logic was rebuilt differently
OwnersOwner on a sample of recordsA user was missing or mapped incorrectly
DuplicatesRecords that repeat the same Salesforce dataA load ran without the identifier, or IDs were compared without case
Import filesRows in each file against HubSpot’s per-file limit of 1,048,576 rows[5]A file was truncated or split incorrectly

Use a sample for the value checks and full counts for the volume checks. The CRM migration checklist covers the checks that apply to the whole project, including what to confirm before go-live.

Common Mapping Mistakes

  • Copying the Salesforce model one to one. Some objects work better as properties on a standard object, and some should not move.
  • Designing before checking the plan. Custom objects, labels, and calculation properties depend on your subscription.
  • Importing before the object and associations exist. Both have to be defined first.
  • Leaving out a unique identifier. Without one, a second run creates duplicates instead of updating.
  • Mapping a lookup as text. The value arrives, but the link between the records does not.
  • Loading children before parents. Load parents first so every child has a record to link to.
  • Ignoring junction data. A role or date on the junction has nowhere to go on a plain association.
  • Treating picklists as clean. Records can hold values that are not on the Salesforce list, so check the data and not only the setup.
  • Ignoring HubSpot limits. Check definitions, properties, associations, and picklist values against the limits before you build.
  • Trusting counts alone. Check links, values, and owners as well.

Conclusion

Mapping Salesforce custom objects to HubSpot comes down to a short list of decisions made early: which objects move, which become properties, how each relationship is represented, and what happens to fields that do not fit. Make them in a mapping sheet, test them on edge cases, and validate links and values, not only counts.

SuprSwitch is built around the same sequence. Its four phases move the hard decisions to the front, before live data touches HubSpot.

References

[1] HubSpot, Product & Services Catalog: Technical Limits. https://legal.hubspot.com/hubspot-product-and-services-catalog/technical-limits

[2] HubSpot Knowledge Base, Create and use association labels. https://knowledge.hubspot.com/object-settings/create-and-use-association-labels

[3] HubSpot Knowledge Base, Create a sandbox and deploy changes to production. https://knowledge.hubspot.com/account-management/deploy-sandbox-changes-to-production

[4] HubSpot Knowledge Base, Understand property field types in HubSpot. https://knowledge.hubspot.com/properties/property-field-types-in-hubspot

[5] HubSpot Knowledge Base, Format import files. https://knowledge.hubspot.com/import-and-export/set-up-your-import-file

[6] Salesforce Help, Locate the Unique ID of a Record in Salesforce. https://help.salesforce.com/s/articleView?id=000385008&language=en_US&type=1

[7] HubSpot Knowledge Base, Set limits for record associations. https://knowledge.hubspot.com/object-settings/set-limits-for-record-associations

[8] Salesforce Help, Classic Encryption for Custom Fields. https://help.salesforce.com/s/articleView?id=platform.fields_about_encrypted_fields.htm&language=en_US&type=5

CRM Integration vs. Migration: Which Is Right for Your Business?

When two CRMs need to work together, there are two different answers. You can connect them so that data flows between them, or you can move everything into one and retire the other. People often use the words interchangeably, and that is how projects end up with the wrong plan: a migration scoped like an integration, or an integration that quietly becomes a permanent second system nobody planned to run.

This guide explains what each approach is, how they differ in data movement, cost, and upkeep, when each one fits, and how to decide. It uses HubSpot as the destination, since that is where most of our readers are heading. On the migration side, it also shows where SuprSwitch, SuprDense’s CRM migration platform, fits.

What Is CRM Migration?

CRM migration is a move. Data is extracted from the old system, transformed to fit the new one, loaded, checked, and then the old system is retired. After cutover there is one system of record. The work is front-loaded: it takes place over a defined project, and ends.

A migration usually covers records such as contacts, companies, deals, and activities, along with the supporting structure: properties, pipelines, users, and associations between records. HubSpot’s Smart Transfer is built for this case. It supports a defined list of source apps, including Salesforce, Pipedrive, Dynamics 365, ActiveCampaign, and Zoho CRM, and HubSpot describes it as designed for a one-time migration from another app. Smart Transfer can also revert a transfer, which is useful when something is wrong in a first run.

SuprSwitch covers the same ground, including custom objects, which Smart Transfer does not support. It connects to the source CRM and HubSpot through their APIs and maps any field or object that lives in the source, along with owners, activities, and associations. Its four phases, Schema Analysis, Mapping Logic, Pilot Validation, and Final Execution, give the project a defined start and a defined end.

What Is CRM Integration?

CRM integration is a connection. Both systems stay in use, and a sync keeps chosen data consistent between them. The work is continuous: the connection must be set up, monitored, and maintained for as long as both systems are used.

HubSpot data sync is one example. After you connect a supported app, you can configure a one-way or two-way sync so that updates in one system appear in the other, based on your settings. A sync is always between two apps, one of which is HubSpot. It starts with an initial sync that indexes the existing records in both systems, then an incremental sync that checks HubSpot for changes at regular intervals and relies on the other app’s webhooks to flag its own changes. For very large databases the initial sync takes time; HubSpot notes that very large syncs can take several days.

The HubSpot-Salesforce integration is another. It is designed for ongoing two-way syncing, is available on Professional and Enterprise subscriptions of HubSpot’s hubs, and requires a Salesforce system administrator with specific profile permissions to set up.

Key Differences Between Migration and Integration

MigrationIntegration
GoalMove data to a new system and retire the old oneKeep two systems consistent while both stay in use
DurationA project with an end dateOngoing for as long as both systems are used
Data movementMostly one-time bulk transfer, then deltas until cutoverContinuous, record by record, one-way or two-way
System of recordOne, after cutoverTwo, with rules for which value wins
Main riskData loss, mapping errors, cutover problemsSync conflicts, duplicates, API limits, broken connections
Ongoing workMostly stops after go-live and a stabilization periodMonitoring, error handling, and updates to field mappings
Cost profileOne-time project cost, then the old license endsBoth licenses continue, plus the upkeep of the connection
UsersOne system to learnTwo systems, and the question of where to update what

The two also have different failure modes. A migration usually fails visibly and early, in testing. An integration can fail slowly: a field mapping drifts, a sync error goes unread, and two systems disagree for months before somebody notices.

A migration’s visible failures are also the easiest to catch. SuprSwitch’s real-time record validation flags any record that does not appear in HubSpot within the expected window, and its retry mechanism re-runs failed records without restarting the whole job.

When to Keep Two CRMs Connected

Integration is the right choice when both systems have a real, continuing job.

  • Different teams, different tools: Sales runs in one CRM, and marketing or service runs in HubSpot, and each team’s tool fits its work. A common example is HubSpot for marketing alongside Salesforce for sales.
  • A migration is not yet possible: A contract, a regulation, a dependency on a custom build, or a divestiture means the old system has to remain for a period. An integration can bridge that period.
  • A phased move: You can connect the systems while you migrate in stages. This is a temporary integration with a planned end.
  • A small, defined overlap: Only a limited set of records needs to be shared, such as qualified leads or closed deals. Sync rules and filters let you limit what flows. In HubSpot data sync, for example, filters limit which records sync between the apps.

Know what you take on. A permanent integration means two licenses, two admins, and a mapping that has to be updated whenever either side changes a field. The HubSpot-Salesforce integration, for example, uses a limited number of API calls per day, and a single contact sync can take several API calls per record. HubSpot connects to only one Salesforce instance per HubSpot account[1]. Those are constraints to plan around, not reasons to avoid integration.

When to Move to a New CRM

Migration is the right choice when the old system no longer has a job, or costs more than it returns.

  • Cost or consolidation: You are paying for two platforms to do what one could do.
  • One view of the customer: Teams are working from different versions of the same records, and syncing has become a permanent effort to hide that.
  • The old system is a limit: It cannot support your process, your reporting, or your integrations.
  • Complexity from patches: Years of custom fields, workarounds, and connectors have made the system hard to change.

Remember that moving the data is only part of the job. A migration puts records in the new system, but it does not on its own configure the new system for how your team works. Our guide to CRM migration vs. implementation explains where one ends and the other begins.

Cost and Maintenance Considerations

Compare the total cost over a realistic period, not the upfront price. We deliberately give no numbers here, because they vary widely with data volume, complexity, and which tools you use. We can describe the shape of the cost.

  • Migration: A one-time cost for planning, mapping, cleaning, loading, testing, and cutover, plus a short stabilization period. After that, the license for the old system ends.
  • Integration: A lower start, since you only configure the connection. But you keep paying for both systems, plus the effort of owning the connection: monitoring, fixing sync errors, updating mappings, and handling conflicts. If either vendor changes something, it can need attention.

An integration looks cheaper at the start, and a migration often looks cheaper over a longer period when the alternative is running two systems indefinitely. The reverse is true when the second system is needed for years anyway, or when migrating means rebuilding something expensive. Put both on the same timeline, for example several years, and include the licenses, admin time, and the cost of inconsistent data.

Also count the cost of inaction. Records that disagree across systems lead to duplicated outreach, wrong reports, and time spent working out which version is right. These are harder to price, but they are the reason most teams eventually choose one system.

Can Integration and Migration Work Together?

Yes, and often they should, in a defined order. The common pattern is to integrate temporarily while you migrate. You connect the old and new systems for a limited period so that teams can keep working while data moves in phases, then switch off the sync when the old system is retired.

There is one important trap. If you are moving from Salesforce and plan to keep using it for a while, HubSpot recommends the HubSpot-Salesforce integration for that continuing sync and Smart Transfer for the one-time migration, and warns against mixing the two carelessly. The two use different unique identifiers to match records, and using them together can create duplicate records. If you previously used Smart Transfer, turn off its sync connections before turning on the Salesforce integration.

The sequence matters. Decide which system is the source of truth during the overlap, which fields flow in which direction, who resolves conflicts, and the date the connection ends. Write that date down at the start, or the temporary integration becomes permanent.

For some teams, delta migration is an alternative to a temporary sync. SuprSwitch can move only the records created or changed since the main run, so a phased migration can close each phase with a catch-up load instead of maintaining a two-way connection. On SuprDense’s Salted Stone consolidation, a final delta run captured the Salesforce activities created after the first extraction.

If you plan a move into HubSpot, a SuprSwitch CRM migration solution handles the data movement, while an integration is a separate piece of work. Define each one separately in the plan. Its no-storage architecture means the data moves directly from the source to HubSpot and is never held on SuprSwitch servers.

Decision Framework for Choosing an Approach

Answer each question for your own situation. Most answers point clearly to one approach, and a split result points to the hybrid described below.

QuestionIf yesIf no
Does the old system still have a necessary job in the years ahead?Lean to integrationLean to migration
Do two teams need different tools for different jobs?IntegrationMigration
Is a contract, regulation, or dependency preventing retirement of the old system now?Integrate temporarily, plan the migrationMigration can start
Is the overlap in data small and well defined?Integration with filtersMigration
Can you name an owner for the connection, and a person to watch it?Integration is viableIntegration is risky
Are you paying for two systems that do the same job?MigrationEither
Is a single view of the customer a business requirement?MigrationEither

If the answers are mixed, the hybrid is usually the answer: integrate now, migrate on a date, and switch the sync off on that date.

Conclusion

Integration connects two systems and keeps both running. Migration moves data into one and retires the other. Pick integration when both systems have a continuing job and you can own the connection. Pick migration when the old system has no future role. Use both in sequence when a phased move is the practical route, with an end date for the connection.

CRM Migration Cost Calculator: Estimate Your Budget

Many CRM migration cost calculators ask for a few numbers and return a price. The price depends on rates the calculator cannot see, and on parts of your data it cannot ask about. This CRM migration cost calculator works differently. It turns your CRM into a profile of cost drivers, shows you which ones will take the most work, and gives you a scope you can take to any provider.

It does not return a dollar figure, because the cost of a migration depends on who does it and what your data looks like. What it does is make sure every quote you get is for the same work, and that nothing that moves your CRM migration budget is missing from it. The examples are for moves into HubSpot. Where SuprSwitch, SuprDense’s CRM migration platform, changes the work behind a driver, the guide says so.

 How the CRM Migration Cost Calculator Works

The calculator has four steps:

1. Rate each driver. Use the table in the next section to mark each cost driver as Low, Medium, or High for your CRM.

2. Read your profile. Mostly Low means a lighter project. Each High is work that needs its own line in a scope.

3. Write the scope. List what moves, what gets rebuilt, and what stays behind.

4. Take it to providers. Ask each one to quote against the same scope.

The sections after the table explain why each driver matters, so you can rate it with confidence.

SuprSwitch’s Schema Analysis phase can fill in much of the profile for you. It scans the source CRM and surfaces record counts, custom fields, and property types, and flags duplicates, empty required fields, and broken associations, which covers the volume, data quality, and custom object rows.

 Inputs That Affect Your Estimate

Rate each driver for your own CRM. The thresholds for record volume come from HubSpot’s import limits. The other levels describe how much design and testing work a driver adds.

DriverLowMediumHigh
Source CRMOn HubSpot’s Smart Transfer listNot on the list, so data moves through exports or the API and HubSpot’s import toolMore than one source system
Record volumeEach object fits in one import file (1,048,576 rows)[1]Some objects need several filesTotal volume approaches HubSpot’s daily import limit (10,000,000 rows)[1]
Data qualityContacts have unique emails, companies have domains, few duplicatesSome contacts without email or companies without a domainMany missing identifiers or many duplicates
Custom objects and relationshipsStandard objects onlyA few custom objectsMany custom objects or many-to-many relationships
Activity historyNot moved, or recent onlyA defined period of historyFull history, including emails and meetings
AutomationNone to rebuildA few simple automationsMany, or with complex logic
IntegrationsEmail and calendar onlyA few, with HubSpot connectorsMany, or custom-built
Validation needsSpot checksReconciled counts and associationsFormal sign-off, rollback plan, or parallel run
HubSpot plan fitYour plan covers the designOne feature needs a higher tierSeveral features need a higher tier

The plan row matters because the HubSpot subscription is a separate budget line from the migration itself.

 Source and Destination CRM

The source CRM decides how data comes out. The destination decides what it can hold and which plan you need.

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 custom fields through it requires a Data Hub subscription, and it does not support custom objects. If your source is not on the list, the data has to move another way.

Some teams use CRM migration tools that connect to the source and destination directly instead of working from files. Others use exports and HubSpot’s import tool. Either way, the source sets the limits. Salesforce, for example, limits how often you can export your data, includes attachments and files in an export only if you select them, and deletes the export files after a set period. If you extract through its API instead, you work within a daily allowance for the whole org that your other integrations share.

SuprSwitch is one of those tools. It connects to the source CRM and HubSpot through their APIs, maps any field or object that lives in the source, including custom objects, and moves data directly under a no-storage architecture, so it is never held on SuprSwitch servers.

On the destination side, several HubSpot features depend on your subscription. Custom objects need Enterprise, workflows need Professional or Enterprise, and the leads object needs Sales Hub Professional or Enterprise. Settle the plan before you finalize the design.

Record Volume and Data Quality

Volume

On paid HubSpot accounts, an import file can be up to 512 MB and 1,048,576 rows[1]. You can import up to 10,000,000 rows and run 500 imports in a rolling 24 hours[1]. Volume above a single file means splitting and sequencing the load, which is project time. That is why the volume row in the table uses these limits.

Volume also drives tool pricing. SuprDense prices SuprSwitch migrations on the total number of records in the source CRM, so the counts you gather for this row feed straight into a SuprSwitch quote.

Data quality

HubSpot matches contacts by email address and companies by domain name, and an import without a unique identifier creates duplicates. Contacts without an email and companies without a domain need a plan before the import. Duplicates in the source become duplicates, merged records, or review work in HubSpot. Cleaning before the move reduces what has to be loaded, mapped, and checked.

Marketing contacts

If you use Marketing Hub, contacts count toward your billable tier only when they are marketing contacts. Contacts imported without a marketing status are non-marketing by default, and you can set a single-file contacts import to mark them as marketing contacts. If you exceed your tier, HubSpot upgrades you automatically to the next one. You are billed for it until your next renewal, even if the count drops. Super Admins and users with the Modify Billing permission can set a maximum, and imported contacts that would exceed it are set as non-marketing instead. Decide the number before the import.

Custom Objects, Associations, and Activities

HubSpot’s Smart Transfer does not support custom objects. Creating custom objects in HubSpot requires an Enterprise subscription, and each subscription limits objects, properties, and associations. Every custom object in your source is therefore moved into a HubSpot custom object, folded into a standard object, or left behind. Each option changes the cost in a different way.

Associations are the links between records, such as a contact and its company or a deal and its contacts. An import can create associations between objects, using identifiers such as email address, domain name, or record ID. Relationships that exist only in the source, such as many-to-many links, need their own design.

For activities, HubSpot’s import tool can create emails, meetings, notes, and tasks, but it cannot update existing ones. Each type needs certain properties, such as an email body and direction, or a task title and due date. HubSpot recommends including an activity date, and if you leave it out the import uses the date and time of the import. A wrong activity load cannot be fixed by importing again, so decide how much history you need before you rate this driver.

SuprSwitch migrates notes, calls, meetings, and tasks along with email history, its activity-type mapping keeps each activity on the matching HubSpot type, and its association integrity mapping preserves one-to-one and labeled relationships. That moves some of this driver from design work to mapping work.

Integrations and Automation

HubSpot’s import tool loads records and activities. It does not carry over automation logic, so workflows are designed and built separately, and workflows need a Professional or Enterprise subscription. Count the automations your team depends on, and retire the ones nobody uses.

List every tool that sends data to your CRM or reads from it. For each one, decide whether it will be reconnected to HubSpot, replaced, or retired. A tool with a HubSpot connector and a custom-built integration are different jobs, which is why the table separates them.

Testing, Reconciliation, and Go-Live Support

A pilot on a representative sample finds mapping problems while they are cheap to fix. HubSpot’s standard sandbox needs an Enterprise subscription. It copies your setup and, if you choose, a set of your 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 one, plan where the pilot will run.

Reconciliation means more than counting records. A matching count shows the data moved, not that it matches, so check associations, owners, deal stages, and activity history too. Our CRM migration checklist covers the verifications to run before go-live.

SuprSwitch builds the pilot into its process. Its Pilot Validation phase runs a sample migration before the full run, and during Final Execution its real-time record validation flags any record that does not arrive while its retry mechanism re-runs failures. A free sample migration on your own data is also a low-cost way to test a driver before you rate it.

Plan the cutover as well. Keep the source available until validation is complete, and check your source CRM’s renewal date against your go-live date. Agree on what support you get after go-live and how long it lasts.

Example Migration Scenarios

These three examples are illustrations. They are not real client projects and they carry no prices. They show how the profile changes with the shape of the data.

DriverA: Small team, standard objectsB: Growing team, custom dataC: Several systems merged
Source CRMLowMediumHigh
Record volumeLowLowHigh
Data qualityMediumMediumHigh
Custom objects and relationshipsLowHighHigh
Activity historyLowMediumHigh
AutomationLowMediumHigh
IntegrationsLowHighMedium
Validation needsLowMediumHigh
HubSpot plan fitLowHighHigh

Scenario A. Almost everything is Low, so the work centers on cleaning the contacts that lack an email and checking the result. A transfer or an import may cover most of it, and the main costs are your team’s time and the HubSpot plan.

Scenario B. The volume is small, but custom objects, integrations, and the plan they require are High. The scope needs a data model for the custom objects, an Enterprise subscription, rebuilt workflows, a reconnected integration list, and a pilot. A provider would quote these items separately.

Scenario C. Most drivers are High. This project needs an assessment before anyone can quote it, because each system, its volume, and its history have to be sized on their own.

The same logic applies to your own profile. The more High ratings you have, and the more of them are in custom objects, history, or integrations, the more important a written scope becomes.

Get a Tailored Migration Estimate

Get a Custom CRM Consolidation Estimate

Every CRM consolidation project is different. To provide an accurate estimate for moving your data into HubSpot, we’ll need a few details:

  • Source and destination CRMs: Which platforms are you consolidating?
  • Record volume: How many contacts, companies, deals, and other records need to be migrated?
  • Data structure: Are custom objects and custom fields involved?
  • Activity history: How much historical data needs to be preserved?
  • Workflows and integrations: Which automations and third-party integrations need to be rebuilt?
  • HubSpot subscription: Which HubSpot plan do you currently use or plan to purchase?
  • Migration timeline: What is your target go-live date, and what validation requirements do you have?

With SuprSwitch, record counts and a free sample migration help establish the scope and starting point for your quote. Choose from self-service, guided, or custom migration options based on your requirements.

Planning to consolidate multiple CRMs into HubSpot? Talk to a SuprSwitch migration expert to discuss your migration requirements and get a tailored estimate.

The cost of a CRM migration comes from the shape of your data, not from a headline number. Rate each driver, write down the scope, and ask every provider to quote the same work. That is the most reliable way to a CRM migration budget you can defend. If you want to test your profile on real data, try a sample migration with SuprSwitch.

References

[1] HubSpot Knowledge Base, Format import files. https://knowledge.hubspot.com/import-and-export/set-up-your-import-file

How to Consolidate Multiple CRM Systems Into HubSpot

Migrating one CRM into HubSpot is a move. Consolidating several is a merge, and a merge is harder because the same customer can exist in every system, described differently each time. One system calls them a lead, another an account, a third a contact with a different spelling of the company. Which record is right, which owner is current, and whose notes survive are decisions, not data transfers.

This guide covers how to decide whether consolidation is the right move, how to inventory and align your systems, how to resolve duplicates and conflicts, how to keep ownership and history intact, and how to phase and validate the result. It also shows how SuprSwitch, SuprDense’s CRM migration platform, handles a consolidation through its four phases: Schema Analysis, Mapping Logic, Pilot Validation, and Final Execution.

When Does CRM Consolidation Make Sense?

Consolidation usually follows a business event: an acquisition, a merger of business units, a regional team that bought its own tool, or a long period in which different teams chose their own systems. The common symptoms are duplicate customers across teams, reports that need a spreadsheet to reconcile, sales reps who cannot see what marketing or support has already done, and several licenses for overlapping tools.

It does not always make sense. Keep systems separate when business units have different data models and no shared customers, when regulations require data to stay apart, or when a unit is about to be divested. Consolidate when the cost of not having one view of the customer, in lost context, duplicated outreach, and manual reporting, is greater than the cost of the project. Decide this with the owners of each system, because the project will need their time and their data.

Inventory Each CRM and Its Data Model

Before you decide how to merge, document what each system holds. For each CRM, record the objects in use, the record counts, the custom objects and fields, the pipelines and stages, the users and owners, the integrations and automations, and the quality of the data, including how many records are missing an email address or a company domain. Those two fields matter more than the rest for consolidation, because HubSpot uses email to identify contacts and domain to identify companies.

Put the results side by side. You will usually find that the same concept has different names, that the same name has different meanings (a lifecycle stage in one system may be a lead status in another), and that stage definitions do not match. Write these differences down now. They become the first draft of your mapping.

Also check how each source can be extracted. HubSpot’s Smart Transfer tool supports a defined list of source apps, including Salesforce, Pipedrive, Dynamics 365, ActiveCampaign, and Zoho CRM. A source that is not on that list, including another HubSpot portal, needs a different route, such as an export and import or a purpose-built migration tool.

SuprSwitch is one such tool. It works with HubSpot as a source as well as a destination, and its Schema Analysis phase scans each source CRM and surfaces every custom field, record count, and property type, flagging duplicates, empty required fields, and broken associations. That way the side-by-side inventory starts from the same facts for every system.

Define a Master Data Model

A master data model is the single set of rules for what a record means in the consolidated HubSpot portal. It answers a short list of questions.

  • Objects: Which HubSpot objects will you use, and which source objects map to each? Decide where leads, accounts, and any custom objects land, bearing in mind that custom objects require a HubSpot Enterprise subscription.
  • Identity: What makes a record the same record? For contacts it is normally the email address, and for companies the domain name. Where either is missing, you need a different rule, such as a source system ID.
  • Properties: One definition per business concept. If three systems each store industry differently, choose one list of values and map the others to it.
  • Pipelines and lifecycle: One agreed set of lifecycle stages and, where sales processes truly differ, separate pipelines with shared definitions of won and lost.
  • Source of truth: For each property, which system wins when two disagree? It may differ by field. The billing system may win on address, and the sales system on owner.

Name one person who can approve changes to the model. Without that, every team will ask for its own exceptions.

In SuprSwitch, the master data model becomes the Mapping Logic. Each source is mapped to the same HubSpot objects and properties, several source pipelines and their stages can be merged into one, and any property or custom object the model needs can be created from SuprSwitch in a single click.

Resolve Duplicate and Conflicting Records

Duplicates are the heart of consolidation. They come in two kinds. Exact duplicates share an identifier, such as the same email address in two systems. Fuzzy duplicates describe the same entity with different values: Acme Ltd and ACME Limited, or a contact with a work email in one system and a personal email in another.

HubSpot helps with the exact kind. It automatically deduplicates contacts by email address and companies by domain name when records are created through imports or forms. During an import, if a contact already exists with the same email, the imported information updates the existing contact rather than creating a new one, and only mapped properties are updated. Two limits matter. If an import includes no email or other unique identifier, each row becomes a new contact. And companies created through the API, including by some third-party sync apps, are not deduplicated by domain.

Plan the rules before you load anything.

  • Decide a winner: When two records match, which one’s values are kept? A simple rule works best, such as: the most recently updated non-empty value wins, except for owner and lifecycle stage, where the primary system wins.
  • Keep a source ID: Create a custom property in HubSpot that stores each record’s ID from its source system. It gives you a stable key for matching, for updating records in later waves, and for tracing a record back to its origin. HubSpot imports can also deduplicate on a custom property that requires unique values.
  • Use secondary values: HubSpot supports additional email addresses on contacts and additional domains on companies, so a second address from another system can be attached to the same record and not create a duplicate.
  • Review the fuzzy matches: Automated matching on names is unreliable. Send borderline matches to a human, and set a rule for what happens to anything nobody reviews.

Be careful with merging inside HubSpot after the data is loaded. Once two records are merged they cannot be unmerged, and HubSpot also limits how many times a record can be merged. Resolve identity before loading wherever you can.

Our CRM consolidation case study describes this problem in practice: a company that acquired a business had to combine Salesforce data with a long-established HubSpot portal. According to the case study, identity was governed by reference IDs rather than company names, a side-by-side simulator exposed a possible 600-record chain merge before production, and a set of rules controlled which records were created, updated, merged, or skipped.

That consolidation ran on SuprSwitch, which can merge duplicates as part of the migration, so the identity rules are applied before records reach HubSpot rather than cleaned up afterwards.

Map Fields Across Source Systems

With several sources, mapping is a many-to-one exercise. One HubSpot property may receive values from three different fields in three systems, each with different formats.

Build the mapping as one worksheet with a row per HubSpot property and a column per source system, then add the transformation rule, the owner of the decision, and the status. Standardize as you go: phone number formats, country names, date formats, currencies, and picklist values.

Check data types carefully. A text field in one source that holds dates, a number stored as text, or a picklist whose retired options still appear on old records will all fail or load incorrectly. HubSpot dropdown properties hold a defined list of options, so build that list first from the union of source values, and map each source value to it.

Run a small sample from each source through the mapping before committing to it. Differences you did not expect will show up in the sample, when they are cheap to fix.

This is SuprSwitch’s Pilot Validation phase. A representative sample from each source moves first, and the run checks relational integrity, field truncation, and association chains before the full load.

Preserve Ownership, Associations, and History

A consolidated CRM that has all the records but not the context is not useful. Three things need deliberate handling.

  • Ownership: List the users from every system, match them to HubSpot users, and decide how to treat people who have left. Users generally need to exist in HubSpot before the records they owned can be assigned to them, so settle owners first.
  • Associations: Contacts need to stay connected to the right companies, deals to the right contacts, and activities to the right records. Load in dependency order, with companies and contacts first and the records that depend on them afterwards, so each relationship can be created as the record arrives. When a required relationship cannot be established safely, hold the record for review and do not load it without its parent.
  • History: Calls, emails, meetings, tasks, and notes are often far more numerous than the contacts and companies themselves. Decide what history you will bring, and test it. HubSpot’s import tool cannot update existing emails, meetings, notes, or tasks, so an activity loaded with the wrong association has to be dealt with another way.

The same case study reports that inactive owners were mapped so that historical records kept their original context, that required company lookups acted as a guardrail, and that a final delta run captured activity created after the initial extraction.

SuprSwitch’s ownership transfer engine resolves records owned by deactivated users before anything moves, its association integrity mapping keeps contacts, companies, deals, and activities linked, and it migrates notes, calls, meetings, and tasks along with email history.

Plan a Phased Consolidation

Whether to consolidate all at once or in phases depends on risk, volume, and how much each system is in use. A single cutover is shorter for users but has little room for error. Phases reduce risk and give you time to learn, but they mean running two systems in parallel for longer.

A phased plan often follows this order:

  • Phase 1, the primary system: Load the system that will serve as the base, so that the master data model is proven on real data.
  • Phase 2, the next source: Add the second system against the first, with the matching rules active. This is where duplicate handling is tested.
  • Phase 3 and later: Add the remaining systems, one at a time, each with its own validation.
  • Delta loads: Plan for changes made in the source after the initial extraction, and a short freeze window or a final delta run.

SuprSwitch supports delta migration, which moves only the records created or changed since the main run, so each phase can close with a final catch-up load.

Pause automations in HubSpot during loads so that records are not emailed, enrolled, or reassigned halfway through. Keep each source system read-only for a set period after its cutover, so that anyone who finds a discrepancy can check the original, and agree when each system will be retired.

Validate Data Across All Sources

Validation in a consolidation has an extra step: you check each source against HubSpot, and you check the merged result as a whole. Counts will not match one to one, since merging reduces the number of records. So reconcile with an explanation: source records loaded, minus records merged, minus records excluded, should equal records in HubSpot.

  • Counts: Per object and per source, with every difference explained.
  • Duplicates: Run a duplicate check on the result. Look for the same email or the same domain appearing where it should not.
  • Values: Compare a random sample from each source field by field, including dates, amounts, picklists, and owners.
  • Relationships: Open records and check that contacts, companies, deals, and activities connect as they did in the source.
  • People: Ask a user from each former system to look at their own accounts. They will notice what the numbers do not.

During Final Execution, SuprSwitch’s real-time record validation flags any record that does not appear in HubSpot within the expected window, and its retry mechanism re-runs failed records without restarting the whole job. Its no-storage architecture means data from every source moves directly to HubSpot and is never held on SuprSwitch servers.

Our guide to CRM migration best practices has the general checklist, and the same steps apply here, repeated for each source.

Common CRM Consolidation Risks

RiskWhat happensHow to reduce it
No agreed source of truthTeams argue over which value is right after go-liveDecide a winner per property before the first load
Missing emails and domainsRecords cannot be matched and become duplicatesAdd a source ID property and set matching rules for records without these fields
False mergesTwo different customers become one record, and merges in HubSpot cannot be undoneResolve identity before loading and review borderline matches
Unmatched picklist valuesValues are rejected or left blankBuild the option list from all sources first
Broken associationsContacts, deals, and activities are detached from their parent recordsLoad in dependency order and hold records without a parent
Lost ownershipRecords belong to nobody, or to the wrong personCreate users and map owners before loading records
Automation firing on loadsCustomers receive unintended emailsPause workflows and sequences during loads
Stale data after the first extractThe new system is out of date at go-livePlan a delta load and a freeze window
Scope growthEach team asks to keep its own exceptionsName one owner for the master data model

Conclusion

Consolidating several CRMs into HubSpot is mostly about decisions: what the customer record means, which value wins when sources disagree, who owns what, and in what order the data moves. Make those decisions in a master data model, resolve identity before loading, move data in dependency order, and validate each source and the combined result.

SuprSwitch is built for this kind of project: map every source to one model, run a sample, then migrate in phases with real-time validation and delta runs. If you are planning a consolidation, try a sample migration with SuprSwitch or get in touch with SuprDense.

How to Choose the Right HubSpot Migration Partner

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.

How Much Does a Salesforce to HubSpot Migration Cost?

Search for Salesforce to HubSpot migration cost and you will find price ranges that often do not say what they include or how they were worked out. A small Salesforce org with accounts, contacts, and a single sales process is a different project from one with custom objects, flows, Apex code, years of activity history, and a dozen connected tools. The same headline number cannot describe both.

This guide does not add another range. It shows what moves the cost, what you can count yourself before asking for a quote, and how to compare Salesforce to HubSpot migration pricing from different providers on the same terms. It treats the total as a HubSpot migration budget, not just the project fee.

What Determines Salesforce to HubSpot Migration Cost?

The total is rarely one line. It is made up of five budgets.

BudgetWhat it coversWhat often gets missed
Migration projectAudit, data mapping, automation rebuilds, testing, and go-live supportA pilot run and a reconciliation check
HubSpot subscriptionThe plan you need and the seats your team usesA plan that does not include custom objects, workflows, or custom field mappings when the design needs them
Internal team timeDecisions on what to keep, mapping approvals, and testingNobody counts it, so nobody plans for it
OverlapSalesforce and HubSpot running until the cutover is validatedThe Salesforce renewal date against your go-live date
ReserveRoom for issues found after the auditHaving none

Salesforce adds its own pressure points. Custom objects and custom fields all need a destination in HubSpot. Flows and Apex code are not on the list of what HubSpot’s Smart Transfer carries over, so they are rebuilt as part of the project. Leads, contacts, and person accounts all end up as HubSpot contacts, so the data model has to be decided before anything is loaded. Each one is a decision, and each decision has a cost.

Data Volume and Record Complexity

Volume affects how long extraction and checking take. Complexity affects how much design work the project needs. They are easy to confuse, and they move different parts of the budget.

Volume changes the schedule

Salesforce limits how often you can export your data. Weekly exports are available only in Enterprise, Performance, and Unlimited editions, and Professional and Developer editions get monthly automatic exports. The export is a set of CSV files in a zip archive, large exports are split into several files, and the zip files are deleted 48 hours after the notification email is sent. Attachments and files are included only if you select them. A large org therefore needs its extraction planned, not left to the last week.

If you extract through the API instead, the limit is a daily allowance for the whole org. Salesforce calculates it from your edition, the number of licenses, and any add-ons, and calls from managed packages count toward it. A migration that runs next to live integrations shares that allowance with them, so heavy extraction is paced.

On the HubSpot side, paid accounts can import files of up to 512 MB and 1,048,576 rows each, with up to 10,000,000 rows and 500 imports in a rolling 24 hours. Large orgs are split into files and sequenced, and the sequencing is project time.

Complexity changes the design work

Salesforce data is relational. Accounts, contacts, opportunities, and cases are linked by lookups, and Smart Transfer rebuilds the main ones as HubSpot associations: contact to company, deal to company, contact to deal through contact roles, and ticket to company and contact. Anything outside those links, such as lookups between custom objects, needs its own design.

Some Salesforce field types are not moved by Smart Transfer, including encrypted, calculated, reference, junction ID list, and master record fields. Formula fields need a decision: a HubSpot calculation property where the logic fits, or a report.

HubSpot also matches records differently. It deduplicates contacts by email address and companies by domain name, and an import without a unique identifier creates duplicates. Salesforce accounts without a website, and contacts without an email, need a plan before the import, because that is where duplicate and orphaned records come from.

Custom Objects, Associations, and Activity History

This part of the budget sits outside the standard objects.

Custom objects

HubSpot’s Smart Transfer does not support custom objects. In HubSpot, creating custom objects requires an Enterprise subscription, and each subscription has its own limits on objects, properties, and associations. Every Salesforce custom object is therefore one of three things: moved into HubSpot custom objects, folded into standard objects and properties, or left behind. The first needs the right plan and a separate load. The second needs a redesign.

Leads, contacts, and person accounts

Smart Transfer maps Salesforce leads, contacts, and person accounts to HubSpot contacts. HubSpot also has a leads object, which requires Sales Hub Professional or Enterprise. Which one you use depends on how your team qualifies leads today, so decide it before the load.

Activity history

Smart Transfer maps Salesforce tasks to tasks, events to meetings, email messages to email activities, and notes to notes. Attachments are transferred once after the sync and are not kept up to date. HubSpot’s import tool can create emails, meetings, notes, and tasks, but it cannot update the ones that already exist. A wrong load cannot simply be fixed by importing again, so the first load has to be right.

One more detail: after the initial sync, Smart Transfer keeps running in the background and is designed for a one-time migration. The cutover plan needs to say when it stops. HubSpot also warns that running Smart Transfer and the HubSpot-Salesforce integration at the same time creates duplicate records, because they match records on different identifiers, so pick one.

Integrations and Workflow Rebuilding

Salesforce rarely sits alone. Marketing automation, sales engagement, quoting, support, billing, and data warehouse tools are often connected to it, and each connection needs a decision: reconnect it to HubSpot, replace it, or retire it.

  • Flows and Apex code. These are rebuilt as HubSpot workflows or other automation. Count how many are active, and retire the ones nobody uses.
  • Validation rules and assignment logic. Each one has a purpose that has to be rebuilt as required properties, workflows, or ownership rules.
  • Managed packages and connected apps. Some will have a HubSpot connector, some will not, and some may need a paid plan on the other tool’s side.
  • Email and calendar sync. Reps who log email and meetings in Salesforce need the HubSpot equivalent set up before the cutover.
  • Reports and dashboards. These are rebuilt on HubSpot’s data model, starting with the ones leadership uses.

HubSpot documents workflows as available with Professional or Enterprise subscriptions. If the design depends on them and the plan does not include them, the plan itself is part of the cost.

Rebuilding is a chance to ask what each flow was meant to achieve, then rebuild that outcome. Copying the old logic step by step usually carries the old clutter with it. List every system that sends data to Salesforce or reads from it before you ask for a quote.

Internal vs. Partner-Led Migration Costs

Both are reasonable. The right one depends on what is in your org.

DIYPartner-led
Best whenStandard objects only, few flows, no custom objects, someone on your team knows HubSpotCustom objects, Apex code, several integrations, long activity history, or a tight go-live date
Cash costLower. Often only the tools and the HubSpot planHigher. You pay for scoping, rebuilds, testing, and support
Your timeHigh. You own mapping, cleanup, testing, and fixing mistakesLower. You review and approve
Main riskMissed associations, duplicate records, flows rebuilt without testingPaying for scope you did not need if the quote is not specific
DIY or partner-led: a quick check

HubSpot’s own Smart Transfer is one DIY route for Salesforce. Only Super Admins can run it, mapping your own custom Salesforce fields through it requires a Data Hub subscription, and it does not move custom objects. A DIY migration therefore still includes rebuilding work, and that is where the time goes.

Between a spreadsheet-and-import approach and a fully managed project there is a middle option: tool-assisted migration. A platform such as the SuprSwitch CRM migration tool analyzes the source CRM first, maps objects and fields, runs a pilot on a sample, and then migrates and validates the full dataset. A tool does not replace the decisions on scope and design, so those still need an owner.

If you are weighing HubSpot migration services against doing it yourself, compare your own hours against the quote, not the quote against zero.

How to Estimate Your Migration Budget

You can build a useful CRM migration cost estimate before you talk to anyone. Start by counting what is in your org.

What to countWhere to find itWhy it moves cost
Records per object: accounts, contacts, leads, opportunities, casesReports, or a record count per objectDrives extraction time and import batches
Custom objects and custom fields in useObject ManagerEach needs a destination, and custom objects need a HubSpot Enterprise plan
Active flows and Apex codeFlows and Apex classes in SetupRebuilt and tested one by one
Integrations and managed packagesInstalled Packages and connected appsReconnect, replace, or retire
Activity history: tasks, events, emails, notesActivity reportsLoaded once, and not updatable by import afterwards
Attachments and filesFiles and attachmentsTransferred once after the sync
Reports and dashboardsReports and Dashboards tabsRebuilt on the new data model
Users, including inactive ownersUsers in SetupRecords owned by inactive users need an ownership decision before import

Then work through four steps:

1. Decide what to leave behind. Inactive records, dead flows, and unused fields come off the list.

2. Choose the HubSpot plan. This is your recurring cost, and it should be set before the data moves.

3. List what must be rebuilt. Flows, reports, and integrations, each with a priority.

4. Ask for a scoped quote. Share the table above with each provider so they quote the same thing.

When quotes come back, compare what each one includes: automation rebuilds, a pilot migration, validation, activity history, attachments, and a support window after go-live. A lower quote that leaves several of these out is not lower.

Ways to Control Migration Costs

  • Export early. Salesforce export files expire after 48 hours and are limited by frequency, so plan the timing.
  • Protect your API allowance. Schedule heavy extraction away from your busiest integrations.
  • Run a pilot. A small test finds mapping problems while they are cheap to fix.
  • Check the renewal date. Do not let your Salesforce renewal force a choice between another term and a rushed cutover.

When to Get a Migration Assessment

An assessment is worth asking for when your org has any of these:

  • Custom objects, or data that does not fit HubSpot’s standard objects
  • Apex code, or a large number of active flows
  • Several integrations or managed packages
  • Years of activity history and attachments your team still needs
  • A fixed go-live date, such as a Salesforce renewal
  • Reports and dashboards that leadership depends on

A good assessment ends with a written scope: what moves, what is rebuilt, what stays behind, and which HubSpot plan the design needs. That document is what lets you compare quotes on the same terms. If you want a second opinion on yours, our CRM migration services are a place to start.

Conclusion

Salesforce to HubSpot migration cost is not one number. The fastest way to a reliable budget is to count what is in your org first and ask every provider to quote the same scope.

How SaaS Companies Use SuprSwitch to Move to HubSpot

A SaaS CRM migration doesn’t fail on the day you flip the switch. It fails two weeks later. A Customer Success manager opens HubSpot to pull a renewal list and finds the renewal dates never came over, because subscriptions lived in a Salesforce custom object that nobody mapped. The contacts are there. The deals are there. But the revenue picture is hollow.

I’ve watched this pattern play out across dozens of SaaS migrations. The problem is never record volume. A 60,000-contact Series B org and a 400,000-record enterprise org both break at the same place: mapping. SaaS teams run on data that lives between systems. Product usage events sit in the product database, subscription and MRR records sit in billing, and a trial-to-paid lifecycle spans all three. A migration that only moves Contacts, Companies, and Deals lands in HubSpot with no lifecycle context, orphaned subscription records, and deal stages that no longer describe how the business actually converts.

A suprswitch saas crm migration front-loads exactly these decisions. SuprSwitch uses a four-phase process to resolve the SaaS-specific mismatches in schema analysis and mapping logic, all before any live data moves. It completes the full migration in 3 to 4 days instead of the 3 to 6 weeks these projects usually drag into.[1]

Why SaaS CRM Migrations Break Where Others Don’t

Standard B2B migrations move three object types and call it done: Contacts, Companies, Deals. That works when your revenue model is linear. A rep opens a deal, closes it, and the deal amount is the revenue. SaaS breaks that assumption in three specific ways.

Product usage data has no native home in the CRM data model. SaaS teams track logins, feature adoption, seat counts, and activation events. That data almost never lives in the source CRM in a clean, mappable form. It lives in the product DB or a CDP. When teams move to HubSpot, they assume usage attributes come along. They don’t, unless the migration explicitly maps them to custom properties and decides what belongs on the Contact, what belongs on the Company, and what needs its own custom object.

Subscription and MRR records don’t map cleanly to Deals. In Salesforce or a homegrown CRM, subscriptions are usually a custom object carrying renewal date, billing frequency, and MRR. Force them into HubSpot Deals and you lose renewal tracking. Leave them out and you lose revenue history. That’s a mapping decision, not a copy-paste.

The trial-to-paid lifecycle breaks across stage mismatches. A typical SaaS lifecycle runs Signup, Activated, Trial, Paid, Expansion, Churn. It rarely aligns with a legacy CRM’s deal stages or HubSpot’s default lifecycle stages.[2] Migrate blindly and every record lands in the wrong stage, which breaks every downstream workflow and every report built on lifecycle stage.

These aren’t edge cases. They’re the defining features of a SaaS revenue model. And they’re exactly what a generic migration ignores.

The SuprSwitch SaaS CRM Migration: Four Phases in 3–4 Days

Most SaaS CRM migrations that stall for weeks aren’t slow because of data volume.[1] They’re slow because field mapping is done manually and iteratively, broken associations get discovered mid-run, and half the project timeline is post-migration cleanup. SuprSwitch moves the discovery and decision-making to the front, before any live data touches HubSpot.

Phase 1, Schema Analysis (Day 1). SuprSwitch scans the source CRM database and surfaces every custom field, record count, and property type. For a SaaS org, this is where the subscription objects, usage records, and Salesforce Lead tables get identified. It also flags the data-quality issues that would otherwise blow up mid-migration: duplicate self-serve contacts, empty required fields, and broken associations. Nothing moves in Phase 1. You get the full picture first.

Phase 2, Mapping Logic (Day 2). This is where the SaaS-specific decisions get made. The transformation layer maps legacy objects to the HubSpot data model: subscription object to a HubSpot custom object versus Deals, usage attributes to Contact versus Company properties, Salesforce Leads to Contacts with lifecycle stage logic, and trial-to-paid stages to HubSpot pipeline stages. Custom properties are created, association rules are defined, and ownership transfer logic is set. The mapping is reviewed and locked before the first record moves.

Phase 3, Pilot Validation (Day 2–3). SuprSwitch runs a pilot migration, a representative sample into HubSpot, to validate relational integrity, activity history formatting, field-level truncation, and association chains. If a usage field truncates or an association scatters, it gets caught here and fixed in the mapping layer, not after go-live.

Phase 4, Final Execution (Day 3–4). The full dataset runs through the migration engine with real-time record validation. If a record doesn’t appear in HubSpot within the expected window, it flags immediately. The retry mechanism re-runs failed records without restarting the full job. Every record is validated post-migration before go-live is confirmed.

Mapping Product Usage Data Into HubSpot’s Model

The first question every SaaS migration has to answer: where does usage data live in HubSpot? There’s no single right answer, and the wrong one shows up as unusable reports six months later.

Contact-level usage attributes like last login, individual feature adoption, and seat activation belong on the Contact record. Account-level rollups like total active seats, aggregate product engagement score, and plan tier belong on the Company. High-cardinality event data, a stream of usage records with timestamps, belongs in a HubSpot custom object associated to the Company, not crammed into a text property.

In Phase 2, SuprSwitch’s mapping logic is where you make these calls deliberately. The common failure here is truncation. Long JSON-style usage blobs or event strings from the product DB get cut off on field-level import when property types aren’t set correctly. That’s exactly the kind of issue pilot validation in Phase 3 catches. A truncated usage field in a 200-record sample is a five-minute mapping fix. The same field discovered after a 60,000-record go-live is a re-migration.

One clarification worth stating plainly: SuprSwitch maps any field or object that lives in the source CRM. Usage data that lives outside the CRM, in your product database or CDP, is a separate integration project, not a migration. Don’t assume a migration tool will reach into your product backend and pull event data that was never in the CRM to begin with.

Subscriptions and MRR: Deal, Custom Object, or Both?

This single decision determines whether renewal tracking survives the move. Subscriptions in a legacy CRM carry attributes that HubSpot Deals don’t model well: recurring billing frequency, renewal date, contract term, and MRR that persists across renewals rather than closing once.

If you map subscriptions to Deals, you get pipeline visibility but lose clean renewal tracking. A Deal closes and is done, while a subscription renews indefinitely. If you map them to a HubSpot custom object, you preserve renewal dates and MRR as first-class data but need to build the reporting around it. For most SaaS orgs I’ve migrated, the answer is a custom Subscription object for renewal and MRR tracking, with expansion and renewal opportunities modeled as Deals.

Here’s why association integrity mapping matters more in SaaS than anywhere else. A single Company can have multiple subscription records, multiple product-usage contacts, and multiple open deals, such as an expansion deal and a renewal deal at the same time. If those associations aren’t preserved during transfer, one company’s records scatter and the account view in HubSpot becomes unusable. SuprSwitch’s association integrity mapping keeps every subscription, usage contact, and expansion deal tied to the right Company through the migration.

Handling Salesforce Leads and Self-Serve Duplicates

PLG-heavy SaaS orgs carry huge Lead tables from self-serve signups, sometimes hundreds of thousands of them. HubSpot has no Lead object in the Salesforce sense.[2] These records have to be mapped to Contacts with lifecycle stage logic, and if that mapping is careless, they collide with existing Contact records and multiply duplicates.

SuprSwitch’s Phase 1 Schema Analysis flags duplicate self-serve contacts before the migration is designed. Phase 2 mapping logic then defines the dedup and lifecycle-stage rules. A Salesforce Lead that already exists as a Contact gets merged on a matching key rather than created as a second record, and its lifecycle stage is set based on where it actually sits in the trial-to-paid funnel.

The ownership problem compounds this. High rep turnover and PLG motions mean thousands of records owned by users who no longer exist in the system. Without a plan, those records either fail on import or land unowned, which breaks routing and forecasting the moment you go live. SuprSwitch’s ownership transfer engine resolves deactivated-user gaps before the migration runs, so records land with valid ownership instead of failing or orphaning.

Rebuilding the Trial-to-Paid Lifecycle Before You Migrate

Every workflow, report, and automation in your new HubSpot instance keys off lifecycle stage and pipeline stage. If those stages are wrong on day one, everything built on top of them is wrong too.

The work here is a stage-to-stage mapping, done in Phase 2 before any records move. Your legacy Signup, Activated, Trial, Paid, Expansion, and Churn stages get explicitly mapped to HubSpot lifecycle stages and deal pipeline stages. A trial user maps to a specific lifecycle stage, a paid conversion maps to Customer, and a churned account maps to a stage your CS workflows can act on.

Do this in the mapping layer and your workflows fire correctly the first time. Skip it and you spend the two weeks after go-live manually re-staging thousands of records while your automation misfires against them. The order matters. Get the lifecycle right before migration, not after.

Validating a SaaS Migration Before Go-Live

“Done” is not “the job finished running.” Done is “every record is confirmed in HubSpot, correctly associated, with no truncation or lost history.” Those are different claims, and the gap between them is where most post-migration support tickets come from.

During Phase 4, SuprSwitch’s real-time record validation flags any record that doesn’t appear in HubSpot within the expected window. It catches the problem during the transfer, not three weeks later in a CS complaint. The retry mechanism automatically re-runs failed records without restarting the entire job, which on a large SaaS org is the difference between a contained fix and a full re-run.

For SaaS IT and security buyers, one architectural detail matters: SuprSwitch’s no-storage architecture means customer data, including usage and billing data, is never held on SuprSwitch’s servers. That’s a meaningful distinction when the data in transit includes MRR and subscription records.

Conclusion

The reason SaaS migrations go wrong isn’t the size of the database. It’s that the data defining a SaaS revenue model, usage, subscriptions, and lifecycle, doesn’t map onto a standard Contacts-Companies-Deals migration. Move those three objects and ignore the rest, and you get a hollow HubSpot instance that can’t tell you who’s up for renewal or where an account sits in its lifecycle.

A suprswitch saas crm migration works because it moves the hard decisions to the front. Schema Analysis surfaces the subscription objects, usage records, and Lead tables on Day 1. Mapping Logic resolves them on Day 2. Pilot Validation proves the mapping on a real sample before the full run. And Final Execution validates every record in real-time, with a retry mechanism catching the failures that would otherwise become support tickets.

If you’re scoping a move to HubSpot, start with the schema, not the transfer. Know exactly which SaaS objects need custom mapping before a single record moves. That’s the difference between a migration that finishes in 3 to 4 days and one that drags into a six-week cleanup.

References

  1. HubSpot, “CRM Migration Best Practices and Data Import Guidelines,” HubSpot Knowledge Base, 2024.
  2. Salesforce Developer Documentation, “Lead and Contact Object Data Model Differences,” Salesforce Architect Resources, 2023.

SuprSwitch vs CSV Migration: Why Spreadsheets Break CRM Moves

Every failed CRM migration I’ve been called in to fix started the same way. Someone exported their CRM to CSV, imported it into HubSpot, checked that the record counts matched, and called it done. Three weeks later a rep opens a deal worth $80,000 and the contacts are gone. Reporting shows revenue with no associated company. A pipeline that held 200 deals now has 200 deals owned by nobody. And the source CRM, the one system that still held the relationships, was shut down nine days ago.

This is the core problem with a suprswitch vs csv crm migration comparison. It isn’t a comparison of two tools that do the same thing at different speeds. It’s a comparison of a flat-file transfer method against a relational transformation engine. A CSV moves rows. A CRM is not rows. It’s a web of associations between objects. That mismatch is where migrations die, and no amount of careful VLOOKUP work saves it at scale.

Let me walk through exactly what breaks, why record counts lie to you, and how treating migration as a relational problem instead of an import problem turns a 3 to 6 week ordeal into 3 to 4 days.

Why a CSV Can’t Represent a Relational CRM

A spreadsheet is flat. Each row is a self-contained record with no built-in sense of how it connects to any other row. That’s fine for a mailing list. It simply can’t represent a CRM.

Take a single deal. Deal #4471 belongs to Company X. It’s associated with three contacts: one is the Decision Maker, one is the Billing Contact, one is a technical influencer. It has 14 activities logged against it, a custom object record for the signed contract, and an owner. In HubSpot’s data model, that’s a set of associations with association labels connecting five different object types.

Now export that to CSV. What column holds “associated with three contacts under two different labels”? There isn’t one. The deal becomes a single row with an owner name and a company name as text strings. Every relationship it took part in is gone the moment it hits the spreadsheet.

The standard workaround is to export associations as a separate file and re-link records after import using record-ID matching. That means VLOOKUP against exported source IDs, or a custom script mapping legacy IDs to new HubSpot IDs. This works on a demo dataset. It falls apart on a real one, because HubSpot generates new internal IDs on import. So you end up maintaining a translation table between source IDs and destination IDs across every object type, then re-associating tens of thousands of records against it. One mismatched key and you’ve silently linked a deal to the wrong company.

What Actually Breaks: Associations, Activities, and Ownership

Matching record counts is the most dangerous kind of false confidence in a migration. You imported 50,000 contacts and HubSpot shows 50,000 contacts, so the migration “worked.” What the count doesn’t tell you is whether any of those contacts are still connected to anything.

Three data types consistently die in a CSV migration:

Associations. As covered above, these are the links between contacts, companies, deals, tickets, and custom objects. They’re the connective tissue of a CRM, and a CSV has no way to carry them. On a mid-size Salesforce org with 50,000 contacts, 15,000 deals, and 8,000 companies, rebuilding these associations by hand is where the real timeline lives. The data transfer takes a few hours. The association rebuild takes weeks.[1]

Activity and engagement history. Calls, emails, meetings, notes, and tasks. Here’s the part most people don’t discover until it’s too late. Even when you can export activities to CSV, HubSpot’s unified Activities model doesn’t accept them through the standard contact, company, or deal import. Salesforce stores activities as separate Tasks and Events objects, while HubSpot unifies them under one Activities timeline. A CSV import wizard has no transformation layer to reconcile that split. So you migrate the record and lose three years of context: every logged call, every email thread, every meeting note attached to it.

Ownership. Record owners who were deactivated in the source system, or whose user IDs don’t map to a HubSpot user, land as null or broken ownership after a CSV import. On a large org that’s easily thousands of orphaned records. Nobody notices until a rep asks why their pipeline is empty, because their deals imported with no valid owner and never showed up in their view.

The Object-Model Mismatches No CSV Can Reconcile

Beyond lost relationships, CSV imports break silently on structural differences between the source CRM and HubSpot. An import wizard maps columns to fields. It doesn’t transform an object model.

Salesforce Leads have no HubSpot equivalent. HubSpot has no Lead object. A Salesforce Lead is conceptually a Contact, sometimes a Contact plus a Company. Deciding how each Lead resolves is a transformation decision. A CSV import forces you to make it manually, in advance, in a spreadsheet, with no validation that you got it right.

Field truncation and type mismatches happen without an error. HubSpot enforces property character limits and property types. A 5,000-character notes field gets clipped on import. A picklist value that doesn’t match an existing HubSpot dropdown option gets dropped. A bulk CSV import doesn’t raise a row-level error the way real-time validation does. It just quietly lands partial data.[2]

A real migration isn’t one CSV, it’s many. You have separate exports for Contacts, Companies, Deals, Activities, Notes, and every custom object. Each has to be imported in dependency order: companies before contacts, contacts before deals, then re-linked. Every additional file multiplies the association-mapping surface area and the number of places a key can go wrong.

Where the “3-6 Weeks” Actually Comes From

When people say a CRM migration took six weeks, they almost never mean the data spent six weeks in transit. The transfer itself is fast. The weeks come from two things a CSV forces on you: manual field mapping up front, and manual association rebuild plus cleanup after import.[3]

Here’s the sequence that produces the timeline. You export. You build mapping spreadsheets. You import in dependency order. Record counts match, so you think you’re done. Then reporting looks wrong, so you start investigating. You find broken associations, orphaned owners, truncated fields, and duplicates. You go back to the source CRM to reconcile, assuming it’s still live. You re-import corrected batches. You rebuild associations by hand. Every fix surfaces two more problems, because you’re doing discovery in production, after go-live, on data that’s already partially broken.

The root cause is timing. In a CSV migration, you don’t discover the problems until the data is already in the destination and wrong. Discovery happens last, when it’s most expensive to fix. That inversion is the whole reason the timelines run long.

How SuprSwitch Handles a suprswitch vs csv crm migration as a Relational Problem

SuprSwitch treats migration as what it actually is, a relational transformation, and front-loads the discovery work so nothing gets found in production. It runs in four phases across 3 to 4 days.

Phase 1, Schema Analysis (Day 1). SuprSwitch scans the source CRM database and identifies every custom field, record count by object, property type, and data-quality issue: duplicates, broken associations, empty required fields. Nothing moves yet. This is the exact information a CSV export can’t give you until it’s already broken something in the destination.

Phase 2, Mapping Logic (Day 2). This is the transformation layer a CSV fundamentally lacks. SuprSwitch maps legacy objects to the HubSpot data model: resolving Salesforce Leads into Contacts and Companies, unifying split Tasks and Events into HubSpot Activities, creating the required HubSpot custom properties, and defining association rules before the first record moves. The ownership transfer engine resolves deactivated-user gaps here, so records land with valid HubSpot owners instead of orphaned nulls. Association integrity mapping preserves 1:1 and labeled relationships between objects instead of forcing a manual rebuild.

Phase 3, Pilot Validation (Day 2 to 3). A representative sample migrates to HubSpot first. This pilot migration validates relational integrity, activity history formatting, field-level truncation, and association chains against real records. Anything wrong gets fixed in the mapping layer, not in production after go-live. This is the step that eliminates the “three weeks later” failure pattern, because breakage surfaces on a sample before the full run.

Phase 4, Final Execution (Day 3 to 4). The full dataset runs through SuprSwitch’s migration engine with real-time record validation. If a record doesn’t appear in HubSpot within the expected window, it flags immediately rather than becoming a support ticket weeks later. The retry mechanism automatically re-runs failed records without restarting the entire job. Every record is validated after migration before go-live is confirmed.

The reason this compresses weeks to days isn’t faster data transfer. It’s that discovery and validation move to Day 1 and Day 2, before any live data moves. That’s the exact inversion of the CSV sequence.

Real-Time Validation vs. Discovering Breakage Three Weeks Later

The single biggest difference between the two approaches is when you find out something failed.

A CSV import that fails at row 38,000 of a 40,000-row file gives you a batch that partially succeeded and no clean way to know which records made it. You restart, or you manually reconcile what imported against what didn’t. And the failures that don’t stop the import, the truncated field, the dropped picklist value, the association that silently didn’t link, you don’t find at all until someone hits them in daily use.

Real-time record validation changes the timing. A failed record flags during transfer, not after. The retry mechanism handles transient failures automatically without touching the records that already succeeded. And because Pilot Validation already proved the mapping on a sample, the full run isn’t the first time you’re seeing whether associations hold. You’re validating a process you already tested, not discovering one in production.

When a CSV Is Actually Fine (and When It Isn’t)

I’ll be honest about scope, because overselling this helps no one. A CSV import is genuinely fine for a single-object, low-volume, low-relationship load. If you have 500 contacts with no deal history, no activity timeline, and no custom objects, just names, emails, and a couple of properties, export it, import it, move on. HubSpot’s native import handles that well, and reaching for a migration engine would be overkill.

A CSV stops being fine the moment relationships matter. Multiple object types. Association labels. Years of activity history. Custom objects. Deactivated users owning live records. Object-model mismatches like Salesforce Leads or split Activities. The instant your migration involves the connections between records, not just the records themselves, a flat file is the wrong instrument, and the cost shows up as weeks of cleanup instead of a clean cutover.

Conclusion

The suprswitch vs csv crm migration question isn’t really about speed, even though the timeline difference is stark. It’s about whether you’re using a tool that understands relationships. A CSV is a flat representation of a relational system, and that mismatch is the single root cause behind every broken association, lost activity timeline, and orphaned record I’ve been called in to untangle.

Matching record counts tells you the rows arrived. It tells you nothing about whether the deal still knows which company it belongs to, whether the contact still carries three years of call history, or whether the rep who owns the pipeline can actually see it. Those are the things that make a CRM worth migrating, and they’re exactly the things a spreadsheet drops on the floor.

SuprSwitch handles migration as the relational transformation it actually is: mapping object relationships, preserving association chains, resolving ownership gaps, and validating every record in real-time, with discovery front-loaded to the first two days so nothing gets found the hard way in production. Use a CSV when you’re moving a simple list. Use a migration engine when the connections between your records are the point.

References

  1. HubSpot, “Understand the association model between objects and records,” HubSpot Knowledge Base, 2024.
  2. HubSpot, “Set up your import file: property limits, field types, and troubleshooting import errors,” HubSpot Knowledge Base, 2024.
  3. HubSpot, “CRM migration best practices: planning, mapping, and validation,” HubSpot Solutions Partner Program resources, 2023.