CRM migration

Migrate from InTouch to Freshsales

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

InTouch logo

InTouch

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between InTouch and Freshsales.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

InTouch CRM targets small businesses with a straightforward contact-and-deal model using contacts, companies, pipelines, and custom fields stored per matter template. Freshsales organizes data around Leads, Contacts, Accounts, and Deals with lifecycle-stage tracking, multiple pipeline support, and plan-gated features like Freddy AI scoring on Pro and above. We migrate InTouch contacts directly to Freshsales Contacts for existing customers and to Leads for unqualified prospects, using email matching to resolve owner assignments. Companies map to Accounts with parent-child hierarchy preserved via Freshsales's parent_account_id. InTouch deals become Freshsales Deals with pipeline stages value-mapped per pipeline. Custom fields transfer as Freshsales custom fields with type-aware transformations. Activity history (calls, emails, notes, tasks) migrates to Freshsales Sales Activities. Automations, email templates, and workflow rules do not transfer — we export InTouch workflow definitions as a reference document your Freshsales admin rebuilds with Freshsales's workflow builder. The migration uses Freshsales's API with rate-limit-aware sequencing; files re-upload to Freshsales's native file storage.

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 logo

InTouch

What's pushing teams away

  • Advanced customisation for dashboards, reporting, and workflow branching is limited, causing firms with complex or non-standard transaction types to outgrow the platform's flexibility.
  • The mobile app receives consistent criticism for poor usability and feature gaps compared to the desktop interface, which frustrates fee-earners who work on-site at properties.
  • The transition from the legacy flash-based version to the modern platform disrupted established users' workflows, and some firms report the learning curve on the new UI was steeper than expected.
  • Firms requiring deep third-party integrations with accounting software, Land Registry portals, or practice management suites find InTouch's native integration ecosystem too narrow for their needs.

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 objects map to Freshsales

Each row shows how a InTouch 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

Contact

maps to

Freshsales

Contact

1:1
Fully supported

InTouch contacts with a customer lifecycle status migrate directly as Freshsales Contacts. Unqualified contacts with no deal history route to Freshsales Lead. Owner resolution uses email matching against Freshsales user list; unmatched owners flag for admin assignment before migration commits.

InTouch

Contact (unqualified)

maps to

Freshsales

Lead

1:many
Fully supported

InTouch contacts that are early-stage prospects with no associated deals split to Freshsales Lead. Lead conversion mapping in Freshsales transfers field values to Contact, Account, and Deal on conversion — we pre-configure this mapping during schema planning to prevent data loss at conversion time.

InTouch

Company

maps to

Freshsales

Account

1:1
Fully supported

InTouch company records map 1:1 to Freshsales Accounts. Company name maps to Account Name, domain to Website, industry pick-list to Freshsales Industry with value-by-value mapping. Parent-child company hierarchy preserves via Freshsales parent_account_id — circular references flagged during validation. Including address and phone fields.

InTouch

Deal

maps to

Freshsales

Deal

1:1
Fully supported

InTouch deals migrate to Freshsales Deals with amount, close date, owner, and stage preserved. Pipeline stages value-map to Freshsales deal_stage pick-list per pipeline. If InTouch uses multiple pipelines, we create corresponding Freshsales pipelines and map stage sets independently. Ensuring deal amount formatting and probability overrides transfer correctly.

InTouch

Pipeline

maps to

Freshsales

Pipeline

1:1
Fully supported

Each InTouch pipeline becomes a Freshsales Pipeline. Pipeline-level stage definitions transfer as Freshsales stage entries within each pipeline. Stage order and probability weights map for forecasting continuity — custom probability overrides in InTouch become custom fields in Freshsales. Including stage-specific SLAs.

InTouch

Custom Field

maps to

Freshsales

Custom Field

1:1
Fully supported

InTouch custom fields scoped to matter templates map to Freshsales custom fields on the corresponding module (Contact, Account, Deal). Field type conversion handles text, number, currency, date, pick-list, and multi-select. Pick-list values map value-by-value; new Freshsales pick-list entries created when source values have no destination match.

InTouch

Call Log

maps to

Freshsales

Sales Activity (Call)

1:1
Fully supported

