CRM migration

Migrate from InTouch CRM to Freshsales

Field-level mapping, validation, and rollback between InTouch CRM and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

InTouch CRM logo

InTouch CRM

Source

Freshsales

Destination

Freshsales logo

Compatibility

67%

6 of 9

objects map 1:1 between InTouch CRM and Freshsales.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from InTouch CRM to Freshsales is a schema-remodeling migration. InTouch stores Contacts with inline company data, defined Pipelines with custom stages, and Activities against records. Freshsales separates Contacts from Accounts, requires explicit deal stages, and maintains a distinct Leads module for unqualified prospects. We resolve these structural differences during scoping, remap InTouch pipeline stages to Freshsales Deal Stages, and preserve InTouch activity timestamps through Freshsales bulk import. Custom fields and custom field types in InTouch require pre-creation in Freshsales before migration begins, which adds a schema preparation phase not required in same-platform moves. InTouch has no publicly documented bulk API, so all data moves through CSV with careful field type validation, date format normalization, and owner email resolution. Workflows, automations, and lead scoring models do not migrate; we deliver a written inventory for the customer's admin to rebuild in Freshsales.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

InTouch CRM logo

InTouch CRM

What's pushing teams away

  • Limited advanced customization — Capterra UK reviewers cite the lack of flexible reporting, integrations, and dashboard customization as the main reason teams outgrow the platform.
  • Integration ecosystem is narrow compared to mainstream SMB CRMs (HubSpot, Pipedrive, Zoho), pushing teams with custom tech stacks to switch.
  • Reporting and analytics are basic, prompting data-driven teams to move to platforms with richer BI integration.
  • Small public review base (mostly Capterra UK) limits peer-reference signal, making procurement teams hesitant when scaling up.
  • No publicly documented bulk API restricts modern automation workflows, so power users hit the integration ceiling earlier than on platforms with open developer ecosystems.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • 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.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How InTouch CRM objects map to Freshsales

Each row shows how a InTouch CRM object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

InTouch CRM

Contact

maps to

Freshsales

Account + Contact (split required)

1:many
Fully supported

InTouch Contact records carry inline company fields (company name, address, phone). We split these during migration by creating Freshsales Account records first (using the InTouch company name as the Account Name) and then creating Freshsales Contact records linked to those Accounts via the AccountId lookup. Any InTouch Contact without a company name maps to a single Contact without an AccountId, held for customer review.

InTouch CRM

Company (inline on Contact)

maps to

Freshsales

Account

1:1
Fully supported

The company portion of each InTouch Contact becomes a Freshsales Account. We use company name as the dedupe key to avoid duplicate Accounts when multiple Contacts share the same company. The original InTouch company phone, website, and address fields map to the corresponding Account fields. Any duplicate company names are resolved by appending a sequence suffix after customer review.

InTouch CRM

Deal

maps to

Freshsales

Deal

1:1
Fully supported

InTouch Deals map to Freshsales Deals. Each InTouch Pipeline becomes a Freshsales Sales Flow, and InTouch pipeline stages map to Freshsales Deal Stages with probabilities remapped to the 0-100 integer scale Freshsales requires. Deal value and close date migrate directly. We flag any Deal without an associated Contact for the customer to resolve before import.

InTouch CRM

Pipeline

maps to

Freshsales

Sales Flow + Deal Stage

lossy
Fully supported

Each InTouch Pipeline is recreated as a Freshsales Sales Flow with its stages defined as Deal Stages in Admin settings. We preserve InTouch stage ordering and probability values, normalizing percentages to integers. If InTouch used multiple pipelines for different product lines, each becomes a separate Sales Flow in Freshsales.

InTouch CRM

Activity: Call

maps to

Freshsales

Task (type = Call)

1:1
Fully supported

InTouch call records map to Freshsales Task with Task Type set to Call. Call duration, disposition, and recording link (if available) transfer to custom Task fields. Activity timestamp from InTouch becomes the Freshsales Task Due Date to preserve timeline ordering.

InTouch CRM

Activity: Email

maps to

Freshsales

Task + Email

1:1
Fully supported

InTouch email activity migrates to Freshsales as a Task record with email body content. The email subject line becomes the Task Subject. We set the Task status to Completed and link to the parent Contact or Account via the WhoId and WhatId fields.

InTouch CRM

Activity: Meeting

maps to

Freshsales

Task (type = Meeting) or Event

1:1
Fully supported

InTouch meeting records map to Freshsales Task with Task Type set to Meeting, preserving title, date, and attendee information. If the customer uses Freshsales Calendar, meetings can alternatively map to Event records for calendar display.

InTouch CRM

Custom Field

maps to

Freshsales

Custom Field

lossy
Fully supported

InTouch custom fields require pre-creation in Freshsales Admin settings before migration begins. We map InTouch field types (text, number, date, checkbox, dropdown) to Freshsales field types (Single Line Text, Number, Date, Checkbox, Picklist). Picklist values in InTouch must be recreated as Freshsales Picklist options. Custom fields are created per module (Contact, Account, Deal) and the migration CSV references them by exact field name.

InTouch CRM

Owner

maps to

Freshsales

User

1:1
Fully supported

InTouch Owners map to Freshsales Users by email address. We resolve owners by email match against the Freshsales User table. Any InTouch Owner without a matching Freshsales User is held in a reconciliation queue. The customer provisions missing Users before record import resumes because OwnerId is required on most standard objects in Freshsales.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

InTouch CRM logo

InTouch CRM gotchas

High

CSV-based import is the primary documented data path

Medium

Stage and pipeline label drift across customer instances

Medium

Limited custom-object surface

Low

