---
title: "Sharpspring to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Sharpspring to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/sharpspring/to/hubspot"
---

# Sharpspring to HubSpot migration

Moving from SharpSpring to HubSpot means stepping from a contact-based marketing automation platform into HubSpot's hub-based CRM model — where lifecycle\_stage, deal pipelines, and custom properties live inside one unified system. FlitStack AI maps every SharpSpring contact, company, deal, and activity into HubSpot's CRM, preserving original create dates and owner assignments while surfacing the configuration work your team needs to rebuild HubSpot's automation layer from scratch.

Short answer

FlitStack AI migrates contacts, companies, deals, contact / engagements and custom objects from Sharpspring to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/sharpspring/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Sharpspring ![](https://flitstack.ai/platforms-trim/sharpspring.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact Company Deal Contact / Engagement Custom Object

Mapped field by field · sample run · one-click rollback

## What moves from Sharpspring to HubSpot?

SharpSpring organizes its CRM around contacts, companies, and deals with a visual workflow builder for automation campaigns and a VisitorID module for anonymous visitor tracking.

Read the full summary

HubSpot structures its CRM around contacts (with a unified contact record that absorbs company data), deals mapped to pipeline stages, and a lifecycle\_stage property that tracks a contact's progression from lead to customer. The migration carries all standard SharpSpring objects — contacts, companies, deals, activities, notes, attachments — into HubSpot's equivalent records. SharpSpring's visual automation workflows (tree-based logic with branching and scoring) do not migrate; they require a complete rebuild in HubSpot's workflow editor or a third-party automation layer. HubSpot's lifecycle\_stage replaces SharpSpring's stage-based contact progression, and SharpSpring's lead scoring migrates as a custom number property on the contact record. Custom fields that have no HubSpot equivalent become HubSpot custom properties created during setup. FlitStack sequences the migration as: export from SharpSpring API, map to HubSpot objects, create custom properties in HubSpot first, import contacts and companies, then deals with pipeline mapping, then activities, then a delta-pickup window captures any records modified during the cutover.

direct

### Contact → Contact

SharpSpring contacts map 1:1 to HubSpot contacts.

How it maps

The primary company association migrates as a HubSpot company association. Contacts without a company are created as standalone HubSpot contacts. Original SharpSpring create dates are preserved as a custom datetime field since HubSpot's native CreatedDate reflects the migration timestamp.

custom\_field\_required

### Contact (scoring data) → Contact (hs\_lead\_score)

SharpSpring lead scores (fit + engagement) migrate as a custom numeric property on the HubSpot contact record.

How it maps

FlitStack creates the custom property during setup. No native HubSpot equivalent exists for SharpSpring's separate lead scoring page, so the score is stored as a static value at migration time — ongoing scoring requires rebuilding in HubSpot workflows.

transformed

### Contact (stage from workflow) → Contact (lifecycle\_stage)

SharpSpring contact stages are tracked via workflow membership and list membership rather than a single property.

How it maps

FlitStack maps the most-recent workflow-exited stage to HubSpot's lifecycle\_stage pick-list (subscriber, lead, MQL, SQL, opportunity, customer). Stage transitions that SharpSpring tracked over time become a single lifecycle value in HubSpot; original stage history is preserved in a custom audit field.

direct

### Company → Company

SharpSpring companies map to HubSpot companies.

How it maps

Company domains, industry values, employee counts, and annual revenue migrate as HubSpot company properties. SharpSpring parent-child company hierarchies map to HubSpot's associated company relationships. Multi-company associations on SharpSpring contacts collapse to the primary company association in HubSpot.

direct

### Deal → Deal

SharpSpring deals map to HubSpot deals.

How it maps

Each SharpSpring deal pipeline maps to a named HubSpot pipeline. Deal stage names are mapped value-by-value to HubSpot stage names within the corresponding pipeline. Deal amount, close date, owner, and custom deal fields migrate directly. Unmapped custom deal fields require HubSpot custom deal properties created during setup.

direct

### Form Submission → Contact (form\_submissions)

SharpSpring form submission events — which form was filled, submission date, and field values — migrate as engagement notes on the HubSpot contact record.

How it maps

Form names and submission timestamps are preserved. Field values from SharpSpring forms that map to known HubSpot contact properties are migrated to those properties; unmapped fields are stored in custom properties on the contact.

******What moves 12 objects

Sharpspring HubSpot

- Contact Contact 1:1
- Contact Contact transformed
- Contact Contact transformed
- Company Company 1:1
- Deal Deal 1:1
- Form Submission Contact 1:1

\+ 6 more in the mapping below

## How Sharpspring and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension             | Sharpspring                                                                                                                                                   | HubSpot                                                                                                                                                                          |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Lead scoring model    | SharpSpring uses a separate lead scoring page with fit and engagement dimensions, managed outside the contact record                                          | HubSpot uses a native contact property (hs\_lead\_score) that appears on every contact record and drives list segmentation                                                       |
| Lifecycle stage       | SharpSpring tracks contact stages through workflows and list membership — no single property maps lifecycle across the full journey                           | HubSpot lifecycle\_stage is a built-in pick-list property (subscriber, lead, MQL, SQL, opportunity, customer) with stage-change timestamps tracked automatically                 |
| Automation logic      | SharpSpring visual workflow builder stores branching conditions, time delays, and scoring actions inside the platform — exported as workflow definitions only | HubSpot workflows are separate objects with triggers, conditions, and actions defined inside HubSpot's editor — no automation data carries over on migration                     |
| Visitor tracking      | SharpSpring VisitorID captures anonymous visitor data and correlates it with contacts based on email — stored within SharpSpring's tracking module            | HubSpot tracks page visits and link clicks natively on contact records via the HubSpot tracking code — no equivalent to SharpSpring's VisitorID correlation model                |
| Custom object model   | SharpSpring supports custom fields on standard objects and stores custom objects with their own property sets accessible via the API                          | HubSpot Custom Objects are available on Enterprise-tier accounts only and require creation in Settings → Objects before data can import                                          |
| Pipeline structure    | SharpSpring deals belong to a single pipeline with stage values; pipeline name and stage names are separate properties                                        | HubSpot deals belong to named pipelines with stage values tied to that pipeline; multiple pipelines are supported natively with pipeline-level settings for deal creation access |
| Email template assets | SharpSpring stores email templates as platform assets with images hosted on SharpSpring's CDN                                                                 | HubSpot email templates reference images stored in HubSpot file manager or external URLs — all image assets must be re-uploaded or re-linked                                     |

## Sharpspring to HubSpot field mapping

The 30 most-used fields of 40 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/sharpspring/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Sharpspring HubSpot

1. `firstname` Contact `firstname` Contact
2. `lastname` Contact `lastname` Contact
3. `email` Contact `email` Contact
4. `phone` Contact `phone` Contact
5. `mobilephone` Contact `mobilephone` Contact

| Sharpspring field                | HubSpot field                        | Mapping                 | Note                                                                                                                                                                                                                                               |
| -------------------------------- | ------------------------------------ | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Contact.firstname`              | `Contact.firstname`                  | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.lastname`               | `Contact.lastname`                   | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.email`                  | `Contact.email`                      | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.phone`                  | `Contact.phone`                      | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.mobilephone`            | `Contact.mobilephone`                | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.jobtitle`               | `Contact.jobtitle`                   | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.address`                | `Contact.address`                    | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.city`                   | `Contact.city`                       | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.state`                  | `Contact.state`                      | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.postalcode`             | `Contact.zip`                        | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.country`                | `Contact.country`                    | direct                  |                                                                                                                                                                                                                                                    |
| `Contact.dateadded`              | `Contact.SharpSpring_Create_Date__c` | custom\_field\_required | HubSpot's native CreatedDate is set at migration time. Original SharpSpring create date preserved as a custom datetime field for reporting continuity.                                                                                             |
| `Contact.lead_score`             | `Contact.SharpSpring_Lead_Score__c`  | custom\_field\_required | SharpSpring lead score migrates as a custom numeric property. HubSpot has no native lead scoring field — score is stored for reference only; ongoing scoring requires rebuilding in HubSpot workflows.                                             |
| `Contact.lifecycle_stage_status` | `Contact.lifecycle_stage`            | transformed             | SharpSpring stage tracked via workflow membership maps to HubSpot lifecycle\_stage pick-list. FlitStack maps the most-recent exited stage value to one of HubSpot's standard lifecycle values (subscriber, lead, MQL, SQL, opportunity, customer). |
| `Contact.company`                | `Contact.associatedcompanyid`        | transformed             | SharpSpring's company name on a contact creates a Company association in HubSpot. The Company record must exist first; FlitStack sequences companies before contacts.                                                                              |
| `Contact.owner_id`               | `Contact.hubspot_owner_id`           | transformed             | SharpSpring owner IDs resolved by email match to HubSpot users. Unmatched owners are flagged before migration; records are assigned to a fallback owner or held for review.                                                                        |
| `Contact.optout`                 | `Contact.hs_email_optout`            | direct                  |                                                                                                                                                                                                                                                    |
| `Company.name`                   | `Company.name`                       | direct                  |                                                                                                                                                                                                                                                    |
| `Company.domain`                 | `Company.domain`                     | direct                  |                                                                                                                                                                                                                                                    |
| `Company.industry`               | `Company.industry`                   | value\_mapping          | SharpSpring industry pick-list values are mapped to HubSpot industry pick-list values. Non-matching values are mapped to 'Other' or preserved as a custom property.                                                                                |
| `Company.numberofemployees`      | `Company.numberofemployees`          | direct                  |                                                                                                                                                                                                                                                    |
| `Company.annualrevenue`          | `Company.annualrevenue`              | direct                  |                                                                                                                                                                                                                                                    |
| `Company.phone`                  | `Company.phone`                      | direct                  |                                                                                                                                                                                                                                                    |
| `Company.city`                   | `Company.city`                       | direct                  |                                                                                                                                                                                                                                                    |
| `Company.state`                  | `Company.state`                      | direct                  |                                                                                                                                                                                                                                                    |
| `Company.country`                | `Company.country`                    | direct                  |                                                                                                                                                                                                                                                    |
| `Company.dateadded`              | `Company.SharpSpring_Create_Date__c` | custom\_field\_required | Original SharpSpring company create date preserved as a custom datetime field since HubSpot's CreatedDate reflects the migration timestamp.                                                                                                        |
| `Deal.dealname`                  | `Deal.dealname`                      | direct                  |                                                                                                                                                                                                                                                    |
| `Deal.amount`                    | `Deal.amount`                        | direct                  |                                                                                                                                                                                                                                                    |
| `Deal.dealstage`                 | `Deal.dealstage`                     | value\_mapping          | SharpSpring deal stage values map to HubSpot stage names within the corresponding pipeline. Stage mapping is pipeline-specific; FlitStack delivers a stage-mapping table per pipeline during planning.                                             |

## What to watch for in a Sharpspring to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### SharpSpring workflows do not migrate and require complete rebuild in HubSpot

SharpSpring stores automation workflows as platform-native objects with branching logic, time-delay actions, scoring triggers, and enrollment conditions.

How we handle it

These do not export as executable logic — only as exported workflow definitions that must be manually rebuilt inside HubSpot's workflow editor. Teams frequently underestimate this scope. FlitStack exports the full SharpSpring workflow definitions (step-by-step conditions, actions, and enrollment rules) as a rebuild reference document for the HubSpot admin. Budget separate time for this rebuild phase and consider whether HubSpot's workflow model can replicate all SharpSpring branching patterns before migration day.

high

### HubSpot Custom Objects require Enterprise-tier — SharpSpring custom objects may not fit

SharpSpring custom objects are accessible on all tiers and are commonly used for product references, project records, or event registrations.

How we handle it

HubSpot Custom Objects are gated behind the Enterprise tier of the CRM Suite. If the destination HubSpot account is Starter, Professional, or not on the CRM Suite, SharpSpring custom object records cannot migrate to native HubSpot custom objects. FlitStack surfaces this before migration and migrates custom object data as custom properties on standard objects (Contact or Deal) when Enterprise is not available, with a note in the migration plan explaining the limitation.

medium

### SharpSpring VisitorID anonymous tracking has no HubSpot equivalent

SharpSpring VisitorID captures anonymous website visitor behavior (page views, session duration) and correlates those sessions with contacts once an email address is captured via form fill.

How we handle it

HubSpot's tracking code records page views and link clicks on contacts who are already known, but there is no anonymous-to-contact correlation model that preserves the pre-submission session history. SharpSpring VisitorID data for contacts who had anonymous visits before converting cannot be replicated in HubSpot's timeline. This data is documented in the migration plan but cannot be fully reconstructed without a HubSpot replacement for visitor identification.

medium

### HubSpot lifecycle\_stage is a single value — SharpSpring stage history collapses

SharpSpring tracks contact progression through multiple workflow exits and re-entries, giving contacts a potentially rich stage-change history.

How we handle it

HubSpot's lifecycle\_stage property holds a single current value at any point in time. FlitStack maps the most-recent SharpSpring stage value to HubSpot lifecycle\_stage at migration time and stores the full stage-change history as a custom text audit field (SharpSpring\_Stage\_History\_\_c). This preserves the data for reference but does not recreate HubSpot's native lifecycle-stage timeline behavior, which only tracks forward from the migrated value.

low

### SharpSpring email template images hosted on SharpSpring CDN must be re-uploaded

SharpSpring email templates store images on SharpSpring's CDN with platform-specific URLs.

How we handle it

When emails are rebuilt in HubSpot, those image URLs will not resolve inside HubSpot's email editor. All images embedded in SharpSpring email templates must be downloaded and re-uploaded to HubSpot's file manager before the rebuilt emails can send correctly. FlitStack extracts image URLs from SharpSpring email template data during export and provides a re-upload manifest as part of the migration package, reducing manual work during the email rebuild phase.

## How the migration runs

1. ### Assess HubSpot account tier and create custom properties

   FlitStack begins by reviewing the destination HubSpot account's tier to confirm Custom Object availability on Enterprise plans.

   What this step covers

   We then create all required custom properties in HubSpot — SharpSpring\_Lead\_Score\_\_c for lead scoring data, SharpSpring\_Create\_Date\_\_c for preserving original creation timestamps, SharpSpring\_Stage\_History\_\_c for lifecycle stage audit trails, and any additional custom properties for unmapped SharpSpring fields — before any data import begins. This preparation ensures HubSpot's schema is fully ready to receive SharpSpring data and prevents import errors from missing field references during the migration run.

2. ### Export SharpSpring contacts, companies, deals, and activities via API

   FlitStack pulls all standard objects from SharpSpring using the platform API: contacts with all properties and scoring data, companies with domain and industry, deals with pipeline and stage assignments, and engagement records (emails, calls, notes, tasks).

   What this step covers

   Form submission events, workflow membership snapshots, and VisitorID correlation data are exported as supplementary records. The export is validated for record count, required field completeness, and duplicate detection before mapping begins.

3. ### Map and import companies before contacts, then deals

   HubSpot requires company records to exist before contact associations can be created (via associatedcompanyid).

   What this step covers

   FlitStack sequences the import: first companies, then contacts with company associations resolved by email-domain or explicit company name match, then deals with pipeline-to-stage mapping applied per deal. Owner assignments are resolved by email match to HubSpot users at each stage. Records with unresolved owners are flagged in a pre-migration exception report for the team to address.

4. ### Run sample migration with field-level diff

   A representative slice — typically 200–500 records spanning contacts across different lifecycle stages, companies, deals from multiple pipelines, and a selection of activities — migrates to HubSpot first.

   What this step covers

   FlitStack generates a field-level comparison report between the SharpSpring source values and the HubSpot destination values for each mapped field. You review the diff to confirm lifecycle\_stage mapping, deal stage mapping, company association accuracy, and owner resolution before the full migration run commits.

5. ### Execute full migration with delta-pickup window and audit log

   The full migration loads all validated records into HubSpot.

   What this step covers

   A delta-pickup window of 24–48 hours captures any contacts, companies, or deals modified in SharpSpring during the cutover window — this is critical for teams that continue using SharpSpring up to go-live. FlitStack maintains a full audit log of every record created, updated, and skipped during migration. If reconciliation against the source data fails, one-click rollback reverts the HubSpot environment to its pre-migration state while preserving the audit log for root-cause analysis.

![](https://flitstack.ai/platforms/sharpspring.png) Sharpspring ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 50,000 records** Typical, smaller accounts

**5–10 days for over 200,000 records or heavy custom-object / multi-pipeline setups** Large or heavily customised accounts

SharpSpring-to-HubSpot migration pricing scales with record count, custom property count, and pipeline complexity. Accounts with high contact volume (50k+) and multiple deal pipelines fall in the upper pricing range because HubSpot pipeline-to-stage mapping and lifecycle\_stage value-mapping per stage add validation overhead during data transformation. Custom object creation in HubSpot (Enterprise-only feature) adds scope when SharpSpring uses custom objects extensively, as these require schema mapping and potential custom property creation on standard objects. The test migration pass and delta-pickup window for capturing in-flight changes are included in all migration packages. Setup consultation and rebuild planning for SharpSpring automation workflows are priced as separate line items, as these involve workflow analysis and HubSpot workflow design sessions outside the data migration scope. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Sharpspring to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Sharpspring to HubSpot

- SharpSpring's automation and workflow builder has become a bottleneck as team size grows and campaign complexity increases — HubSpot's workflow editor supports more complex branching logic, better list-based triggers, and integrates natively with HubSpot's CRM properties without relying on a separate scoring module for ongoing lead management.
- HubSpot's free CRM tier offers comprehensive contact management, deal tracking, email integration, and reporting capabilities at a cost structure that SharpSpring's contact-based pricing model cannot match as contact lists scale past 10,000 records.
- Reporting depth in SharpSpring caps out at built-in analytics with limited customization options — HubSpot's reporting suite across Sales Hub and Operations Hub provides funnel analytics, cohort reporting, and attribution tracking without requiring third-party BI tool integrations.
- SharpSpring recently adjusted its pricing structure to be more comparable with HubSpot's tiered model, narrowing the cost advantage that originally attracted smaller teams and startups — making the switch a more viable long-term investment in a more extensible platform.
- HubSpot's integration ecosystem through the App Marketplace connects to a broader range of tools than SharpSpring's third-party integrations, including native ERP, accounting, and service platform connectors that reduce the need for workarounds and custom API development.

Questions, answered

## Sharpspring to HubSpot migration questions

How long does a SharpSpring to HubSpot migration take?

Most SharpSpring-to-HubSpot migrations complete within 48–72 hours of clock time for under 50,000 contacts and standard deal pipelines. Larger setups with 200,000+ records, multiple SharpSpring custom objects, or complex multi-pipeline deal structures extend to 5–10 days. The longest planning step is mapping SharpSpring workflow definitions into HubSpot workflow logic — this rebuild happens outside the data migration timeline and should be scoped separately with your HubSpot admin.

Will my SharpSpring automation workflows migrate to HubSpot?

No. FlitStack AI migrates data and schema only — SharpSpring visual workflows, automation campaigns, sequence enrollments, and behavioral triggers do not transfer to HubSpot. SharpSpring stores workflow logic as platform-native objects that cannot be exported as executable automation. We export your SharpSpring workflow definitions as a structured rebuild reference (step-by-step conditions, actions, enrollment rules) so your HubSpot admin can reconstruct them inside HubSpot's workflow editor. This rebuild phase should be planned separately from the data migration.

What does SharpSpring lead scoring become in HubSpot?

SharpSpring lead scores (fit and engagement dimensions combined) migrate as a custom numeric property on the HubSpot contact record named SharpSpring\_Lead\_Score\_\_c. This preserves the score as a static reference value at migration time. HubSpot has no native equivalent to SharpSpring's lead scoring module — ongoing scoring requires rebuilding inside HubSpot using workflows, list-based segmentation, or HubSpot's native lead scoring feature if available on your Sales Hub tier. FlitStack creates the custom property during setup so the migrated score is immediately visible on every contact record.

Can I migrate SharpSpring custom objects to HubSpot?

SharpSpring custom objects migrate to HubSpot Custom Objects, but HubSpot Custom Objects are gated behind the Enterprise tier of the CRM Suite. If your destination HubSpot account is not Enterprise, FlitStack migrates custom object records as custom properties on the closest standard HubSpot object (Contact or Deal) and documents the limitation in the migration plan. Contact our team before migration if you need to confirm your HubSpot tier supports Custom Objects.

What happens to SharpSpring VisitorID data in HubSpot?

SharpSpring VisitorID captures anonymous visitor page views and correlates them with known contacts by email. HubSpot has no equivalent anonymous-to-contact correlation model — anonymous session history is not preserved in HubSpot's contact timeline. FlitStack exports VisitorID correlation data as a custom text property on the contact record for reference, but the behavioral timeline from anonymous visits cannot be reconstructed in HubSpot without rebuilding tracking from day one using HubSpot's native tracking code.

Does the migration affect my SharpSpring account during cutover?

No. FlitStack AI uses scoped read access on SharpSpring — your team continues working in SharpSpring throughout the migration window. A delta-pickup window of 24–48 hours captures any records created or modified in SharpSpring during the cutover so HubSpot reflects the final state of your SharpSpring data at go-live. No workflows are modified, no records are deleted, and no automations are triggered in SharpSpring during the migration.

How does SharpSpring's contact lifecycle stage map to HubSpot lifecycle\_stage?

SharpSpring does not have a single lifecycle\_stage property — contact stages are tracked through workflow membership and list assignments. FlitStack identifies the most-recent exited workflow stage for each contact and maps it to HubSpot's lifecycle\_stage pick-list (subscriber, lead, MQL, SQL, opportunity, customer). The full stage-change history is preserved as SharpSpring\_Stage\_History\_\_c on the contact record. This gives you both the current HubSpot lifecycle value and the complete SharpSpring stage audit trail for reporting continuity.

What happens to SharpSpring email templates and campaign assets?

SharpSpring email templates and campaign content do not migrate as reusable HubSpot templates. Images embedded in SharpSpring emails are stored on SharpSpring's CDN and will not resolve in HubSpot. FlitStack extracts all image URLs from SharpSpring email template data during export and provides a re-upload manifest so your team can re-host images in HubSpot's file manager before rebuilding templates. Email body content, subject lines, and design elements should be copied from the exported SharpSpring templates into HubSpot's email editor using HubSpot's drag-and-drop builder or code-paste functionality.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Iterable to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/iterable/to/hubspot) [**Marketing Star to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/marketing-star/to/hubspot) [**ChartMogul to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/chartmogul/to/hubspot) [**Kartra to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/kartra/to/hubspot) [**HighLevel to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/highlevel/to/hubspot) [**Filevine to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/filevine/to/hubspot) [**Sharpspring to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sharpspring/to/freshsales) [**Sharpspring to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sharpspring/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from Sharpspring to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