InTouch call logs transfer as Freshsales Sales Activities with type=Call. Original call duration, timestamp, and owner preserved. Call disposition notes migrate as activity notes. Parent record links (contact or company) re-established via Freshsales's activity association model. Including call recording URLs and outcome codes.

InTouch

Email Log

maps to

Freshsales

Sales Activity (Email)

1:1
Fully supported

InTouch email records migrate as Freshsales Sales Activities with type=Email. Subject line maps to activity subject, body to notes. Timestamps and sender/recipient information preserved. Email threading preserved via Freshsales conversation view for linked contacts. Including CC/BCC fields and attachment references.

InTouch

Note

maps to

Freshsales

Note

1:1
Fully supported

InTouch notes migrate to Freshsales Notes attached to the corresponding record (Contact, Account, or Deal). Rich-text formatting preserved where InTouch supports it. Note owner and create date transfer for audit continuity. Including tags, shared visibility settings, and linked activity references.

InTouch

Task

maps to

Freshsales

Task

1:1
Fully supported

InTouch tasks migrate as Freshsales Tasks with subject, due date, status, and priority. Completed status maps to Freshsales completed status flag. Open tasks retain their owner assignment; completed tasks archive with original completion timestamp. Including task description, reminders, and recurrence patterns.

InTouch

Attachment / File

maps to

Freshsales

File

1:1
Fully supported

InTouch file attachments re-upload to Freshsales Files linked to the parent record. File size limits enforced per Freshsales storage tiers (2GB/user on Growth, 5GB/user on Pro, 100GB/user on Enterprise). Inline images extracted and rehosted during upload. Including file metadata and version history.

InTouch

User / Owner

maps to

Freshsales

User

1:1
Fully supported

InTouch owner records matched to Freshsales users by email address. Active/Inactive status maps to Freshsales user state. InTouch team or group assignments surface as Freshsales territory management on Pro and above — flagged for admin configuration if territory model applies.

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 logo

InTouch gotchas

High

Custom fields are template-bound and require pre-migration schema review

Medium

Contact export runs asynchronously and can exceed one hour for large rolls

Medium

Legacy flash-era data may have inconsistent field encoding in exports

Low

Matter export is not a self-service feature on all tiers

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 lifecycle stage requires custom field creation in Freshsales

    InTouch tracks prospect progression through lifecycle stages that have no direct Freshsales native equivalent. Freshsales splits Lead and Contact into separate objects, and lifecycle stages exist as a configurable field on Contact. We create a lifecycle_stage custom field on Contact and map InTouch values 1:1. When InTouch contacts split to Freshsales Leads (unqualified prospects), the lifecycle stage does not follow automatically at lead creation — it requires post-conversion field mapping configured in Freshsales's conversion settings. We document this mapping requirement in the migration plan so your admin pre-configures it before go-live.

  • InTouch multi-pipeline stage values collide in Freshsales without pipeline scoping

    InTouch allows each pipeline to define its own stage values independently. Freshsales also supports multiple pipelines, but stage values are pipeline-scoped within each pipeline's configuration. If your InTouch setup uses the same stage name across multiple pipelines (e.g., 'Qualification' in Pipeline A and Pipeline B), we create separate Freshsales pipelines and configure each with its own stage set. Stage probability defaults are pipeline-specific in Freshsales — we preserve any custom probability overrides from InTouch as a Probability_Override__c custom field on Deal so forecast models remain accurate post-migration.

  • InTouch workflow rules do not transfer to Freshsales's automation builder

    InTouch workflows built with its automation engine — including email triggers, task creation rules, field update actions, and assignment logic — have no equivalent in Freshsales that receives them automatically. Freshsales provides its own workflow builder (Admin Settings > Workflows) with triggers, conditions, and actions. We export your InTouch workflow definitions as a structured reference document listing each rule's trigger, conditions, and actions. Your Freshsales admin uses this document to rebuild rules in Freshsales's workflow builder. This is a manual step that adds 1–3 days of admin effort depending on workflow complexity.

  • InTouch parent-company hierarchy needs Freshsales territory setup for large org structures

    InTouch company hierarchies with multiple levels of parent-child relationships map to Freshsales Account via parent_account_id. However, Freshsales's native hierarchy view is limited to two levels. For organizations with deeper account hierarchies (grandparent → parent → child), we recommend Freshsales territory management (available on Pro and above) as an organizational layer. Territories let you group accounts hierarchically beyond the two-level native parent-account constraint. We flag deep-hierarchy accounts during validation and surface the territory mapping recommendation in the migration plan.

  • InTouch file attachments re-uploaded to Freshsales storage with size-tier constraints

    InTouch stores file attachments associated with contacts, companies, and deals. Freshsales file storage is per-user based on plan tier: 2GB/user on Growth, 5GB/user on Pro, 100GB/user on Enterprise. Large InTouch instances with extensive file attachments may exceed Growth-tier storage immediately. We calculate total attachment volume during discovery and flag if your file total exceeds your target Freshsales plan's storage allocation. Files re-upload via Freshsales's native file storage API with original filenames and content preserved.

