Skip to main content

How to Compare HubSpot Onboarding Providers for a Salesforce or Dynamics Migration

Rob Ayala
Rob Ayala 13 min read Updated
Illustration of a project path: a winding road climbing soft hills to a flag at the summit, with numbered milestone pins along the road.

Compare HubSpot onboarding providers for a Salesforce or Dynamics 365 migration with a weighted 100-point scorecard, not a general checklist. Score each proposal on field and object mapping, history retention, parallel run and cutover, automation rebuild and post-launch guidance. Ask for written evidence under each criterion, deduct points for red flags, and check every plan against HubSpot's documented tool limits.

Key takeaways

  • Give the most weight to the two areas where a migration loses data: object and field mapping (25 points) and history retention (25 points).
  • HubSpot documents Smart Transfer as a one-time, one-way move and the HubSpot-Salesforce integration as ongoing two-way sync, and warns that running both at once creates duplicate records.
  • With a Smart CRM, Starter, Professional or Enterprise subscription, HubSpot file imports allow up to 10,000,000 rows per day on a rolling 24-hour period, so a large history load needs a day-by-day plan.
  • Microsoft's Power Platform documentation says that if the subscription for a tenant expires, the system marks production and sandbox environments for deactivation and eventual deletion, so the final export must finish before the license end date.
  • In the fictional worked example below, a Salesforce proposal scores 73 and a Dynamics 365 proposal scores 67, mainly because the Dynamics plan names no method for the parallel run.

What should a HubSpot onboarding proposal include when you leave Salesforce or Dynamics?

A migration proposal must show how your data, history, automation and users move out of the old CRM, how the two systems overlap, and what happens after launch. A standard onboarding plan with one import step is not a migration proposal.

Digitalegy is a HubSpot partner. If you want the general questions to ask any onboarding partner about experience, integration and support, start with 7 Questions to Choose a HubSpot Onboarding Partner. If you are still confirming that HubSpot is the right CRM, read Things You Should Know Before Implementing HubSpot first. The checks in this post sit on top of those.

A migration proposal should add five items to standard onboarding:

  • A field-level mapping file covering every object, record type, picklist and relationship you use.
  • A history plan that lists which activities, emails, notes, attachments and closed deals move, and with which tool.
  • A parallel run, cutover and rollback plan with dates.
  • An automation and integration inventory with an owner for each rebuild.
  • Post-launch guidance written into the contract.

Ask for a timeline too. HubSpot's page on switching from Salesforce says: "We typically see most businesses complete their migration process within three months." Treat that as a vendor benchmark, not a promise, and ask any provider whose plan is much longer or shorter to explain why. If your team is moving off Salesforce or Dynamics and wants an onboarding service for its HubSpot rollout, see Digitalegy's HubSpot onboarding page.

How do you score HubSpot onboarding proposals with a 100-point migration scorecard?

Rate each proposal from 0 to 5 on five migration criteria, convert each rating to points with the criterion's weight, and add them for a score out of 100. The weights below are a recommended starting point; shift them if, for example, you have no integrations to rebuild.

Score only what the proposal shows in writing. A promise made on a sales call scores zero until it appears in the statement of work.

Criterion (weight)Question to askEvidence a good proposal includesRed flags that cost points
Object and field mapping (25)Which HubSpot object and property receives each of our objects, fields, record types and picklist values?A mapping file with every field, its HubSpot target, data type and transformation rule"We map standard objects"; no word on custom objects or unsupported field types
History and activity retention (25)Which activities, emails, notes, attachments and closed deals move, with which tool, and what stays behind?A data inventory with record counts, a tool per data type and a day-by-day load planOne "import historical data" line; no plan for attachments or captured emails
Parallel run, cutover and rollback (20)How long do both systems run, what syncs during that time, and how do you undo a failed load?Dates for overlap, freeze and cutover, one sync method per phase, a written rollback stepTwo sync methods at once; cutover after the old license ends; no rollback
Automation and integration rebuild (15)Who rebuilds each workflow, validation rule, Apex trigger, Power Automate flow and integration?An inventory with an owner, a HubSpot replacement and a test case per item"Automations will be recreated" with no inventory or owner
Post-launch guidance (15)What happens in the first 90 days after go-live?Dated adoption checks, data quality reviews, admin training and a set number of support hoursSupport "as needed" with no hours, dates or named contact

