---
title: "Sharpspring to Freshsales Migration | FlitStack AI"
description: "Migrate Sharpspring to Freshsales 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/freshsales"
---

# Sharpspring to Freshsales migration

Moving from SharpSpring to Freshsales consolidates your sales and marketing stack into a single CRM with built-in Freddy AI, contact lifecycle stages, and Kanban pipeline views. FlitStack AI maps every SharpSpring contact, company, deal, lead, and custom field to Freshsales objects — preserving original create dates, owner assignments, and activity timestamps so your new CRM reflects the full relationship history from day one.

Short answer

FlitStack AI migrates contacts, accounts, leads, deals and tasks from Sharpspring to Freshsales, 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: 24–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/freshsales#field-mapping)

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

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

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

Contact Account Lead Deal Task

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

## What moves from Sharpspring to Freshsales?

SharpSpring and Freshsales share a similar CRM object model — both use contacts, companies, leads, and deals as their core entities — but the platforms diverge significantly in how they handle automation, lead scoring, and lifecycle tracking.

Read the full summary

SharpSpring's visual workflow builder and behavioral lead scoring operate on a different architecture than Freshsales's workflow engine and Freddy AI. When migrating, we carry all SharpSpring data objects (contacts, companies, deals, leads, tasks, notes, emails) into Freshsales via the Freshsales REST API, preserving original timestamps, owner assignments via email match, and custom field values. SharpSpring's lead scoring values migrate to Freshsales custom number fields since Freshsales calculates scoring through Freddy AI rather than a static property. SharpSpring's VisitorID tracking data has no Freshsales equivalent and is preserved as a custom reference field. Workflows, automation rules, email sequences, and campaign logic do not migrate — these must be rebuilt in Freshsales using our exported definitions as a rebuild guide. The migration runs in scoped read-access on SharpSpring with a 24–48 hour delta-pickup window capturing in-flight changes during cutover.

direct

### Contact → Contact

SharpSpring contacts map 1:1 to Freshsales contacts.

How it maps

Email is the primary deduplication key. Contacts without an associated company in SharpSpring land in Freshsales as standalone contacts. Primary company assignment uses SharpSpring's primary company flag or most-recently-modified rule. If a contact has multiple associated companies, we select the most recently updated company as the primary account to maintain data consistency.

direct

### Company → Account

SharpSpring companies map to Freshsales accounts.

How it maps

Account Name, domain, industry, employee count, and annual revenue transfer directly. Parent-child company hierarchies in SharpSpring map to Freshsales Parent Account relationships, requiring topological ordering during migration. We also preserve the original company identifiers as a custom field to avoid confusion if duplicate company names exist across different SharpSpring accounts.

direct

### Lead → Lead

SharpSpring leads map to Freshsales leads.

How it maps

Both platforms treat leads as pre-contact records with status fields. SharpSpring lead status values map to Freshsales lead status via value mapping. Unconverted SharpSpring leads land as Freshsales leads; converted leads migrate as contacts.

direct

### Deal → Deal

