Skip to content
Get a quote

Migrate to Freshsales

Freshsales is the Freshworks Suite CRM whose import model rewards teams that pre-create custom fields against tier-scaled caps, respect the 100-record bulk upsert ceiling, and align Leads-versus-Contacts boundaries before the first row is uploaded.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Freshsales from 850+ CRMs, including Sharpspring, Dynamics 365, HubSpot. Every field is mapped to Freshsales's objects, history and associations come across, the Freshsales setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationFreshsales
SharpspringDynamics 365HubSpot
850+ sources mapped into Freshsales

Systems we move into Freshsales

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

What Freshsales supports, and where its import tools stop

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
REST onlyOAuth 2.0
Rate limitsNot publicly documented on Freshworks CRM; Freshdesk docs reference rate limits but Freshsales-specific limits are undocumented
ObjectSupportNote
LeadsfullStandard lead object with lifecycle stages and source tracking. We migrate Leads 1:1 and map Lead_Status to the destination's equivalent lifecycle field.
ContactsfullCore contact record linked to Accounts. We preserve all standard fields, custom fields, and contact lifecycle stages.
AccountsfullCompany/Organization record that can be linked to multiple Contacts and Deals. We preserve account details and association mappings.
DealsfullCalled 'Deals' in Freshsales UI. We map to Opportunities in standard CRM terminology. Pipeline stage, amount, probability, and owner are all migrated.
ProductsmappedProduct catalog is used in CPQ and quotes. We migrate products but CPQ licenses are plan-gated (1 on Growth, more on Pro). We flag any CPQ-related records for review.
Activities (Tasks and Events)mappedTasks and Events/Calls are separate activity types. We migrate tasks fully; event metadata (call recordings, logs) requires API access and Enterprise tier for audit logs.
Custom ObjectsmappedCustom objects are created via Freshworks developer platform apps and stored in entity storage. We can migrate custom object records if the app schema is documented; otherwise we preserve raw records as JSON blobs.
Custom FieldsmappedBoth standard and advanced custom fields exist depending on plan tier. We migrate all custom field definitions and values, flagging any advanced fields that may require Pro or Enterprise.
PipelinesfullMultiple pipelines are supported on Pro and above. We migrate pipeline configurations and stage definitions.
TerritoriesmappedTerritory management is Pro-tier only. We migrate territory assignments where available; otherwise territory data is preserved as a Contact/Deal property.
Sales SequencesmappedSequences are Pro and above. We migrate sequence definitions but note that sequences will not auto-execute post-migration until re-enabled by Freshworks support.
AttachmentsmappedFile storage limits vary by plan (2GB/user Growth, 5GB/user Pro, 100GB/user Enterprise). We migrate attachments but check storage limits against destination plan.

The Freshsales migration guide

Why teams migrate to Freshsales

The four shapes a Freshsales migration takes, and what makes the platform easier — or harder — than the category average.

Freshsales is the sales CRM inside the Freshworks Customer Engagement Suite, the company also known for Freshdesk and Freshservice. The product was originally launched as a standalone CRM and is now sold as Freshsales Suite — the bundled CRM, marketing automation, chat and telephony offering that succeeded the older Freshsales Classic and Freshmarketer Classic SKUs1.

The typical Freshsales customer is a small to mid-market sales team — 10 to 200 reps — that wants pipeline, sequences and Freddy AI scoring without the per-seat cost and admin overhead of Salesforce. Compared with HubSpot Sales Hub, Freshsales positions itself on flat per-user pricing instead of a contact-tier model; compared with Pipedrive, it positions on the integrated Freshworks suite (one tenant for sales, marketing and support) plus Freddy AI deal insights.

The shapes of migration that actually land on Freshsales tend to fall into four patterns. First, HubSpot exits, driven by contact-tier pricing creep at the $2M–$10M revenue band where the bill triples as the list grows without any new feature usage2. Second, Pipedrive consolidations, where a team needs marketing automation, telephony and chat alongside the deal pipeline and would rather have one vendor than four.

Third, Salesforce downsizes — teams that bought Sales Cloud for the brand and never used Apex, Flows or the AppExchange, and want a flat-rate CRM with the same Leads/Accounts/Opportunities mental model. Fourth, Freshsales Classic upgrades — existing customers being moved by Freshworks itself onto Freshsales Suite under the published plan-mapping table1.

Each shape has a different difficulty profile: a Pipedrive migration usually has clean object parity, while a Salesforce migration brings rich automation that does not move across at all.

What makes migrating to Freshsales easier than the category average is the native CRM Migration tool itself — Freshworks ships pre-built importers from Pipedrive, Salesforce, Zoho and HubSpot that accept the source platform's own zip export and map default and custom fields automatically up to 25,000 records for instantaneous import12.

What makes it harder than the average is the per-tier custom-field cap — the Sprout (Free) plan allows zero custom fields per entity, Blossom (Growth) allows 10, and only Forest (Enterprise) opens up to 450 across the core modules3. Teams who do not check this number against their source schema discover mid-import that they need to upgrade the tier before they can even land the data.

Workflows, Sales Sequences, Freddy AI scoring rules and reports do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

The Freshsales data model you need to map into

Objects, custom fields, relationships, and the upsert keys you'll wire on every record — the destination schema decoded.

Freshsales is built around a small set of standard modules plus optional Custom Modules on higher tiers. The platform's object model splits people into two records — Leads for unqualified inbound and Contacts for qualified prospects associated with an Account. Leads were temporarily removed in the older Freshsales Classic generation and reintroduced in the current Suite as a separate module; do not assume your source platform's single People object collapses neatly into one Freshsales module.

Before you can map a field on the source side, you need to know exactly which destination module the row belongs on, what fields it requires, and which value will serve as its unique identifier for upsert. The table below summarises the modules you will touch in a Freshsales Suite migration.

ObjectWhat it storesRequiredTier
ContactsQualified people associated with an AccountLast name (email recommended as unique key)All plans
LeadsUnqualified inbound prospects before account associationLast name, emailAll plans (reintroduced in Freshsales Suite)
Accounts (Sales Accounts)Companies / organisationsNameAll plans
DealsRevenue opportunities in a pipeline stageDeal name, sales pipeline, deal stage, deal valueAll plans
NotesFree-text notes attached to any recordBody, target recordAll plans (20 MB attachment cap per note)
TasksOpen or completed to-do items with owners and due datesTitle, owner, due dateAll plans
AppointmentsCalendar meetings logged against recordsTitle, start time, attendeesAll plans
Documents / FilesTrackable attachmentsFile, owning record150 MB per file; storage scales with seat count
ProductsCatalogue of sellable items linked to dealsName, pricePro and above
Custom ModulesCustomer-defined record typesSchema defined first; per-field requirementsEnterprise (Forest) — up to 310 custom fields per module