Migration approach

Six steps for a successful InTouch to Freshsales data migration

  1. Discover InTouch data model and schema

    We connect read-only API access to your InTouch instance and enumerate all standard objects (contacts, companies, deals, pipelines), custom fields, and activity records. We inventory pipeline structures, stage value sets, owner assignments, and attachment volumes. We also capture relationship types and record counts for each object. Discovery output is a data inventory document used to build the field-level mapping spec and flag schema divergence points before migration begins.

  2. Map InTouch fields to Freshsales schema with type-aware transformations

    Our mapping engine builds a field-level translation table covering every standard and custom field in InTouch. Pick-list value mappings are generated for all custom pick-list and multi-select fields. Owner resolution logic (email-to-user match) is configured. Custom fields that require Freshsales-side creation are listed with field type, pick-list values, and required module assignment. The mapping spec goes through your review before any data movement begins.

  3. Create Freshsales custom fields and configure pipelines

    Before data loads, we create all required Freshsales custom fields (Contact, Account, Deal modules) using Freshsales's API or admin import. Pipeline configurations matching InTouch's pipeline structure are set up with stage definitions and probability weights. Territory structures (if needed for deep account hierarchies) are configured on Pro and above. This step can run in parallel with your team's Freshsales onboarding.

  4. Run sample migration with field-level diff

    A representative slice of records — typically 100–500 covering contacts, accounts, deals, and activities — migrates to a Freshsales test environment. We generate a field-level diff report showing source values against destination field values for every mapped field. You review the diff, confirm lifecycle stage routing, pipeline mapping, and owner resolution before the full migration commits. Including data validation checks, duplicate detection, and mapping correction steps.

  5. Execute full migration with delta-pickup window

    The full dataset migrates using Freshsales's API with rate-limit-aware sequencing to avoid throttling. Accounts migrate first (foreign key dependency for contacts), then contacts and leads split by qualification, then deals with pipeline and stage mapping, then activities and tasks. A delta-pickup window of 24–48 hours captures any records created or modified in InTouch during the cutover. Audit log records every operation; one-click rollback reverts to pre-migration state if reconciliation fails.

Platform deep dives

Context on both ends of the pair

InTouch logo

InTouch

Source

Strengths

  • Purpose-built conveyancing workflow templates with Land Registry task automation built in.
  • Fully managed cloud infrastructure with six file replicas across two regions and real-time database replication.
  • Data export capability included at all pricing tiers, not gated behind Enterprise only.
  • Dedicated customer champion and structured onboarding for firms with limited in-house IT capacity.
  • 2FA security enforced for both users and clients accessing the system.

Weaknesses

  • Advanced customisation for dashboards, reports, and workflow branching is limited compared to general-purpose legal platforms.
  • Mobile app is widely reported as under-featured and difficult to use on-site.
  • Native integration ecosystem with third-party accounting, Land Registry, and practice management tools is narrow.
  • Transition from the legacy flash-based interface created workflow disruption for established users that some firms still reference negatively.
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?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • 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: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your InTouch 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 to Freshsales data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most InTouch-to-Freshsales migrations complete in 24–72 hours of clock time for under 10,000 records. Larger datasets with 50,000+ records or multiple InTouch pipelines extend to 3–7 days. The longest planning step is mapping InTouch pipelines to Freshsales pipeline configurations and setting up custom field type conversions. We provide a timeline estimate during discovery based on your record volumes and custom field complexity.

Adjacent paths

Related migrations to explore

Ready when you are

Move from InTouch.
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