SharpSpring deals map to Freshsales deals (Freshsales uses 'Deal' as the object name, distinct from Salesforce's 'Opportunity').

How it maps

Deal name, amount, expected close date, owner, and stage all transfer. Pipeline-stage mapping requires value-by-value mapping since stage names differ between platforms. We also record the original SharpSpring deal ID in a custom field to support future cross-referencing and to aid in reconciling any duplicate deal names during the migration.

direct

### Task → Task

SharpSpring tasks map to Freshsales tasks.

How it maps

Task subject, due date, status, priority, and owner transfer. Tasks linked to specific contacts, companies, or deals preserve their parent record associations via Freshsales foreign key lookups. If a task references a contact that does not yet exist in Freshsales, we create a placeholder contact record to maintain the association until the full dataset is loaded.

transformed

### Email Activity → Sales Activity (Email)

SharpSpring email logs and sent emails map to Freshsales Sales Activities of type 'Email'.

How it maps

The original sent date, recipient, subject, and body text transfer. HTML formatting is preserved as plain text since Freshsales activities store plain text content. We also capture any inline attachments as linked file records in Freshsales, ensuring that important email assets are retained with the activity timeline.

******What moves 12 objects

Sharpspring Freshsales

- Contact Contact 1:1
- Company Account 1:1
- Lead Lead 1:1
- Deal Deal 1:1
- Task Task 1:1
- Email Activity Sales Activity transformed

\+ 6 more in the mapping below

## How Sharpspring and Freshsales 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                                                                                           | Freshsales                                                                                         |
| ---------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Lead scoring model     | SharpSpring stores behavioral and demographic scores as contact properties updated by workflow rules  | Freshsales uses Freddy AI for dynamic lead scoring; static scores require custom fields            |
| Automation engine      | SharpSpring visual workflow builder with triggers, actions, and branching logic for complex sequences | Freshsales workflows use a simpler rule-based model; advanced sequences require Freshsales Suite   |
| Contact lifecycle      | SharpSpring tracks lifecycle through behavioral data and custom properties                            | Freshsales has native Contact Lifecycle Stages (Subscriber, Lead, MQL, SQL, Opportunity, Customer) |
| Visitor tracking       | SharpSpring VisitorID captures anonymous web visitors with company identification                     | Freshsales lacks native visitor tracking; requires third-party integration                         |
| Pipeline model         | SharpSpring uses a single deal pipeline with customizable stages                                      | Freshsales Growth plan includes one pipeline; Pro and Enterprise support multiple pipelines        |
| Built-in communication | SharpSpring email and forms are part of its marketing automation suite                                | Freshsales includes built-in phone, email, and chat on all paid plans                              |
| Pricing structure      | SharpSpring charges by contact volume with unlimited users across all plans                           | Freshsales uses per-seat pricing with tiered features; Growth $9/user/mo, Pro $39/user/mo          |
| AI capabilities        | SharpSpring relies on rule-based lead scoring and manual workflow triggers                            | Freshsales includes Freddy AI for contact scoring, deal insights, and forecasting on Pro+ plans    |

## Sharpspring to Freshsales field mapping

The 30 most-used fields of 43 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/freshsales.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Sharpspring Freshsales

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

| Sharpspring field           | Freshsales field              | Mapping                 | Note                                                                                                          |
| --------------------------- | ----------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------- |
| `Contact.firstname`         | `Contact.first_name`          | direct                  |                                                                                                               |
| `Contact.lastname`          | `Contact.last_name`           | direct                  |                                                                                                               |
| `Contact.email`             | `Contact.email`               | direct                  |                                                                                                               |
| `Contact.phone`             | `Contact.phone`               | direct                  |                                                                                                               |
| `Contact.mobilephone`       | `Contact.mobile`              | direct                  |                                                                                                               |
| `Contact.jobtitle`          | `Contact.job_title`           | 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.leadsource`        | `Contact.lead_source`         | direct                  |                                                                                                               |
| `Contact.leaddate`          | `Contact.created_at`          | transformed             | Original SharpSpring lead date preserved as custom field since Freshsales CreatedAt is set at migration time. |
| `Contact.leadscore`         | `Contact.sharpSpring_score`   | custom\_field\_required | Freshsales calculates scoring via Freddy AI; SharpSpring static score migrates to custom number field.        |
| `Contact.visitorid`         | `Contact.visitor_id_source`   | no\_equivalent          | SharpSpring VisitorID data has no Freshsales equivalent; preserved as reference text field.                   |
| `Contact.company`           | `Contact.account_id`          | transformed             | SharpSpring company name resolves to Freshsales account\_id lookup; account must exist first.                 |
| `Contact.owner`             | `Contact.owner_id`            | transformed             | Owner resolved by email match to Freshsales users; unmatched owners flagged before migration.                 |
| `Company.name`              | `Account.name`                | direct                  |                                                                                                               |
| `Company.domain`            | `Account.website`             | direct                  |                                                                                                               |
| `Company.industry`          | `Account.industry`            | value\_mapping          | Industry pick-list values mapped per source value; default applied where no exact match.                      |
| `Company.numberofemployees` | `Account.number_of_employees` | direct                  |                                                                                                               |
| `Company.annualrevenue`     | `Account.annual_revenue`      | direct                  |                                                                                                               |
| `Company.phone`             | `Account.phone`               | direct                  |                                                                                                               |
| `Company.address`           | `Account.address`             | direct                  |                                                                                                               |
| `Company.city`              | `Account.city`                | direct                  |                                                                                                               |
| `Company.state`             | `Account.state`               | direct                  |                                                                                                               |
| `Company.postalcode`        | `Account.zip`                 | direct                  |                                                                                                               |
| `Company.country`           | `Account.country`             | direct                  |                                                                                                               |
| `Company.parentcompanyid`   | `Account.parent_id`           | transformed             | SharpSpring parent company maps to Freshsales parent account; circular references flagged during migration.   |
| `Lead.firstname`            | `Lead.first_name`             | direct                  |                                                                                                               |

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

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

high

### SharpSpring lead scoring requires manual configuration in Freshsales

SharpSpring stores behavioral and demographic lead scores as contact properties calculated by its workflow engine.

How we handle it

Freshsales calculates contact scoring through Freddy AI on Pro and Enterprise plans, not as a static property. Migrated SharpSpring scores transfer to a custom number field (SharpSpring\_Score\_\_c) as a reference value, but Freshsales Freddy AI scoring starts fresh after migration. Teams relying heavily on SharpSpring lead scores for segmentation or prioritization must rebuild scoring logic in Freshsales using Freshsales workflows or Freddy AI configuration. Additionally, we can preserve historical scores as a separate custom field for reference during the transition.

high

### SharpSpring workflows and automation sequences do not transfer to Freshsales

SharpSpring visual workflows and email sequences operate on an event-action architecture that has no equivalent in Freshsales.

How we handle it

Every SharpSpring workflow — including lead routing rules, autoresponders, scoring adjustments, and campaign sequences — must be recreated in Freshsales using Freshsales workflows or Freshsales Suite's Journey Builder. We export all SharpSpring workflow definitions as a structured reference document so your Freshsales admin can rebuild them systematically.

medium

### VisitorID tracking data has no Freshsales equivalent

SharpSpring's VisitorID feature identifies anonymous web visitors and associates them with companies based on IP lookups.

How we handle it

This behavioral data is stored on contact records and used for lead scoring and campaign triggers. Freshsales has no native visitor tracking or company identification feature — it relies on form submissions and manual data entry for contact creation. VisitorID data migrates as read-only reference fields on contacts; it does not create net-new tracking capabilities in Freshsales.

medium

### Freshsales Growth plan limits pipelines and requires upgrade for multiple sales processes

SharpSpring supports multiple deal pipelines on all plans.

How we handle it

Freshsales Growth ($9/user/mo) is limited to one sales pipeline. Teams with multiple SharpSpring pipelines (e.g., separate pipelines for enterprise vs. SMB deals) must upgrade to Freshsales Pro ($39/user/mo) or Enterprise ($59/user/mo) before migration to recreate all pipelines. Pipeline-stage mapping must account for this plan dependency. If you are on the Growth plan, we can still import all pipeline data into a single Freshsales pipeline and tag each deal with a custom field indicating its original SharpSpring pipeline. After migration, you can upgrade to Pro or Enterprise and create additional pipelines based on those tags.

low

### Email templates and campaign assets require manual migration

SharpSpring stores email templates, landing page designs, and campaign assets in its marketing automation system.

How we handle it

These do not migrate to Freshsales, which handles email through Freshsales Suite's template editor and supports landing pages only on marketing plans. We export email template content as HTML files and provide a mapping guide for rebuilding in Freshsales or your preferred email platform. The exported HTML preserves inline styles and images, but any dynamic content driven by SharpSpring's personalisation tokens must be remapped to Freshsales liquid syntax or replaced with static text. Our mapping guide lists each token and its Freshsales equivalent, and we flag any template elements that require manual review before deployment.

## How the migration runs

1. ### Audit SharpSpring data and schema before migration

   FlitStack AI connects to SharpSpring via scoped read-access API credentials to inventory all contacts, companies, leads, deals, tasks, notes, and custom field definitions.

   What this step covers

   We generate a data audit report showing record counts per object, custom field inventory with data types, and pipeline/stage configuration. This report identifies any data quality issues (duplicate emails, missing required fields, orphaned records) before field mapping begins.

2. ### Map SharpSpring objects and fields to Freshsales schema

   We create a field-level mapping document for every SharpSpring standard and custom field, assigning Freshsales target fields and transformation logic.

   What this step covers

   Lead score fields map to custom fields, VisitorID maps to reference text fields, and SharpSpring pipeline stages map to Freshsales deal stages. We validate that required Freshsales fields (email on contacts, account\_id on contacts) are populated or have a fallback rule before the migration run.

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

   A representative sample (typically 100–500 records spanning contacts, accounts, leads, deals, and activities) migrates first.

   What this step covers

   We generate a field-level diff comparing source values to Freshsales values, letting you verify lead score mapping, pipeline-stage mapping, and owner resolution before committing the full dataset. You approve the sample before the full migration run executes. During the sample phase, we also validate custom field data types, check for missing required fields, and confirm that any picklist values align with Freshsales allowed options. This helps catch configuration issues early and reduces risk for the full data load.

4. ### Execute full migration with delta-pickup window

   The full SharpSpring dataset migrates to Freshsales via the Freshsales REST API, sequenced to resolve foreign keys correctly (accounts before contacts, contacts before deals).

   What this step covers

   A 24–48 hour delta-pickup window runs concurrently, capturing any records created or modified in SharpSpring during the migration window. Audit logs record every operation, and one-click rollback is available if post-migration reconciliation reveals issues. We also perform a final reconciliation report that compares record counts and key field values between SharpSpring and Freshsales, ensuring data integrity before you switch off the source system.

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

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 · Freshsales 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

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

**5–10 days for over 500,000 records or complex custom object setups** Large or heavily customised accounts

SharpSpring-to-Freshsales migration pricing depends on three primary drivers: total record volume across contacts, companies, deals, and activities; the number of custom fields and custom objects that require mapping or recreation in Freshsales; and the complexity of deal pipeline stage mapping, particularly if SharpSpring uses multiple pipelines or custom stage configurations. Accounts with more than 20 custom fields or complex custom objects fall into the upper pricing tier because field-level validation and transformation work increases. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Sharpspring to Freshsales

- SharpSpring's workflow automation is built for marketing sequences rather than sales-driven triggers, making it clunky for teams that need deal-stage-based actions and territory-based assignment rules that Freshsales handles natively. When sales teams rely on pipeline-specific automation and dynamic assignment based on geographic territories, SharpSpring's marketing-centric design can slow down processes and require custom workarounds. Freshsales natively supports deal-stage workflows and territory routing, reducing the need for external configuration.
- SharpSpring pricing scales with contact volume, which becomes expensive as teams grow beyond 10,000 contacts. Freshsales per-seat pricing is more predictable for sales-focused teams that don't need full marketing automation. For growing sales teams, per-seat pricing offers a clearer cost structure, especially when the primary use case is managing deals and contacts rather than executing marketing campaigns. This predictability helps with budgeting and scaling headcount without unexpected spikes in license fees.
- Freshsales Freddy AI provides automated contact scoring, deal insights, and conversation intelligence on Pro plans — features that SharpSpring requires third-party integrations or manual workflow setup to approximate. By embedding AI-driven scoring and conversation analysis directly into the CRM, Freshsales reduces the reliance on external tools and custom scripts, enabling sales reps to prioritize leads based on real-time data without additional configuration overhead.
- Teams already using Freshdesk or other Freshworks products gain unified support-to-sales visibility with Freshsales, whereas SharpSpring operates as a standalone marketing CRM without native service desk integration. This tight integration allows support tickets to automatically create or link to Freshsales contacts, giving sales reps immediate context on customer issues and enabling a smooth handoff between support and sales workflows.
- SharpSpring's UI has a steeper learning curve for new sales reps compared to Freshsales, which is designed specifically for sales team onboarding with Kanban views and built-in calling that SharpSpring positions as add-ons. Freshsales also includes integrated email, chat, and a mobile app that allows reps to manage pipelines on the go, whereas SharpSpring's communication features are often billed separately, adding to overall cost and complexity for sales teams.

Questions, answered

## Sharpspring to Freshsales migration questions

How long does a SharpSpring to Freshsales migration take?

Most SharpSpring-to-Freshsales migrations complete within 24–72 hours for accounts with fewer than 50,000 total records across contacts, companies, deals, and activities. Accounts with 500,000+ records or complex custom object schemas extend to 5–10 days. The longest phase is typically mapping SharpSpring pipelines and custom fields to Freshsales equivalents before data transfer begins. In addition, the preparation stage includes validating record ownership, resolving foreign key dependencies, and flagging any data inconsistencies to ensure a clean import into Freshsales.

Will my SharpSpring workflows and automation sequences migrate to Freshsales?

No. FlitStack AI migrates data only — SharpSpring workflows, email sequences, visual automation rules, and behavioral triggers do not transfer to Freshsales. Freshsales uses a different workflow architecture (Freshsales workflows or Suite's Journey Builder). We export your SharpSpring workflow definitions as a structured reference document your Freshsales admin can use to rebuild automation logic in the destination platform. Because the underlying event-action model differs, each workflow must be recreated using Freshsales workflow rules or the Journey Builder. The exported definitions capture triggers, actions, conditions, and timing so nothing is lost.

What happens to SharpSpring lead scores in Freshsales?

SharpSpring behavioral and demographic lead scores migrate as read-only values in a custom number field (SharpSpring\_Score\_\_c) on each contact. Freshsales calculates its own contact scoring through Freddy AI on Pro and Enterprise plans. The migrated SharpSpring scores provide historical reference but Freshsales scoring logic starts fresh after migration. Teams should plan to configure Freshsales Freddy AI scoring criteria post-migration. If historical scoring influenced past campaign decisions, retaining the SharpSpring scores as a reference field can support retrospective analysis in Freshsales.

Can I migrate SharpSpring custom fields and custom objects to Freshsales?

Yes. SharpSpring custom fields on contacts, companies, leads, and deals migrate to Freshsales custom fields of matching types (text, number, date, picklist, checkbox). Custom objects migrate 1:1 to Freshsales custom objects. Picklist values that differ between platforms require value-by-value mapping. SharpSpring's VisitorID data has no Freshsales equivalent and is stored as a reference text field. During migration, we validate that each custom field's data type aligns with Freshsales field constraints and flag any unsupported formats for manual review.

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. A 24–48 hour delta-pickup window captures records created or modified during the cutover period so Freshsales reflects SharpSpring's final state at go-live. SharpSpring remains fully functional until you choose to decommission it. During the delta window, any new contacts, updated deals, or changed company records are automatically imported into Freshsales, ensuring that the final dataset includes all activity up to the moment of switchover.

How does SharpSpring's multiple pipeline model map to Freshsales?

SharpSpring supports multiple deal pipelines on all plans. Freshsales Growth ($9/user/mo) supports one pipeline; multiple pipelines require Pro ($39/user/mo) or Enterprise ($59/user/mo). Each SharpSpring pipeline maps to a corresponding Freshsales pipeline with stage-by-stage mapping. If you're on Freshsales Growth, we recommend consolidating to one primary pipeline or upgrading before migration. Our migration tool records the original pipeline identifiers so you can later recreate additional pipelines in Freshsales Pro or Enterprise without losing context about which deals originated in which SharpSpring pipeline.

What happens to my SharpSpring email templates and campaign assets?

SharpSpring email templates, landing page designs, and campaign creative assets do not migrate to Freshsales. We export email template HTML content as files you can import into Freshsales Suite or your preferred email platform. Landing pages require rebuilding in Freshsales or an alternative web platform. We provide a content inventory so nothing is overlooked during the rebuild phase. Additionally, we capture metadata such as template variables, conditional content blocks, and associated images so that the rebuilt assets retain as much of the original formatting and dynamic elements as possible.

How does FlitStack handle SharpSpring VisitorID data in Freshsales?

SharpSpring VisitorID identifies anonymous web visitors and associates them with companies via IP lookup. Freshsales has no native visitor tracking equivalent. VisitorID data migrates as read-only reference fields (VisitorID\_Source\_\_c, Tracked\_Company\_\_c) on contact records. This preserves historical context but does not provide ongoing tracking — teams needing visitor intelligence post-migration must configure a separate web tracking tool integrated with Freshsales. If you rely on visitor insights for lead scoring or campaign personalization, we can map existing VisitorID scores to custom number fields to keep that data accessible for future segmentation in Freshsales.

## Related migrations

[![](https://flitstack.ai/platforms-trim/freshsales.webp) Migrate to **Freshsales** Every source we move into Freshsales, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/crm/freshsales) [**Dynamics 365 to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/freshsales) [**HubSpot to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/freshsales) [**Sharpspring to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sharpspring/to/hubspot) [**Sharpspring to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sharpspring/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Freshsales / Freshmarketer Migration FAQs — Freshworks Support](https://crmsupport.freshworks.com/support/solutions/articles/50000003712-freshsales-freshmarketer-migration-faqs)
2. [What are custom field limits? — Freshsales Suite Support](https://support.freshsales.io/support/solutions/articles/226676-what-are-custom-field-limits-)
3. [Freshsales bulk upsert — Freshworks Support](https://support.freshsales.io/support/solutions/articles/freshsales-bulk-upsert)
4. [How to import contacts from a CSV/XLSX file — Freshsales Classic](https://support.freshsales.io/support/solutions/articles/218558-how-to-import-contacts-from-a-csv-xlsx-file-)
5. [Best Practices for Data Import — Freshsales Suite Support](https://support.freshsales.io/support/solutions/articles/225681-best-practices-for-data-import)
6. [How to make a field mandatory? — Freshsales Suite Support](https://support.freshsales.io/support/solutions/articles/222062-how-to-make-a-field-mandatory-)
7. [How to migrate data from Pipedrive? — Freshsales Suite Support](https://support.freshsales.io/support/solutions/articles/225625-how-to-migrate-data-from-pipedrive-)

Get a quote

## Moving from Sharpspring to Freshsales?

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

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