---
title: "Salesforce to HubSpot Migration: Field Mapping & Cutover Plan"
description: Plan your Salesforce to HubSpot migration with object mapping, source IDs, activity-history checks, automation testing, and a controlled cutover.
image: https://unleashtechworx.com/hubfs/Blog%20header%201536x1024@1x%20%283%29.png
---

[![logo](https://unleashtechworx.com/hubfs/logo.png)](https://unleashtechworx.com/)

- [Home](https://unleashtechworx.com/)
- [About](https://unleashtechworx.com/about-us)
- Careers 
  
    - [Join The Team](https://unleashtechworx.com/careers)
    - [HubSpot Bootcamp](https://unleashtechworx.com/hubspot-bootcamp)
- Solutions 
  
    - [Services](https://unleashtechworx.com/solutions)
    - [CRM Setup](https://unleashtechworx.com/service-crm-setup)
    - [Consulting Services](https://unleashtechworx.com/service-consulting-services)
    - [Marketing Automation](https://unleashtechworx.com/service-marketing-automation)
    - [Service Automation](https://unleashtechworx.com/service-service-automation)
- [Success Stories](https://unleashtechworx.com/success-stories)
- Tools 
  
    - [RevOps Calculator](https://revops.unleashtechworx.com/)
    - [Business Case Builder](https://businesscase.unleashtechworx.com/)
    - [ROI Calculator](https://roi.unleashtechworx.com/)
- [Blogs](https://unleashtechworx.com/unleash-blogs)
- [FAQ's](https://unleashtechworx.com/faq)
- [Contact Us](https://unleashtechworx.com/contact-us)

[Home](https://unleashtechworx.com/)/[Blogs](https://unleashtechworx.com/blogs)/Salesforce to HubSpot Migration: Field Mapping & Cutover Plan

# Salesforce to HubSpot Migration: Field Mapping & Cutover Plan

Article · 10 min read

November 6, 2026 · By Ranjith Kumar S, CRM Implementation Consultant, [Unleash Tech Worx](https://unleashtechworx.com/)

A migration can finish with the right record count and still leave your team missing customer context. Opportunities arrive without contact relationships, activities show the wrong dates, and automation acts on incomplete records. Moving rows is only part of the work.

A Salesforce-to-HubSpot migration needs an agreed data model, reliable source identifiers, tested transfer methods, and reconciliation before cutover. Define what must move, how it should behave, and who signs off before you start loading production data.

This guide covers field mapping, activity history, automation rebuilds, and an illustrative Friday–Monday cutover. It follows the Diagnose, Design & Build, Optimize approach in our [HubSpot implementation process](https://unleashtechworx.com/en/unleash-blogs/the-hubspot-implementation-process-explained-diagnose-design-build-optimize).

![Blog header 1536x1024@1x (3)](https://unleashtechworx.com/hs-fs/hubfs/Blog%20header%201536x1024@1x%20(3).png?width=1536&height=1024&name=Blog%20header%201536x1024@1x%20(3).png)

## 1. Define Your Migration Scope and Acceptance Criteria

Start with an inventory of Salesforce objects, relationships, fields, and active processes. Decide what to migrate, archive, transform, or exclude, with a named owner for each decision.

- Count Accounts, Contacts, Leads, Opportunities, Cases, and relevant custom objects.
- Inventory Tasks, Events, notes, emails, files, and their relationship structure.
- Record owners, record types, pipelines, picklists, currencies, and date formats.
- List active Flows, assignment rules, Apex logic, and connected systems.
- Document retention requirements and the reports needed after migration.

Do not retire fields solely because they are old or sparsely populated. Check business use, dependencies, and retention obligations first. An occasional field may still support an important customer or compliance process.

Agree acceptance criteria around expected counts, required values, associations, activity coverage, and representative user scenarios. Our [CRM data migration strategy](https://unleashtechworx.com/en/unleash-blogs/before-you-import-crm-data-migration-strategy-for-a-successful-crm-implementation) explains why these decisions belong alongside CRM design.

## 2. Map Salesforce Objects and Fields

Map objects according to their business purpose and the target HubSpot data model. Salesforce Leads and Contacts commonly become HubSpot contacts; HubSpot also has a separate Leads object, which serves a different prospecting process.

| Salesforce source | HubSpot destination | Mapping decision |
| --- | --- | --- |
| Users and record owners | Users and owners | Map to appropriate active users. Reassign departed staff’s records rather than recreating unnecessary accounts. |
| Accounts | Companies | Select domain or a supported unique identifier; account for shared domains and parent–child relationships. |
| Contacts and Leads | Contacts | Reconcile overlapping identities and preserve relevant source status and IDs. |
| Opportunities | Deals | Map pipeline, stage, currency, amount, owner, and relevant company/contact relationships. |
| Cases | Tickets | Prepare supported ticket pipelines, statuses, owners, and relationships. |
| Custom objects | Suitable standard or custom objects | Assess fit first. HubSpot custom objects require an eligible Enterprise subscription. |
| Tasks, Events, notes, emails, call records | Corresponding activities where supported | Validate the extraction and loading method, required fields, dates, ownership, and associations. |

### Build a Field-Level Mapping Workbook

For each source field, record the target property, data type, transformation, options, identifier role, and exclusion reason if it will not migrate. Include these decisions:

- **Picklists:** Map source values to existing target options; format multi-select values for the selected import method.
- **Record types:** Decide whether they become pipelines, properties, or another structure rather than copying them mechanically.
- **Stages and statuses:** Retain original values in reference properties when useful and document the approved target equivalents.
- **Dates and currencies:** Confirm formats, time zones, currency handling, and reporting assumptions.
- **Products and line items:** Plan pricing, quantities, and deal relationships as a distinct dependency-aware workstream.

Clean confirmed duplicates and inconsistent values before the production load. Our [duplicate-record guide](https://unleashtechworx.com/en/unleash-blogs/how-to-find-and-merge-duplicate-records-in-hubspot) explains HubSpot merge precautions for reviewing the destination; apply Salesforce-specific controls when cleaning the source.

## 3. Preserve Source IDs, Dates, and Associations

Keep Salesforce identifiers and a source-to-target ID crosswalk so your team can trace records, reconcile batches, and retry supported updates safely. Use the 18-character Salesforce ID where available to reduce case-sensitivity problems in spreadsheets.

For supported objects, configure a custom text property to require unique values and explicitly select it as the file-import matching key. This does not change the Salesforce connector’s own matching rules. Contact email uniqueness still applies when you use a custom import identifier.

Check the source and destination module when several record types feed one object. Merged identities may correspond to multiple Salesforce IDs, so define a canonical matching key and retain the additional IDs in your crosswalk rather than discarding traceability.

- Carry Account IDs for the relevant contact and opportunity relationships.
- Preserve contact roles and other relationship evidence where needed.
- Resolve activity parent IDs to the intended HubSpot records.
- Distinguish source identifiers from HubSpot Record IDs in files and logs.

Store original Salesforce timestamps in suitable custom date properties when necessary. Confirm separately whether your chosen transfer path can populate native HubSpot dates. Do not assume native Create date always preserves the source date or always equals import time.

Association imports need the identifiers and structure supported by the selected method. Review HubSpot’s [import-file requirements](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file), then test repeated updates and multi-record relationships before a full load.

## 4. Plan Activity History and Files Separately

Validate each activity type independently because emails, meetings, notes, tasks, and calls have different fields and update behavior. An activity count alone does not confirm that dates, content, or relationships are usable.

| Salesforce history | Potential HubSpot destination | Validation focus |
| --- | --- | --- |
| Tasks | Tasks | Title, due date, owner, status, and associations; existing tasks cannot be updated through file import. |
| Events | Meetings | Description, start/end times, owner, and relationships; existing meetings cannot be updated through file import. |
| Call logs | Calls | Notes, activity date, owner, and supported outcome fields; calls can support import updates using the required identifiers. |
| Notes | Notes | Body, activity date, and relationships; existing notes cannot be updated through file import. |
| Email messages | Logged email activities | Body, direction, dates, and associations; existing emails cannot be updated through file import. |
| Files and attachments | Files and supported record links | Separate extraction, upload, permissions, and linking; not automatically covered by an activity CSV. |

HubSpot can create records and associated activities together in supported multi-object imports. Loading parent records first is often easier to reconcile at scale, but it is not a universal platform requirement.

Set activity dates explicitly where supported; otherwise imported activity dates may default to the import time. Validate owner assignments and the timelines on which activities appear. Log successful batches so retries do not recreate activities that the selected import method cannot update.

Choose history coverage from operational and retention requirements rather than an arbitrary age limit. Preserve the customer evidence your team needs.

## 5. Choose the Connector, Imports, or APIs

Choose transfer methods based on supported scope, control, reconciliation, and the intended system of record. Do not rule out the Salesforce integration automatically or assume it covers the full migration.

- **Salesforce integration:** Supports Salesforce record imports and supported activity synchronization. Review object coverage, filters, matching rules, sync direction, and historical-activity limits.
- **File imports:** Useful for structured, auditable batches with explicit mapping and error review.
- **APIs or specialist tooling:** Consider when extraction, transformations, relationship complexity, or history requires capabilities beyond the chosen standard path.

If both systems remain active, document which one owns each field and process. Limit unintended record creation and outbound automation before syncing. A parallel run needs conflict management, not simply two connected CRMs.

Check HubSpot’s [import-file formats](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file) and [Imports API](https://developers.hubspot.com/docs/api-reference/latest/crm/imports/guide) requirements when selecting your transfer method.

Use a representative pilot covering complex relationships, former owners, unusual values, and history-heavy records. Choose the sample around your data’s complexity rather than a fixed percentage.

## 6. Rebuild and Test Automation

Review Salesforce automation by business outcome, then design and test the HubSpot replacement. Flows, Apex code, and validation rules do not become equivalent HubSpot logic merely because their records migrate.

| Salesforce behavior | Potential HubSpot approach | Check before rebuilding |
| --- | --- | --- |
| Record-triggered Flow or Process Builder | Workflow triggers, branches, and actions | Object support, timing, exclusions, and re-enrollment. |
| Scheduled Flow | Supported scheduled or date-based automation | Scheduling behavior and subscription availability. |
| Assignment and routing | Owner updates or supported rotation actions | Eligibility, fallback owners, and licensing. |
| Email alerts | Internal notifications or appropriate email actions | Recipients, email type, consent, and suppression requirements. |
| Validation rules | Supported validation, required properties, or process controls | Rule scope and entry paths; do not assume identical enforcement. |
| Apex and custom integrations | Workflow actions, supported custom code, or external integration logic | Complexity, execution limits, failure handling, and feature availability. |

Inventory owners and dependencies before retiring old rules. Unexplained logic needs investigation, not automatic deletion. Document what the business still requires and who approves the replacement.

Build automation without exposing live customers to test actions. Use HubSpot’s [workflow testing tools](https://knowledge.hubspot.com/workflows/test-your-workflow) for simulated paths, then controlled end-to-end scenarios where required. Confirm that existing records will not be enrolled unintentionally at activation.

## 7. Run a Controlled Cutover

Use a cutover window sized around your tested load duration, integrations, and operational needs. This Friday–Monday example assumes the pilot and baseline load are complete; it is not a delivery or zero-downtime guarantee.

### Before Friday: Agree Readiness and Fallback Criteria

Sign off the mappings, pilot results, final-change scope, user readiness, and named owners. Define critical failures that stop launch, how to capture changes during a pause, and how work would resume in the agreed system of record.

### Friday: Freeze Writes and Capture Final Changes

Freeze or tightly control Salesforce writes, including integration writes. Capture secure reference exports and extract the changes since the baseline. Reconcile created and updated records, source deletions or exclusions, and changed relationships; an updated-record export may not capture them all. An export is not a complete rollback mechanism.

### Saturday: Load and Reconcile the Final Batches

Load incremental changes in dependency order, then activity and file updates through validated paths. Reconcile each batch with its expected scope and inspect errors before continuing. Avoid repeating a baseline load that is already complete.

### Sunday: Validate, Decide, Then Activate

Complete validation and hold the go/no-go decision **before** redirecting live traffic or enabling production automation. After approval, switch forms and integrations, disable corresponding Salesforce actions, and activate tested HubSpot processes in a controlled sequence.

If readiness criteria fail, follow the fallback plan. Read-only Salesforce alone does not undo HubSpot writes or changes made in connected systems; reconcile those changes explicitly before resuming elsewhere.

### Monday: Support Users and Monitor Processing

Provide a named support route for each team. Check new records, assignments, activity logging, workflow errors, and integrations frequently during the initial support period. Retain source access for an agreed period based on operational, contractual, and retention needs.

## 8. Validate Results and Support Adoption

Validate after every batch and again before and after cutover. Reconcile against the signed-off scope, allowing for documented exclusions, merged identities, and mapping transformations.

- **Counts:** Explain every difference between expected source scope and destination records.
- **Field samples:** Include simple, complex, old, new, and exception records.
- **Associations:** Verify the relationships relevant to each customer and opportunity; investigate unexplained orphans.
- **Ownership:** Confirm accountable active owners and documented exceptions.
- **Pipelines:** Reconcile stages, amounts, currencies, and close dates under agreed definitions.
- **History:** Check activity content, dates, owners, and the correct timelines.
- **Communication preferences:** Confirm that email opt-outs, subscription preferences, and required consent evidence are preserved. Migrated contacts are not automatically eligible for marketing.
- **Duplicates:** Investigate unintended copies and source-ID gaps.
- **Automation:** Confirm both intended actions and excluded scenarios.
- **Reports:** Compare agreed totals using aligned dates, filters, currencies, and scope.

Maintain a sign-off log with evidence, owners, and unresolved exceptions. Our [HubSpot portal audit checklist](https://unleashtechworx.com/en/unleash-blogs/hubspot-portal-audit-checklist-25-checks-to-find-revenue-leaks) can structure follow-up reviews after launch.

Train users on daily tasks, not just navigation. Review adoption and feedback as part of [HubSpot implementation and onboarding](https://unleashtechworx.com/service-hubspot-crm-implementation). Retire Salesforce only when the business, integration, and retention requirements have been met.

## Build Your Salesforce Migration Plan

Unleash Tech Worx provides CRM migration and integration services alongside pipeline configuration, automation, and team training. Plan the mappings and acceptance criteria before committing to a cutover date.

Bring your object inventory, approximate volumes, customizations, history requirements, and connected-system list to the discussion. Agree what moves, how it will be tested, and who owns each decision.

**[Request a Salesforce migration plan](https://unleashtechworx.com/contact-us)**

Want this handled, not just explained?

Book Demo

Related

## Where to go from here

### [HubSpot CRM Implementation Set up HubSpot right the first time—configured for your process and designed for adoption. Learn more →](https://unleashtechworx.com/service-hubspot-crm-implementation)

### [RevOps as a Service An ongoing team to keep your CRM clean, adopted, and actually driving decisions. Learn more →](https://unleashtechworx.com/service-revops-as-a-service)

#### Company

- [About us](https://unleashtechworx.com/about-us)
- [Insights](https://unleashtechworx.com/unleash-blogs)
- [Careers](https://unleashtechworx.com/careers)
- [Contact](https://unleashtechworx.com/contact-us)

#### Services

- [HubSpot Implementation](https://unleashtechworx.com/solutions)
- [CRM Migration](https://unleashtechworx.com/solutions)
- [RevOps as a Service](https://unleashtechworx.com/solutions)
- [CRM & ERP Service](https://unleashtechworx.com/solutions)

#### Migrations

- [Salesforce to HubSpot](https://unleashtechworx.com/service-salesforce-to-hubspot-migration)
- [Zoho to HubSpot](https://unleashtechworx.com/service-zoho-to-hubspot-migration)
- [Pipedrive to HubSpot](https://unleashtechworx.com/service-pipedrive-to-hubspot-migration)

#### Regions

- [HubSpot Partner India](https://unleashtechworx.com/contact-us#offices)
- [HubSpot Partner USA](https://unleashtechworx.com/contact-us#offices)

![footer\_logo-1](https://unleashtechworx.com/hubfs/footer_logo-1.png)

### Let's get in touch!

[contact@unleashtechworx.com](mailto:contact@unleashtechworx.com) [India +91 8792280333](tel:+91%208792280333) [USA +1 (650) 668-0855](tel:+1%20(650)%20668-0855)

[![](https://unleashtechworx.com/hubfs/social-facebook.png)](https://www.facebook.com/unleashtechworx) [![](https://unleashtechworx.com/hubfs/social-instagram.png)](https://www.instagram.com/unleashtechworx/) [![](https://unleashtechworx.com/hubfs/social-linkedin.png)](https://www.linkedin.com/company/unleash-techworx/)

©  Unleash Tech Worx. All rights reserved.

×

### Book your Revenue Diagnostic call

Pick a day and time that works for you — you'll get an instant confirmation.

↑

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Ranjith Kumar S",
    "url" : "https://unleashtechworx.com/en/unleash-blogs/author/ranjith-kumar-s"
  },
  "dateModified" : "2026-11-06T12:48:02.264Z",
  "datePublished" : "2026-11-06T12:48:02.000Z",
  "headline" : "Salesforce to HubSpot Migration: Field Mapping & Cutover Plan",
  "image" : [ "https://unleashtechworx.com/hubfs/Blog%20header%201536x1024@1x%20%283%29.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://unleashtechworx.com/en/unleash-blogs/salesforce-to-hubspot-migration-field-mapping-cutover-plan",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://unleashtechworx.com/hubfs/IMG_0817-2.png"
    },
    "name" : "Unleash Tech Worx Pvt Ltd"
  }
}
```