Contacts and Leads use email as the de-facto unique identifier — Freddy AI's duplicate detection on the Pro plan matches new records against existing rows on email. Accounts use name plus an optional custom cf_domain_name property as the practical upsert key, since the Sales Accounts bulk upsert path requires you to declare which property carries the unique value4.

Deals and Custom Module records have no natural unique key, so create a single-line text custom field, mark it unique, and use it as your external ID during bulk upsert.

Custom field availability is the most important number in this section. Freshsales caps custom fields per entity by plan tier — Sprout offers zero, Blossom 10, Garden 150, Estate 305 and Forest 450, with Custom Modules getting their own 310-field ceiling on Forest3.

Field typeLimitNotes
Text field (single-line)255 charsStores any alphanumeric string
Paragraph / multi-line text~65,000 charsLine breaks preserved on import
NumberInteger or decimalStrip currency symbols and thousands separators
DateYYYY-MM-DDTimezone-stripped — date values can shift by one day on import5
DatetimeISO-8601Stored in account timezone
Dropdown (single-select)~250 optionsPicklist values are case-sensitive on import
Multi-select / checkbox~250 optionsSemicolon-delimited on CSV/XLSX import6
Lookup / relationshipEnterprise only for cross-module lookupsRequired field on Custom Modules to bind parent records
Formula fieldEnterprise / Forest onlyDoes not import — rebuild on-platform
Custom fields per entity0 / 10 / 150 / 305 / 450 (Sprout → Blossom → Garden → Estate → Forest)Custom Modules get a separate 310-field cap on Forest3

Relationships in Freshsales are modelled as lookups between modules: Contacts associate to one or more Accounts, Deals associate to a primary Contact and an Account, and Custom Modules associate via lookup fields to standard modules7. There is no master-detail-style cascade-delete: deleting a parent does not delete children, which is behaviour you may need to reproduce in a workflow if your source platform relied on it.

Custom Modules (Forest / Enterprise) participate in lookups the same way standard modules do. They are loaded via the same bulk upsert path and accept their own custom fields, with the 310-cap noted above3.

Pre-migration prep — the work before you touch Freshsales

What must be true on the source, the destination, and across the team before the first row hits the import tool.

The single best predictor of a clean Freshsales migration is how much work you do on the source side before the first import button is pressed. Freshworks Support's own best-practice article warns that fixing errors after the load is more expensive than fixing them in the CSV, and recommends a final clean run after a deliberate test load9.

Configure Freshsales fully — users, custom fields, territories, pipelines — before the import, not after. Source-side fixes are an order of magnitude cheaper than destination-side cleanup.

Treat the source export as raw material that needs to be shaped to Freshsales's expected formats — email lowercased, phone normalised, picklist values made case-exact, multi-select values joined with semicolons, dates rewritten to YYYY-MM-DD, and owners resolved to Freshsales user email addresses that already exist in the destination.

Source-side prep

  • Audit and dedup the source database before export. Freddy AI duplicate detection on the Freshsales side is Pro-and-above and runs after records land — case-variant emails will become two contacts unless you normalise upstream.
  • Normalise emails to lowercase, trim whitespace, and strip role-based addresses (info@, sales@) that you do not want to flood the Contacts module with.
  • Match picklist values case-exactly — Freshsales drop-down imports treat the value as case-sensitive, and a row whose Stage = New will fail to map to a picklist value named new11.
  • Convert multi-select values to semicolon-delimited strings in the CSV/XLSX — Freshsales splits on ; for multi-select fields and will treat a comma-separated value as a single literal string6.
  • Stamp a stable external ID on every record in the source export — a UUID or the source platform's primary key — and store it in a custom unique field so re-runs and reconciliation are deterministic.
  • Decide what is in scope for historical activities. Notes, Tasks and Appointments can be imported, but past Email conversations require the Freshsales email-sync historical import which runs after mailbox connection13.

Destination-side prep

  • Create a Sandbox under Admin Settings → Other SFA Settings → Sandbox if you are on the Forest / Enterprise plan — Sandbox is gated to that tier, only org admins can create one, and you can have one sandbox at a time8. On lower tiers, use a free trial account as a throwaway dry-run instance.
  • Provision users first under Admin Settings → Users with the exact email address you will reference in the Sales Owner column, otherwise unmatched owners default to the importing admin and silently break owner-based workflows14.
  • Pre-create every custom field on the right module with the right type — Sprout supports zero custom fields, and even on paid tiers a Number field cannot be retroactively changed to Decimal after data lands3.
  • Build sales pipelines and deal stages before importing any deals — Freshsales rejects deal rows whose stage does not exist on the named pipeline.
  • Configure territories and round-robin assignment rules so they run on imported data correctly9. Workflow Automation rules should be paused during the import to avoid triggering notifications on backfilled records.
  • Define Custom Modules and their lookup fields before importing. Custom Module schemas must exist before records of that type can be loaded.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department that touches the CRM. Train sales reps on Freshsales Kanban deal boards, the Contacts/Leads split and the Freddy AI insights panel before go-live, not after.

A small Pipedrive-to-Freshsales migration under 25,000 records runs as an instantaneous import12; anything larger is queued by Freshworks and processed in off-peak hours over one to two business days. Build the human runway accordingly.

Import mechanisms: UI wizard and CRM Migration tool

Two main paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.

Freshsales exposes two main load paths and the right one depends on dataset size and source platform. The native UI Import covers most one-shot migrations under 25,000 records. The CRM Migration tool ships pre-built importers from Pipedrive, Salesforce, Zoho and HubSpot. Third-party ETL tools sit on top of both and add staging, transformation and dedup layers.

UI Import (CSV / XLSX)

The native import lives on each module's list-view page — click Contacts → Import Contacts, Deals → Import Deals, or the equivalent on Accounts and Leads6. The import accepts CSV and XLSX files up to 5 MB per file11 and requires a column that maps to Last Name for Contact and Lead imports.

It offers two modes: Create new records only, or Create new + update existing — the upsert path that matches on a chosen unique field6.

Multi-select fields require values separated by semicolons (;) in the CSV — comma separation is treated as a single string6. Mandatory custom fields block the import if the column is missing or empty11; bad rows are reported in an error-log email sent to the importing admin after the job finishes. The right call: UI for one-shot loads under 25,000 records on standard modules, or any time you want a visual mapping review before commit.

CRM Migration tool (pre-built source importers)

Freshsales ships a CRM Migration experience that accepts the source platform's own zip export and runs a static field mapping. The Salesforce variant accepts the standard Salesforce data export zip and imports Leads, Contacts, Accounts, Opportunities, Events and Tasks CSV files directly15. The Pipedrive variant runs the same pattern with a zip export and maps default plus custom fields by exact name12.