Points = rating ÷ 5 × weight. A rating of 3 on mapping gives 3 ÷ 5 × 25 = 15 points. A suggested rule: send any proposal under 60 back for a second round of questions before you compare price.

How do you check whether a provider can map custom objects, record types, picklists and relationships?

Ask for the mapping file before you sign and test it against your five most customized objects. A provider who can map your data names the HubSpot target, data type and transformation for each field, and flags what the migration tool cannot move.

HubSpot's Smart Transfer guide says "With HubSpot Smart Transfer, you can move your data from other apps to HubSpot," and explains that the configuration step automatically creates HubSpot workflows to manage differences between the two data models. Ask the provider to list those workflows and what each one does. HubSpot's supported apps page for Smart Transfer also lists Salesforce field types that Smart Transfer does not support, so ask which of your fields fall in that list and how each will be handled.

Use this worksheet in your review call. All columns are suggested starting points to confirm against your own org and the provider's mapping file, not documented one-to-one mappings.

ConceptSalesforceDynamics 365HubSpot target to confirm
AccountsAccountAccountCompany records
OpportunitiesOpportunityOpportunityDeals, with a pipeline per sales process
Record typesRecord typeChoice column or business process flow (confirm with your admin)A pipeline or a dropdown property
PicklistsPicklistChoice columnDropdown property, mapped value by value
Custom objectsCustom objectCustom tableCustom object or properties on a standard object
RelationshipsLookup or master-detailLookup columnAssociations between records
ActivitiesTasks, events, emailsActivitiesActivities on the record timeline
WorkflowsFlows, ApexPower Automate flowsHubSpot workflows, rebuilt

Which data and history should move, and what can HubSpot's tools carry over?

Move open records, the closed deals your reports depend on, and the activity history people still use; keep the rest in a dated export. A good provider shows, data type by data type, which tool moves it and what it cannot carry.

Start with an inventory: record counts per object and activity type, plus the date range sales and finance still use. Then ask the provider to name the tool for each data type.

  • Attachments and similar data. The Smart Transfer guide says: "After your first sync, you can transfer additional data using one-time transfers for data types that aren't supported by data sync, such as attachments and segments." Schedule these one-time transfers after the freeze, and ask the provider how they will catch changes made after the transfer.
  • Salesforce activities. If the plan uses the HubSpot-Salesforce integration, HubSpot's activity sync guide says: "Turning on the sync will not automatically import all task data from Salesforce to HubSpot. Individual records will sync when they are created or updated in Salesforce." It adds that "Emails created in Salesforce using the Einstein Activity Capture tool don't sync to HubSpot," so ask how those emails move, if at all.
  • Dynamics 365 activities. Ask whether the provider will use Smart Transfer's data sync for Dynamics 365 activities and one-time transfers for attachments, and ask for activity type, count, tool and what stays in the archive.
  • Volume. For accounts with a Smart CRM, Starter, Professional or Enterprise subscription, HubSpot's import file guide allows imports of up to 10,000,000 rows per day, with a limit of 1,048,576 rows per file, and files up to 512 MB, on a rolling 24-hour period.
  • Audit fields. Ask where original created dates, owners and last-modified values will live in HubSpot, then spot-check five records after the test load.

Should you run Salesforce or Dynamics in parallel with HubSpot, and what cutover plan should a provider commit to?

Yes, but keep the overlap short and dated, use one sync method per phase, and get a written cutover and rollback plan. HubSpot itself describes a phased migration with both systems turned on.

HubSpot's switching page says its team moves businesses off Salesforce "by migrating in a phased approach while they have both systems turned on." The tools matter for how you do that. HubSpot's Salesforce integration guide states that "The HubSpot-Salesforce integration is designed for ongoing, two-way syncing between Salesforce and HubSpot," while the Smart Transfer guide says "HubSpot Smart Transfer is designed for a one-time migration of data from another app to HubSpot." The integration guide warns that the two use different unique identifiers, and using both at the same time creates duplicate records.

It also notes that "A single contact sync can take up to four API calls per record, but this number can vary," so ask for an estimate of daily API use against your Salesforce allowance during the overlap.

That integration guide covers Salesforce only. For Dynamics 365, ask which method keeps records current during the overlap, or whether the provider plans a hard cutover with a final delta load.