All-in-one bundling means multiple modules' data must be reconciled

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • InTouch has no documented bulk export API

    InTouch CRM does not expose a publicly documented bulk export API, so all data extraction runs through CSV export from the platform UI. CSV export may be scoped by module (Contacts, Companies, Deals) and may not include all custom fields in a single export. We request multiple CSV passes with different field selections and combine them by record ID during transformation. If a field is not visible in the export UI, it may require manual extraction or API-based field-by-field reads, which extends the discovery and extraction timeline.

  • Freshsales date format validation rejects non-matching imports

    Freshsales validates date formats during CSV import against the date format set in Admin settings (Admin > CRM Settings > Date format). InTouch exports dates in its own format, which may differ from Freshsales. We normalize all date values during the transformation step to match the destination date format before CSV generation. Records with invalid date formats are rejected by Freshsales import and must be corrected and reimported, which adds a retry pass to the migration timeline.

  • Custom fields must be pre-created before CSV import

    Freshsales CSV import references custom fields by exact name, but the fields must exist in the destination org before import runs. InTouch custom fields do not automatically appear in Freshsales. We work with the customer's Freshsales admin to create all custom fields with matching types (text, number, date, picklist) before the migration CSV is generated. Any missing custom field causes the import column to be silently ignored or to error, which may not surface until post-import reconciliation.

  • InTouch workflow automations do not migrate

    InTouch workflow rules and automation triggers are platform-specific and have no Freshsales equivalent. We deliver a written inventory of every InTouch automation (workflow triggers, conditions, and actions) with a recommended Freshsales Workflow equivalent for the customer's admin to configure post-migration. Sales sequences and lead scoring models similarly do not migrate; the inventory document covers these as separate rebuild tasks.

Migration approach

Six steps for a successful InTouch CRM to Freshsales data migration

  1. Discovery and InTouch data extraction

    We audit the InTouch portal for record counts (Contacts, Companies, Deals, Activities), custom field names and types, pipeline names and stage definitions, owner list, and any integration points. Because InTouch lacks a bulk export API, we extract data via CSV in multiple passes, combining field sets by record ID. We identify any fields not visible in the export UI and flag them for manual extraction or API-based reads. The discovery output is a written data map and extraction plan.

  2. Freshsales schema preparation

    We create the Freshsales schema before any data loads. This includes creating all custom fields with correct types (matching InTouch field types to Freshsales field types), setting up Sales Flows that mirror each InTouch Pipeline, defining Deal Stages with probabilities, and configuring Record Types if the customer uses multiple lines of business. The customer provisions Freshsales Users for each InTouch Owner during this phase so that Owner mapping resolves during import.

  3. Data transformation and field mapping

    We transform extracted InTouch data through the mapping matrix. Contacts are split into Accounts (from InTouch company fields) and Contacts (linked to Accounts). Deals are mapped to Freshsales Deals with stage remapping. Dates are normalized to match the Freshsales date format. Custom field values are mapped to the new Freshsales field names. We generate separate CSVs per module (Accounts, Contacts, Deals, Activities) ready for Freshsales import.

  4. Test import and reconciliation

    We run a test import into a Freshsales sandbox or the production org with a subset of records (typically 100-200 per module) to validate field mapping, date format acceptance, and owner resolution. Any rejected records are diagnosed, corrected in the transformation layer, and retested. This step repeats until the rejection rate is below 1 percent before full import begins.

  5. Production import and validation

    We run the full import in dependency order: Accounts first (from InTouch company data), then Contacts (linked to Accounts), then Deals (with Contact and Account lookups resolved), then Activities. Each phase emits a row-count reconciliation report showing imported, skipped, and errored records. The customer spot-checks 25-50 records per module against the InTouch source before sign-off.

  6. Cutover, automation inventory handoff, and hypercare

    We freeze InTouch writes during cutover, run a final delta migration of any records modified during the migration window, then deliver the automation inventory document covering all InTouch workflows, sequences, and lead scoring models. We support a 5-business-day hypercare window for reconciliation issues. Workflow rebuild in Freshsales is outside migration scope and is handled by the customer's admin or a Freshsales implementation partner.

Platform deep dives

Context on both ends of the pair

InTouch CRM logo

InTouch CRM

Source

Strengths

  • All-in-one bundling of CRM, email marketing, direct mail, SMS, surveys, contact management, and task tracking in one platform
  • Strong fit for UK small businesses — Capterra UK reviewers consistently highlight ease of use and customer support
  • Flat per-user pricing keeps costs predictable as small teams grow
  • Automation features for email marketing, task tracking, and customer segmentation work out of the box
  • Email-to-CRM workflow described as seamless by users, useful for marketing-led small businesses

Weaknesses

  • Limited advanced customization options for reporting, dashboards, and integrations
  • No publicly indexed bulk API or developer portal
  • Small public review footprint outside Capterra UK
  • Custom objects beyond standard CRM entities are not supported
  • Vendor's UK focus may not suit US/international teams expecting global feature parity
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Moderate CRM migration. 1 of 8 objects need a manual workaround.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across InTouch CRM and Freshsales.

  • Object compatibility

    D

    1 of 8 objects need a manual workaround.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    InTouch CRM: Not publicly documented.

  • Data volume sensitivity

    B

    InTouch CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your InTouch CRM to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about InTouch CRM to Freshsales data migrations

Answers to the questions buyers ask most during InTouch CRM to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your InTouch CRM to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Deals with straightforward field mapping. Migrations with high custom field counts, multiple InTouch Pipelines requiring Freshsales Sales Flow configuration, or activity histories over 200,000 records move to six to ten weeks because of schema pre-creation, date format normalization, and CSV chunking work. The absence of a documented InTouch bulk export API adds one to two weeks to extraction compared to CRM-to-CRM migrations with standard REST APIs.

Adjacent paths

Related migrations to explore

Ready when you are

Move from InTouch CRM.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day