Custom-field auto-mapping requires the destination custom field to exist with the exact same display name as in the source export, so the prep step in Section 3 — creating Freshsales custom fields with matching names — is non-optional. The CRM Migration tool handles up to 25,000 records as an instantaneous load; over that, Freshworks queues a migration request and processes in 1–2 business days during off-peak hours12.

Third-party staging tools

Tools like Airbyte, Fivetran, Stitch and Hevo all expose a Freshsales source/destination connector. Their role in a one-time migration is rarely the move itself — they are the staging layer that lands source data in a warehouse, the transformation layer that converts picklist case and resolves owner emails, and the ongoing-sync layer that takes over once the cutover is done.

Mapping your data into Freshsales

The longest section — because field mapping is where almost every migration that fails actually breaks.

Mapping is where every migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether reports work on day two, whether Workflow Automations fire correctly on day five, and whether your sales team trusts the data on day thirty.

Work module by module, top to bottom of the import order: Accounts first (so Contacts and Deals can lookup to them), then Contacts and Leads, then Deals, then Notes / Tasks / Appointments, then Custom Modules and Products.

Contacts and Leads

Freshsales splits people into Leads (unqualified inbound) and Contacts (qualified, account-bound). Decide your boundary before import: a common rule is that source records with a non-empty Account and any logged activity become Contacts, while everything else lands as a Lead. Importing the same person twice (once as Lead, once as Contact) is the most common preventable failure on day one.

Common source → Freshsales Contact mapping
SourceDestinationNote
emailemail (de-facto unique key)Lowercase before import; matched by Freddy AI dedup on Pro+
first_name / last_namefirst_name / last_nameLast Name is mandatory — rows without it fail11
phonemobile_number / work_numberTwo distinct fields; normalise format before import
owner / account_ownerSales OwnerMap by user email; user must exist in Freshsales first14
lifecycle / statusLifecycle stage / Lead stagePicklist values case-sensitive11
tagsTagsSemicolon-delimited string in CSV6
source / lead_sourceLead sourcePre-create missing dropdown options before import
territoryTerritoryConfigure territory assignment rules before load so they run on the import9

Accounts (Sales Accounts)

Common source → Freshsales Account mapping
SourceDestinationNote
company_namename (required)Freshsales Accounts module — name is the human upsert key
website / domaincf_domain_name (custom field)Create as unique custom field; use as unique_identifier_name in bulk_upsert4
industryindustrySingle-select; pre-create missing options
annual_revenueannual_revenueNumber — strip currency symbols
parent accountParent Account lookupSet in a second pass once both parents and children are loaded

Deals and pipelines

Recreate every sales pipeline and every deal stage in Freshsales before importing deals. Each stage has a numeric probability that drives forecasting; build the mapping table source-stage → Freshsales-pipeline + Freshsales-stage-name. Deals whose stage value does not match any stage on the named pipeline are rejected by the importer with no automatic remap.

If you are consolidating multiple source pipelines, the cleanest approach is to keep them as separate Freshsales pipelines for at least 90 days post-migration, then merge once reporting has stabilised. The Deal value field is mandatory in Freshsales — if your source records carry null or blank amounts, populate them with 0 before import, as the Freshsales Support team explicitly recommends, or the rows will fail9.

Common source → Freshsales Deal mapping
SourceDestinationNote
deal_name / opportunity_namedeal_nameRequired
stage / pipeline_stagedeal_stageCase-sensitive; must exist on the named pipeline
amountdeal_valueMandatory — backfill blanks with 09
close_dateexpected_closeYYYY-MM-DD; watch the off-by-one timezone bug5
ownerSales OwnerMap by user email; deal owner drives forecasting
primary_contactRelated Contacts (semicolon-delimited emails)For multiple contacts per deal, separate emails with ;19
account / organisationSales Account lookupUse account name or cf_domain_name in a second pass

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only the custom fields used by an active process or report in the last 12 months. Freshsales caps custom fields per entity at 10 (Blossom), 150 (Garden), 305 (Estate) or 450 (Forest)3 — and the CRM Migration tool's auto-mapping requires the destination custom field to exist with the exact same name as the source column, so every extra field is also extra prep work.

For picklist fields whose source values do not match the destination, either: (1) extend the destination dropdown with the missing options pre-import, (2) collapse adjacent values during transform, or (3) introduce a parallel custom field that holds the legacy value verbatim. Formula fields are Enterprise / Forest only and do not import — they are recomputed on-platform, so any source formula must be rebuilt as a Freshsales formula field on Forest or replicated via Workflow Automation on lower tiers.

Historical activities — notes, tasks, appointments, email and call history

Notes, Tasks and Appointments can be loaded via CSV import, each row carrying its own created_at and target record. For historical email conversations, Freshsales ships a Past Email Sync option under Profile icon → Connect Email → Edit Sync Settings, which pulls Gmail or Outlook threads and matches them to existing Contact and Lead records13.

Historical email sync can be configured per user profile only once13, so users must exist and have mailboxes connected before the sync window is set. Past call logs from third-party telephony providers rarely round-trip — the fallback is to attach a flat call-summary note per record with the original timestamp in the body text.

Files and attachments

Attachments do not import in bulk via the CSV path. The supported path is the Files feature — note attachments cap at 20 MB per file20, standalone documents in the Files module accept up to 150 MB per file21, and total storage scales with seat count at roughly 2 GB per user on paid plans22.

For large attachment estates, the pattern most teams adopt is: keep originals in S3 or Google Drive, store a deep-link URL in a custom field on the parent record, and only upload the most recent subset inline. There is no native batch file-import path, so attachments are attached per record in the UI after parents land.

Audit trail, ownership and original timestamps

Standard created_at and updated_at are system-managed — they are stamped on import day and cannot be overwritten during a CSV load. To preserve the original audit trail, create two custom fields per module — Legacy Created Date and Legacy Created By — and populate them from the source export.

Owner assignment during import works only if the Sales Owner column contains the email of a user who already exists in Freshsales14. Rows whose owner cannot be resolved fall to the importing admin, which silently breaks owner-scoped views, territory rules and Workflow Automations that filter by owner.

CRM-specific: lead scoring, Sales Sequences, Freddy AI, email/calendar sync

Freshsales Lead Score is computed by Freddy AI on the Pro plan and above, based on contact properties, deal stage transitions and engagement signals. Scoring models do not import — they accrue forward once the data lands. If you must preserve historical scores, put them in a Legacy Lead Score custom number field.

Sales Sequences (multi-step email cadences) do not have an import mechanism — recreate them manually under Sales Sequences → Create New and re-enroll active prospects post-cutover. Workflow Automations, IntelliAssign rules and Smartforms are rebuilt the same way.