For rollback, HubSpot's revert guide says: "Any settings that were updated by the transfer will be removed. This includes properties, pipelines, users, currencies, and workflows." It also says: "If any records were created, they will be deleted." Treat revert as one step of the plan, not the whole plan. A freeze is the date after which no new fields or automation are added to the old CRM; a delta load moves only the records created or changed since the last load. A cutover plan worth signing lists:

  1. A freeze date for new fields and automation in the old CRM.
  2. A final delta load with record count checks.
  3. The date the old CRM becomes read-only for users.
  4. A rollback trigger: who decides, and by when.
  5. A fixed end to the overlap; a suggested limit is one month-end close.

How do automation, validation rules, Apex or Power Automate flows and integrations get rebuilt in HubSpot, and who owns that work?

Treat every automation as a rebuild with an owner. The provider should inventory each workflow, validation rule, Apex trigger, Power Automate flow and integration, name its HubSpot replacement, and say who builds and tests it.

The workflows Smart Transfer creates are there to manage data model differences, as the Smart Transfer guide describes them. Plan your own business rules as a separate line in the scope, so they are priced and tested.

A sound ownership split looks like this:

  • Your CRM admin exports the current automation list and marks each item keep, change or retire.
  • The provider proposes the HubSpot replacement (workflow, required property, pipeline rule or integration) and builds it.
  • Your sales or service lead signs off a test case for each item before cutover.

Integrations need the same treatment. HubSpot's switching page says: "If your data is too complex or custom, our APIs or 3rd party integrators can help." Ask the provider which integrations use a ready connector, which need custom API work, and who maintains each one after launch. If your migration needs custom integrations or technology integration work alongside onboarding, see Digitalegy's HubSpot implementation page.

What does a Salesforce or Dynamics to HubSpot migration cost and take, and what drives the price up?

HubSpot says it typically sees most businesses complete a migration within three months, and price follows scope. The sources cited here publish no price range, so compare proposals on the scope items that add hours, not on a headline fee.

Ask each provider to price the same scope list so the totals are comparable. These items usually add hours:

  • The number of custom objects, record types and picklist values to map.
  • Record and activity volume, plus attachments moved in separate one-time transfers.
  • The number of automations and integrations to rebuild.
  • The length of the parallel run and the number of delta loads.
  • Training seats, admin sessions and post-launch support hours.

If the provider loads this history through HubSpot's file import tool, volume sets a floor on load time. Suppose a fictional company has 25,000,000 activity rows. At the HubSpot import limit of 10,000,000 rows per day (Smart CRM, Starter, Professional or Enterprise), that is at least three rolling 24-hour periods. At 1,048,576 rows per file, it is at least 24 files (25,000,000 ÷ 1,048,576 = 23.8, rounded up). A proposal that books one day for a file import of this size has not done the arithmetic; if it uses another method, ask which one and what limits apply.

Hold the three-month figure from HubSpot's switching page loosely: it describes most businesses, not yours.

How do contract end dates, renewal notice periods and data export rights on the old CRM affect your timeline?

Work backward from the old CRM's contract end date. Cutover, the final export and a verified backup must finish before access lapses, and the renewal notice period sets the date you must decide by.

Salesforce. Salesforce Trailhead's data export module says: "Data export tools provide a convenient way to obtain a copy of your Salesforce data, either for backup or for importing into a different system." It also says "Weekly exports are available in Enterprise, Performance, and Unlimited Editions," so confirm which edition you run before you count on a weekly backup during the overlap.

Dynamics 365. Microsoft Learn's guide to automatic environment cleanup says that if the subscription for a tenant expires or is deprovisioned, the system marks all environments for deactivation and eventual deletion. Admins get emails 14 days, 7 days and 1 day before an environment is disabled, and the system deletes it 10 days after the final email if no action is taken. That is 23 days from first warning to deletion. Only production and sandbox environments are affected by this subscription-based cleanup.

Build the timeline backward from the end date:

  1. Contract end date.
  2. Verified full export stored outside the old CRM, at least two weeks before.
  3. Cutover and final delta load before that.
  4. Non-renewal notice sent by the date your order form requires.

Ask each provider to put these dates in the proposal.

What post-launch guidance should be in the contract?

Write adoption checks, data quality reviews, admin training and a set number of support hours into the statement of work, each with a date and an owner. HubSpot's description of a partner-led migration ends with training, which is the floor to hold a provider to.

HubSpot's switching page describes its partner-led option this way:

A partner recommends an overall solution design and sets it up. The partner teaches and trains you to support the system.