Email and Calendar Sync (Gmail / Outlook) is connected per user under Profile icon → Connect Email after users are provisioned13. Do not enable two-way sync during the import window or you will get a flood of duplicate engagements as the connector backfills the same Contacts you are loading.

The pitfalls that derail Freshsales migrations

Nine specific failure modes — ranked by impact, each tied to the exact Freshsales mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and users being allowed in. Freshworks Support's own best-practice flow recommends a deliberate three-stage validation: a sample test load, full review of the error-log email, and a final run after errors are resolved9. The most reliable signal is having department reps verify their own records — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

  • Total Contacts and Leads imported vs source — minus deliberately excluded rows (role-based emails, bounced lists, opt-outs).
  • Total Accounts imported vs source — checking that name-based collapse did not over-merge two legitimately separate companies.
  • Total Deals per pipeline per stage vs source, plus sum of deal_value per pipeline — a non-trivial dollar variance usually signals a stage-mapping error or a currency-precision drop.
  • Total Notes / Tasks / Appointments per type imported vs source — and a date-bucketed comparison to confirm activity dates round-tripped.
  • Lookup integrity — count Contacts with a populated Account, Deals with a Primary Contact, and Deals with an Account; compare against the source-derived expected counts.
  • Owner distribution — group by Sales Owner and confirm no record landed under the default importing admin that should have been assigned to a specific rep14.
  • Unique-identifier integrity — count distinct emails on Contacts and Leads; any duplicates indicate the dedup transform missed a case-variant or the same person was loaded into both modules.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across modules and verify each field against the source UI. Pick five high-value deals and trace the full lookup graph — primary Contact, Account, Products, Notes, Appointments. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by external ID.

Freshsales does not ship a bulk-undo for imports. The Recycle Bin holds deleted records and supports restoration, but the documentation explicitly notes that you can only bulk-delete records from one page at a time23 — there is no one-click rollback for a multi-thousand-row import. The Recycle Bin retains deleted records for a limited window before purge, after which only a Freshworks Support ticket can recover them.

The practical rollback strategy is therefore: export everything to S3 before the import starts, stamp every imported row with an Import Batch ID custom field, and if catastrophe strikes, filter by that batch ID and bulk-delete page by page, then re-import from the cleaned source. The Freshworks Best Practices article explicitly recommends this cycle — fix errors, delete records, rerun full migration9.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported through the UI or CRM Migration tool with the same unique-identifier column; (4) reconciliation runs; (5) users get login access and a 48-hour hyper-care window with the migration lead on call; (6) source decommission is scheduled for 30 to 90 days out, never the same day.

Migration partners and tools

Freshworks Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.

The Freshworks Partner Directory lists Authorized, Authorized Platinum, Distributor and Service Partner tiers across more than 50 countries24. For Freshsales migrations specifically, partners with explicit Salesforce-to-Freshsales, HubSpot-to-Freshsales or Pipedrive-to-Freshsales practices tend to ship cleaner than generalist Freshdesk-leaning implementation shops, because the data-model nuances of the Contacts/Leads split and Sales Sequence rebuild are not the same skill set as ticket-system migration.

A5 Solutions, Abano and the broader Authorized Platinum tier appear in the directory as named regional resellers and implementation partners24. Freshworks itself also operates an internal Data Migration team that handles the CRM Migration tool's queued large-volume runs (over 25,000 records, 1–2 business days off-peak) at no additional cost as part of the subscription12.

On the ETL and iPaaS side, Airbyte, Fivetran, Stitch and Matillion all have Freshsales connectors. Their role in a migration is rarely the migration itself — they are the staging layer that lands source data into a warehouse, the transformation layer that converts picklist case and resolves Sales Owner emails to existing Freshsales users, and the ongoing-sync layer that takes over once the one-time migration is complete.

Hevo Data publishes a dedicated Freshsales pipeline that rebuilds the source schema in the warehouse for downstream consumption.

Managed-migration cost ranges vary widely. A clean Pipedrive-to-Freshsales move of under 25,000 contacts with no historical activities and standard modules only often lands in the $500–$3,000 range with a setup fee plus per-object pricing. A Salesforce-to-Freshsales project with deal history, Custom Modules, historical activities and Marketo decoupling typically runs $5,000–$30,000, with the upper end driven by record count, custom-field complexity, historical-data depth and the number of integrations that need rebuilding rather than re-pointed.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Freshsales migrations and handles the field mapping, Contacts/Leads boundary decisions, picklist case normalisation, historical-data preservation and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count and source platform, with separate line items for Custom Modules and historical activity depth so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a regional Authorized Partner, the in-house Freshworks Data Migration service, an iPaaS-first warehouse approach, or a specialist migration vendor. [Explore FlitStack →](/contact)

Freshsales migration checklist

An atomic, phased task list for moving sales data into Freshsales — covering scope, prep, export, transform, sandbox test, cutover, validation, and post-cutover cleanup. Typical timeline: 4–10 weeks.

0. Decide & Plan11 tasks
  • Document the full list of Freshsales modules in scope. Freshsales has Contacts, Leads (Suite only), Accounts, Deals, Products, Sales Activities, plus optional Custom Modules. Confirm which are in scope and which are deliberately out of scope.If skipped: Discovering at cutover that Custom Modules or the Leads/Contacts split were assumed but never planned forces re-scoping mid-migration.
  • Decide whether you are targeting Freshsales (Sales-only) or Freshsales Suite. Suite reintroduces a separate Leads module on top of Contacts and bundles Freshmarketer features. The schema and field-mapping decisions differ between the two products.If skipped: Mapping all source leads into Contacts on Suite collapses the Leads pipeline and breaks lead-conversion reporting.
  • Confirm the target plan tier and its custom-field ceiling. Custom-field caps per entity are 0 (Sprout/Free), 10 (Blossom/Growth), 150 (Garden/Pro), 305 (Estate), and 450 (Forest/Enterprise). Custom Modules add a separate cap on Forest.If skipped: Buying Growth and discovering you need 200 custom fields on Contacts blocks the migration until billing is escalated.
  • Confirm Sandbox availability on the chosen plan. Sandbox is restricted to Forest / Enterprise. Only Org Admins can create one, and only one Sandbox can exist at a time. Trial accounts cannot use Sandbox.If skipped: Planning a sandbox test on a plan below Forest forces you to dry-run on production or upgrade mid-project.
  • Define historical-data scope by object. Decide how many years of closed deals, completed sales activities, notes, calls, and email threads you will move. Decide whether attachments are in scope.If skipped: Pulling all history by default can multiply the dataset 5–10x and blow through the cutover window.
  • Identify GDPR data-residency and retention requirements. Freshworks processes Personal Data across US, UK, and EEA regions and operates under the EU-U.S. and Swiss-U.S. Data Privacy Frameworks. Confirm which region your tenant uses satisfies any contractual residency commitment.If skipped: Discovering after cutover that your tenant is in the wrong region forces a second migration or a contractual exception.
  • Confirm SOC 2 and ISO 27001 evidence needs. If your auditors require evidence packs at cutover, request the latest Freshworks certification reports before the freeze date.
  • Assign a single accountable migration owner (DRI). One named person owns scope decisions, cutover go/no-go, and post-migration sign-off. Document their backup.
  • Document explicit out-of-scope items. List the source-system features that will NOT be rebuilt in Freshsales — chat transcripts, marketing automation flows, third-party telephony recordings, etc. Get sponsor sign-off in writing.If skipped: Unwritten out-of-scope items resurface as urgent during cutover and derail the schedule.
  • Set the target cutover date and source-system freeze window. Pick a low-activity window (often a Friday evening through Sunday). Communicate the freeze date and time to all source-system users at least two weeks in advance.
  • Define written success criteria for the migration. Examples: 100% of open deals migrated with correct stage; aggregate pipeline value within 0.5% of source; all owners assigned correctly; sales activities linked to the right Contact, Account, or Deal.If skipped: Without falsifiable criteria, the migration is never formally complete and tail issues drag on for months.
1. Pre-Migration Prep23 tasks
  • Run dedup analysis on source Contacts using lowercase email as the primary match key. Resolve duplicate contacts at the source before export. Freddy AI offers duplicate detection inside Freshsales from the Pro plan up, but cleaner source data produces cleaner results.If skipped: Importing duplicates forces you to rebuild deal-to-contact associations against the wrong record after dedup.
  • Run dedup analysis on source Accounts using domain as the match key. Normalize company-name variations (Acme Inc., Acme Incorporated, ACME) to a single canonical form.
  • Standardize email casing to lowercase across all Contact and Lead records. Mixed-case email values create silent duplicates against the lowercase keys Freshsales uses for matching.
  • Normalize phone-number formats to E.164 with country code. Freshsales stores phone as text; agree on one format (+15551234567) and apply it before export.
  • Identify and resolve source records missing values that will be mandatory in Freshsales. Last Name is required on Contacts/Leads, Account Name is required on Accounts, and Deal Value is required on Deals. Records missing these are reported in the import error log.If skipped: Mandatory-field misses produce a skip log at import; without a triage plan you lose visibility into what failed.
  • Standardize country, state, and currency code values to a controlled vocabulary. Freshsales picklist matching is case-sensitive. "USA" and "usa" land as different values unless one is fixed at the source.
  • Export baseline record counts per module as of the export timestamp. Capture counts for Contacts, Leads, Accounts, Deals, Sales Activities, Notes, and Custom Modules. These become the reconciliation target.
  • Identify and quarantine source records with invalid or non-UTF-8 characters. Freshsales' CSV/XLSX parser expects UTF-8. Latin-1 or Windows-1252 bytes corrupt non-ASCII names on import.If skipped: Encoding bugs surface as garbled characters across thousands of records and are painful to detect post-load.
  • Provision the Freshsales tenant on the target plan. Confirm currency, default timezone, and fiscal year are set before any import. These cannot be changed silently mid-migration.If skipped: A timezone mismatch shifts all imported dates by hours and surfaces as off-by-one-day errors on date-only fields.
  • Create all users in Admin Settings > Users with the exact email addresses used in the source export. The import maps the Owner column by user email. Users must exist before you map records to them. Add every active user from the source plus a dedicated 'data-migration' service user.If skipped: Missing owners get reassigned to the importer, breaking owner-based views, territories, and reports.
  • Configure role-based access control and field-level permissions before import. Defining roles upfront avoids retro-fitting permissions across thousands of imported records.
  • Create all required custom fields on Contacts, Leads, Accounts, Deals, and Custom Modules. Use exact field names matching the source export so the CSV/XLSX importer auto-maps. Importing into a field that does not exist silently drops that column.If skipped: Custom field mismatches only surface during the import preview, blocking thousands of records mid-cutover.
  • Create all picklist (dropdown / radio / checkbox) values in the destination before import. Freshsales drop-down matching is case-sensitive. Add every source value, then audit for typos and trailing whitespace.If skipped: Unmatched picklist values are dropped or rejected per row — the error log balloons and import time multiplies.
  • Configure multi-select fields and confirm semicolon delimiter handling in the import file. Freshsales expects multi-select values separated by semicolons inside a single CSV cell.
  • Build the deal pipelines and stage values in Admin Settings. Re-create every pipeline and stage by name before deal import. Map source stage labels to destination stage labels on paper first.If skipped: Missing stages route deals into a default stage at import, breaking pipeline reporting on day one.
  • Build the Custom Modules and their fields if Custom Modules are in scope. Custom Modules are only available on Forest. Confirm the plan, then define the module schema before importing records.
  • Configure Territories and Lead Score rules in draft (paused) state. Defining the rules upfront lets you run them against imported records once cutover completes.
  • Pause Workflows, Smartforms, IntelliAssign, and Sales Sequences for the cutover window. Active automations on the destination fire as records arrive — auto-emails and owner reassignments can result.If skipped: Forgetting to pause workflows triggers thousands of unwanted emails or owner reassignments during the load.
  • Disable email and calendar sync for the cutover window. 2-way email sync ingests messages as soon as a Contact is created, polluting the activity timeline before validation.
  • Provision the Sandbox account via Admin Settings > Other SFA Settings > Sandbox. Sandbox is gated to Forest/Enterprise and is admin-only. Building the sandbox can take time depending on account size; trigger it well before Phase 4.If skipped: Discovering Sandbox is unavailable on your plan forces you to test on production.
  • Communicate the freeze window to all source-system users in writing. Two weeks ahead and again 48 hours ahead. Name the freeze start/end, the read-only date, and the destination login.
  • Schedule role-based training sessions on Freshsales basics. Cover Contacts vs Leads (on Suite), Deals and pipelines, Sales Activities, Sales Sequences, and the mobile app for field reps.
  • Designate first responders for the first 48 hours post-cutover. Name two admins (primary + backup) who will triage user issues, monitor the error log, and decide on hot-fix imports.