Turn that into contract terms:

  • Adoption checks: logins and logged activities by team, weekly for the first month.
  • Data quality reviews: duplicates, records without owners and missing associations, at 30 and 90 days.
  • Admin training: named admins, number of sessions and a handover of the mapping file and automation inventory.
  • Support hours: a number, a response time and an end date.

A proposal that lists all four with dates earns full points on this criterion. If you want process optimization and RevOps support after the move to HubSpot, see Digitalegy's revenue operations page.

What are the biggest red flags, and how do two sample proposals score?

The costliest red flags are a missing mapping file, a history plan that names no tool, two sync methods running at once, and a cutover date after the old license ends. In the fictional example below, those gaps explain the difference between the scores.

Fictional example. Both proposals are invented to show the method. There is no real client, provider, price or metric.

Criterion (weight)Proposal A: Salesforce to HubSpotProposal B: Dynamics 365 to HubSpot
Mapping (25)4/5 = 20. Full field file; no plan for unsupported Salesforce field types.3/5 = 15. Custom tables mapped; choice values not mapped one by one.
History (25)3/5 = 15. Attachments in a one-time transfer; no answer on Einstein Activity Capture emails.4/5 = 20. Day-by-day load plan within import limits; notes and attachments listed.
Parallel run and cutover (20)5/5 = 20. Integration for the overlap, Smart Transfer connections off first, written revert step.2/5 = 8. No sync method for the overlap; cutover set after the license end date.
Automation (15)2/5 = 6. "Workflows will be recreated"; no Apex inventory.3/5 = 9. Power Automate inventory; no owner per flow.
Post-launch (15)4/5 = 12. Training and a 90-day review; support hours unstated.5/5 = 15. Dated reviews, named admins, fixed hours.
Total7367

The source CRM shapes the gaps. Proposal A can point to HubSpot's documented two-way Salesforce integration for the overlap, so its risk sits in history and automation. Proposal B wins on history and post-launch but loses 12 points on cutover, because it names no method for keeping records current during the overlap and sets cutover after the license end date, which Microsoft's environment deletion schedule makes risky. Send each provider its weakest criterion as a written question and re-score. If you want to talk through your migration plan before you sign a provider, book a strategy consultation.

Frequently asked questions

Can HubSpot Smart Transfer send data back to Salesforce or Dynamics?

No. HubSpot's Smart Transfer guide says "The transfer is one-way from other apps to HubSpot." Anything you need to keep in the old system must stay there or live in your own export.

How long does the first Smart Transfer sync take?

HubSpot's Smart Transfer guide says it "can take several hours to complete depending on the volume of data." Schedule it outside working hours and well before your freeze date.

Who should own the mapping file after launch?

Your CRM admin. Ask the provider to hand it over in an editable format with the automation inventory, and update it whenever a property, pipeline or integration changes.

Do we need our Salesforce or Dynamics admin during the migration?

Yes. Someone who knows your record types, validation rules and integrations has to answer the mapping questions, approve the automation inventory and sign off test cases. Book that person's time in the project plan.

Should the scorecard weights change for a simple migration?

They can. If you have no integrations and few automations, move points from automation rebuild to history retention. Keep the total at 100 and use the same weights for every proposal you compare.

Sources

  1. Switching from Salesforce to HubSpot, HubSpot
  2. Transfer data from other apps using HubSpot Smart Transfer, HubSpot (November 10, 2026)
  3. Supported apps for HubSpot Smart Transfer, HubSpot (November 10, 2026)
  4. Sync activities and tasks between HubSpot and Salesforce, HubSpot (July 29, 2026)
  5. Format import files, HubSpot (November 12, 2026)
  6. Connect HubSpot and Salesforce, HubSpot (November 5, 2026)
  7. Revert a transfer in HubSpot Smart Transfer, HubSpot (November 26, 2025)
  8. Learn Data Export Methods and Steps for Salesforce, Salesforce Trailhead
  9. Automatic deletion of Power Platform environments - Power Platform, Microsoft Learn (October 8, 2026)

Want help putting this into practice?

Don't forget to share this post!

Rob Ayala

Rob Ayala

CEO & Founder

Related posts

HubSpot Implementation Revenue Operations

HubSpot Adoption Metrics to Track in the First 90 Days After Go-Live

Rob Ayala
HubSpot Revenue Operations Implementation

How to Consolidate a RevOps Tool Stack Around HubSpot as Your System of Record

Rob Ayala
HubSpot Implementation Revenue Operations

[Webinar] Does Your Company Need HubSpot? Everything You Need to Know!

Ana Victoria Cu