2. Source Export12 tasks
  • Export Contacts to CSV/XLSX with all standard and custom fields. Confirm the file is under 5 MB before passing to the Freshsales UI importer; split into multiple files if necessary.If skipped: Files over 5 MB are rejected by the UI importer with no per-row diagnostic.
  • Export Leads to CSV/XLSX (only if targeting Freshsales Suite). Suite reintroduces a separate Leads module; classic Freshsales does not. Confirm the destination shape before exporting.
  • Export Accounts to CSV/XLSX with all standard and custom fields. Include the domain field; Accounts are typically matched on domain at import.
  • Export Deals to CSV/XLSX with all standard and custom fields. Include the email of the related Contact in a column you can map to Related Contacts. Multiple contacts per deal are supported via semicolon-separated emails.
  • Export Products to CSV/XLSX. Capture SKU, name, currency, base price, and tax for each product. These flow into deal product associations later.
  • Export Sales Activities (tasks, meetings, calls) as separate files. Each activity type has a slightly different schema. Include the linked Contact email and Deal name for re-association.
  • Export Notes with their parent-record references. Capture the linked Contact, Account, or Deal so notes can be re-attached during transform.
  • Export the user list with email, role, and reporting structure. Becomes the input for re-creating users in Admin Settings > Users in Phase 1b.
  • Export pipeline and stage definitions from the source CRM. Names, sort order, probability percentages, and any rotting logic. These drive the destination pipeline build.
  • Export all attachment binaries and a manifest mapping each file to its parent record. Freshsales caps note attachments at 20 MB and document attachments at 150 MB; storage is 2 GB per user across the account.If skipped: Attachments without a parent-record manifest become orphaned files post-load and are nearly impossible to re-link.
  • Capture screenshots and exported configs of source automations, reports, and dashboards. These are rebuilt by hand in Freshsales — Workflows, Smartforms, IntelliAssign, Sales Sequences, and dashboards do not transfer automatically.
  • Record the exact timestamp of every export. Cutover delta (Phase 5) is calculated against these timestamps.
3. Transform & Map27 tasks
  • Build a master mapping spreadsheet covering every source field. Columns: source object, source field, destination module, destination field, field type, transformation rule, required-on-import flag, picklist value mapping, nullability.If skipped: Without a single mapping document, transform logic diverges across files and reconciliation becomes impossible.
  • Resolve every picklist value mismatch between source and destination. Freshsales picklist matching is case-sensitive. Build a one-to-one value translation table per field (e.g. "Won-Closed" → "Closed Won").If skipped: Unmatched values are dropped or rejected per row, inflating the error log.
  • Choose the upsert key for each module. Email for Contacts/Leads, domain for Accounts, deal external ID or name+contact email for Deals. Each record needs exactly one unique identifier value.If skipped: Choosing a non-unique key creates duplicate records on re-runs and breaks idempotency.
  • Decide handling for source fields with no destination equivalent. Drop, concatenate into Notes, or create a Freshsales custom field. Document the decision per field.
  • Decide handling for source fields exceeding Freshsales character limits. Truncate, split, or move overflow to Notes. Apply consistently across all rows of the affected column.
  • Convert date fields to ISO-8601 with explicit timezone offsets. A community-reported bug shifts date-only values by one day when the source timezone differs from the destination. Stamp every date with an explicit timezone to neutralize it.If skipped: Off-by-one-day date drift surfaces as missed renewal dates and skewed cohort reports after cutover.
  • Normalize currency values to the destination's decimal format. Confirm thousands separator, decimal separator, and the configured base currency match the destination tenant setting.
  • Re-encode all CSV/XLSX exports as UTF-8 without BOM. Latin-1 or Windows-1252 bytes corrupt non-ASCII characters on import.
  • Convert multi-select values to semicolon-delimited strings inside a single CSV cell. Freshsales' importer expects "Value A;Value B;Value C" within a single column for multi-select fields.If skipped: Comma-delimited or array-shaped values are interpreted as a single literal string, breaking filter and reporting logic.
  • Escape commas, quotes, and newlines inside text fields per the CSV/XLSX spec. Wrap any value containing those characters in double quotes; double up embedded quotes.If skipped: Unescaped delimiters shift columns mid-row, silently corrupting downstream fields.
  • Truncate or split text fields exceeding destination character limits. Apply consistently and capture the truncated overflow in a Notes file if data preservation matters.
  • Lowercase every email value globally. Required so the dedup engine treats the same person consistently.
  • Validate every Owner column against the email of an existing Freshsales user. Records with an unmatched Owner email fall back to the importer or to a default owner depending on import settings.If skipped: Mass-defaulting to a single fallback owner breaks territory- and owner-based dashboards.
  • Decide and implement the strategy for original Created/Modified timestamps. Freshsales does not let imports override system-managed Created/Modified timestamps. Capture the source timestamps in dedicated custom fields (e.g. "Source Created Date", "Source Modified Date").If skipped: Losing original timestamps breaks time-based cohort reports and contract anniversary logic forever.
  • Decide and implement the strategy for record ownership. Best-match by email per the Owner column, or fall back to the dedicated 'data-migration' user. Document which records use which strategy and why.
  • Decide and implement the strategy for file attachments. Re-upload binaries (subject to 20 MB note-attachment and 150 MB document caps and the 2 GB-per-user storage envelope) or preserve as external storage links in a custom field.If skipped: Hitting the 2 GB-per-user storage cap mid-load leaves attachments orphaned with no notification.
  • Plan the load order for parent-child relationships. Users → Accounts → Contacts/Leads → Deals → Sales Activities → Notes → Attachments. Children loaded before parents have nothing to reference.If skipped: Wrong load order produces orphaned records and forces a full re-import.
  • Map source Contacts/Leads into the Freshsales Contacts/Leads split. On Freshsales Suite, decide whether each source contact belongs in Leads (unqualified) or Contacts (qualified) and stamp a lifecycle stage. On Sales-only, everything goes to Contacts.If skipped: Collapsing Leads into Contacts on Suite breaks lead-conversion reporting; splitting them on Sales-only fails outright.
  • Map source Accounts to Freshsales Sales Accounts with the chosen unique identifier. Include a unique identifier value on every Account record so re-runs are idempotent.
  • Map source Deals to Freshsales Deals with explicit pipeline + stage references. Every Deal row must carry the destination Pipeline name and Stage name exactly. Include the Related Contact email column for primary-contact association.If skipped: Unmatched pipeline/stage values route deals into a default stage, breaking pipeline reporting on day one.
  • Plan the rebuild of Sales Sequences in Freshsales after the data load completes. Sales Sequences (Freshsales' email cadence engine) do not transfer from other CRMs. Document the source cadences and rebuild them in Admin Settings > Sales Sequences after Phase 5.
  • Plan the rebuild of IntelliAssign rules for round-robin lead routing. IntelliAssign distributes new Leads/Contacts to reps by territory, availability, and skill. Capture source assignment rules and reproduce them post-load with workflows paused.If skipped: Activating IntelliAssign during the load reassigns thousands of migrated records to the wrong owners.
  • Plan the rebuild of Workflows and Smartforms. Workflows (automation), Smartforms (web-form lead capture), and their triggers must be hand-rebuilt. Capture each source automation's trigger, conditions, and actions before cutover.
  • Plan the rebuild of Custom Modules if in scope. Forest-only. Define the module's fields, relationships to standard modules, and field-level permissions before importing module records.
  • Plan the rebuild of Territories and Lead Score models. Territories segment records by geography or product line; Lead Score derives a numeric score from rules and Freddy AI signals. Both must be re-derived in Freshsales after the data lands.If skipped: Skipping the Lead Score rebuild leaves reps prioritizing leads by an arbitrary default order on day one.
  • Plan the Freshmarketer / Freshsales Classic plan-mapping if migrating from a Freshworks Classic product. The Freshworks-shipped migration maps Sprout → Free, Garden → Pro, and Estate → Enterprise. Pricing is grandfathered until you choose to upgrade or downgrade.
  • Decide which import path to use per module. The Freshworks-shipped CRM Migration importer handles up to 25,000 records instantaneously and queues larger batches into off-peak windows (typically 1–2 business days). Choose the path that matches each module's volume and the cutover window.
4. Sandbox Test Migration11 tasks
  • Load a 1–5% representative sample of every in-scope module into Sandbox. Use the same import path (UI CSV/XLSX upload) you plan to use in production.If skipped: Testing with a different mechanism than production hides path-specific bugs (CSV row caps) until cutover.
  • Validate field-by-field on 10 random Sandbox records per module. Open each record in the UI and confirm every standard and custom field carries the expected value.
  • Run an edge-case battery: long strings, special characters, NULLs, picklists, and dates across timezones. Include the date-field timezone-shift case explicitly — pick records spanning midnight in non-UTC timezones.If skipped: Edge-case bugs unfound in Sandbox become incidents in production with no rollback option.
  • Test Contact-to-Account, Deal-to-Contact, and Deal-to-Account associations. Confirm related-contacts on Deals carry semicolon-delimited multiple emails correctly.
  • Test Sales Activity association to parent Contacts and Deals. Open a few Deals in the UI and confirm the activity timeline shows the expected tasks, meetings, and calls.
  • Test Note attachment to parent records. Confirm notes attach to the correct Contact, Account, or Deal and that any attached files are accessible.
  • Test the file-upload path for binaries within the 20 MB note-attachment and 150 MB document caps. Confirm storage consumption against the 2 GB-per-user envelope as you go.If skipped: Hitting the storage cap mid-Sandbox-test means the production load will fail at the same point.
  • Time each load step and extrapolate to production volume. Confirm the projected total load time fits inside the cutover window. Factor in the 25,000-record instantaneous limit on the CRM Migration importer.If skipped: A 12-hour cutover that becomes a 36-hour cutover blows past the freeze window and forces an extended outage.
  • Confirm the Sandbox error log shape and capture the diagnostic columns. The Freshsales importer emails an error log per import job. Document its columns so triage during cutover is fast.
  • Have a domain expert from sales operations spot-check 25 Sandbox records. An ops user often catches business-logic errors (wrong pipeline stage, wrong territory) that the technical team misses.
  • Get written sign-off on the Sandbox test results before scheduling production cutover. Sign-off names the issues found, the fixes applied, and the residual known-risks accepted.If skipped: Skipping written sign-off means scope drift between Sandbox and production goes undetected.
5. Production Cutover12 tasks
  • Confirm the source-system freeze is in effect and verify no writes in the last hour. Inspect the source audit log; reject the cutover if the freeze was not honored.
  • Take a final full export of source data as the cutover baseline. The delta from the Phase 2 baseline is what you reconcile in Phase 6.
  • Disable Workflows, Smartforms, IntelliAssign, Sales Sequences, and email/calendar sync. Confirm every automation that could fire on a record-create is off.If skipped: An active workflow during load can send thousands of unwanted emails or reassign owners en masse.
  • Load Users first if any new users were added since Phase 1. Owner mapping fails on missing users; create them before importing the records they own.
  • Load Accounts via the CRM Migration importer. Use the chosen unique identifier on every record so re-runs are idempotent.If skipped: Skipping unique identifiers causes duplicate Accounts on any retry.
  • Load Contacts/Leads next using the matching importer path. Carry the Account email/domain in a column that maps to Sales Account, so the contact-to-account association lands on first write.
  • Load Deals with explicit Pipeline + Stage + Related Contacts columns. Include the deal owner email so deals do not all default to the import service user.If skipped: Defaulting all deals to the service user breaks pipeline-by-owner dashboards immediately.
  • Load Sales Activities, Notes, and attachments last. Activities and notes need their parent Contacts, Accounts, and Deals to exist first; attachments need their notes/records to exist first.
  • Capture import job IDs, row counts, and error logs for every load step. Archive the importer's email error log for each UI-driven import.If skipped: Without job-level evidence, a failed reconciliation cannot be traced back to a specific load step.
  • Cross-check destination row counts against source counts at each step. Stop and diagnose if any module's count diverges by more than the agreed tolerance (typically 0.1%).
  • On a failed load step, stop, fix the transform, and re-run idempotently against the same upsert key. Idempotent upserts on the unique identifier avoid duplicate creation on re-runs.
  • Re-enable Workflows, Smartforms, IntelliAssign, Sales Sequences, and email/calendar sync only after Phase 6 sign-off. Validating before unpausing automations contains the blast radius of any defect found post-load.If skipped: Unpausing before validation means a defect cascades through emails and owner reassignments to external systems.
6. Validate16 tasks
  • Compare total record count per module: source vs Freshsales. Cover Contacts, Leads, Accounts, Deals, Sales Activities, Notes, Custom Modules, and Attachments. Investigate any delta.If skipped: A 100-record gap that is not reconciled is 100 customer relationships silently missing from day one.
  • Compare aggregate pipeline value per stage between source and destination. Sum Deal Value per Pipeline + Stage and compare. Variance should be within 0.5% (rounding only).If skipped: A stage-mismatch defect shifts millions in pipeline into the wrong forecast bucket and skews quota attainment reports.
  • Cross-check 25–50 randomly selected records field-by-field between source and destination. Use a stratified sample: a few records per pipeline, owner, territory, and lifecycle stage.
  • Verify every custom field carries its expected value on the sample. Picklist mismatches and silently-dropped columns surface here most often.
  • Verify Contact-to-Account associations on a sample of 25 records. Open each in the UI and confirm the Sales Account name and ID match expectations.
  • Verify Deal-to-Contact and Deal-to-Account associations on a sample of 25 deals. Confirm Related Contacts shows the expected semicolon-delimited list of emails.
  • Verify Sales Activities are linked to the correct Contact, Deal, or Account. Open Account and Deal activity timelines and confirm tasks, meetings, and calls appear as expected.
  • Verify Notes are attached to the correct parent records. Spot-check 20 notes across Contacts, Accounts, and Deals.
  • Verify file attachments are accessible and download cleanly. Open 10 random attachments; confirm filename, size, and content match the source manifest.If skipped: An attachment that is reachable but corrupt is not flagged by Freshsales — only end users notice, often weeks later.
  • Verify the Source Created Date and Source Modified Date custom fields carry the original timestamps. Spot-check 25 records. System-managed Created/Modified will show the import timestamp; the custom fields preserve the original.If skipped: Without the original timestamps, time-based cohort and contract-anniversary reports are silently broken forever.
  • Run the configured compliance check for your tenant's region. GDPR data-residency confirmation for EU tenants; SOC 2 evidence collection for audited orgs.
  • Archive the source export, the transformed files, and the import error logs to long-term storage. Required for forensic look-ups and audit defense for the contracted retention period.
  • Have 3–5 power users validate their day-to-day workflows in Freshsales against the migrated data. Cover SDR (Leads + Sales Sequences), AE (Deals + activities), sales ops (reports), and a CSM if applicable.
  • Capture every UAT-surfaced data issue in a triage log with severity, owner, and fix-by date. P0 issues block sign-off; P1/P2 are documented and triaged post-cutover.
  • Rebuild the top 3–5 source reports in Freshsales dashboards and compare numbers. If a key report cannot be reproduced within 1% of source, the underlying schema or stage mapping is off.
  • Obtain written sign-off from the migration sponsor before proceeding to Phase 7. Sign-off names the validation evidence, the P1/P2 backlog, and the agreed go-live date.If skipped: Skipping sign-off means scope ambiguity at the 30-day retro and unclear ownership of post-cutover issues.
7. Post-Migration Cleanup13 tasks
  • Communicate go-live to all end users with login URL, SSO instructions, and the help contact. Include a short FAQ covering 'where did my X go' for the five most common source-system features.
  • Run role-segmented Freshsales training sessions. SDRs (Leads + Sales Sequences), AEs (Deals + activity logging), sales ops (reports + workflows), CSMs (Accounts).
  • Set the source system to read-only and announce the read-only date in writing. Read-only prevents accidental drift; archive the source tenant for the contracted retention window before decommission.If skipped: Leaving the source writable creates two systems of record and guarantees data drift within weeks.
  • Rebuild dashboards and reports in Freshsales. Reports do not transfer. Reproduce the top 10 source reports first; backfill the long tail over the following month.
  • Rebuild Workflows and Smartforms in Admin Settings. Re-create each source automation against the Phase 2 screenshots. Test with a single record before flipping live.
  • Rebuild Sales Sequences (email cadences). Re-create each source cadence with its email templates, delays, and exit conditions. Test against a single contact first.If skipped: Re-enrolling thousands of contacts into a buggy sequence causes mass-unsubscribes and brand damage.
  • Activate IntelliAssign rules and confirm round-robin distribution behaves as expected. Test by creating one new lead and verifying it routes to the expected rep.
  • Activate Territories and Lead Score models. Confirm Lead Score values populate against the migrated Contacts/Leads within the first 24 hours.
  • Re-establish email and calendar sync for every user. Each user must individually connect their email; sync settings can only be configured once per profile.
  • Re-establish integrations to BI tools, marketing automation, and telephony. Confirm all integrations are pointed at the new Freshsales tenant, not the source.
  • Schedule the 30-day post-migration retrospective. Capture what worked, what did not, and what the next migration should change. Distribute the notes.
  • Document the source-system decommission date. Typically 90 days after cutover, after the contracted retention window closes. Calendar the date with the source vendor.
  • Close out the migration project formally with a final status report and lessons-learned doc. Record cutover duration, defect counts, reconciliation deltas, and total cost. Hand off to the operations owner.

Questions, answered

Migrating to Freshsales: questions

How long does migration to Freshsales take?

A small-business migration with under 25,000 records and standard modules runs as an instantaneous load through the CRM Migration tool, typically same-day. Mid-market projects with deal history, Custom Modules and historical activities run two to four weeks of elapsed time, including preparation, dry runs, validation and a 48-hour hyper-care window.

Can I migrate from Salesforce to Freshsales?

Yes — Freshworks ships a dedicated Salesforce importer that accepts the standard Salesforce data-export zip and loads Leads, Contacts, Accounts, Opportunities, Events and Tasks CSV files directly. Apex, Flows and AppExchange-bound automations do not transfer; rebuild them as Freshsales Workflow Automations, Sales Sequences and Freddy AI scoring rules from scratch.

Can I migrate from HubSpot to Freshsales?

Yes, and HubSpot-to-Freshsales is a common move driven by contact-tier pricing creep. Export Contacts, Companies, Deals and Engagements from HubSpot, normalise picklist case to match Freshsales options, then load through the CRM Migration tool or the UI Import. Rebuild HubSpot Workflows as Freshsales Workflow Automations after the data lands.

Can I migrate from Pipedrive to Freshsales?

Yes — Freshworks ships a dedicated Pipedrive importer that accepts a Pipedrive zip export and auto-maps default plus custom fields by exact name. People, Organisations and Deals map cleanly to Contacts, Accounts and Deals; Activities map to Tasks and Appointments. Up to 25,000 records load instantaneously; larger sets queue off-peak.

Does Freshsales preserve original timestamps on import?

Partially. Notes, Tasks and Appointments can be loaded with their original `created_at` timestamps. But system fields `created_at` and `updated_at` on Contacts, Accounts and Deals are stamped to import day and cannot be overridden. Use Legacy Created Date custom fields to preserve the original audit trail per record.

What's the difference between using the UI import and the CRM Migration tool for Freshsales?

The UI Import accepts CSV / XLSX files up to 5 MB per file and is best for one-shot loads under 25,000 records with a visual mapping step. The CRM Migration tool ships pre-built importers from Pipedrive, Salesforce, Zoho and HubSpot, ingesting the source platform's own zip export directly.

Can I migrate Custom Modules to Freshsales?

Yes, but Custom Modules require a Forest / Enterprise subscription, and the per-module field cap is 310 custom fields. Define the Custom Module schema, its lookup fields and its association to standard modules before importing any records of that type. Records load through the same paths as standard modules.

What happens to deal pipelines and stages during migration?

Recreate every pipeline and every deal-stage name in Freshsales before importing deals — rows targeting non-existent stages are rejected. Stage history is not auto-preserved; if you need it for reporting, export stage transition timestamps from the source and store them in custom date fields such as Stage Entered Date.

Get a quote

Moving to Freshsales?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Freshsales setup with you, then send a quote.

Get a quote