CRM migration
Field-level mapping, validation, and rollback between InTouch and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
InTouch
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between InTouch and Freshsales.
Complexity
BStandard
Timeline
24–72 hours
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Freshsales
Contact
1:1InTouch 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)
Freshsales
Lead
1:manyInTouch 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
Freshsales
Account
1:1InTouch 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
Freshsales
Deal
1:1InTouch 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
Freshsales
Pipeline
1:1Each 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
Freshsales
Custom Field
1:1InTouch 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
Freshsales
Sales Activity (Call)
1:1InTouch 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
Freshsales
Sales Activity (Email)
1:1InTouch 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
Freshsales
Note
1:1InTouch 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
Freshsales
Task
1:1InTouch 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
Freshsales
File
1:1InTouch 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
Freshsales
User
1:1InTouch 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.
| InTouch | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Contact (unqualified) | Lead1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported | |
| Call Log | Sales Activity (Call)1:1 | Fully supported | |
| Email Log | Sales Activity (Email)1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Custom fields are template-bound and require pre-migration schema review
Contact export runs asynchronously and can exceed one hour for large rolls
Legacy flash-era data may have inconsistent field encoding in exports
Matter export is not a self-service feature on all tiers
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
InTouch
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across InTouch and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
InTouch: Not publicly documented.
Data volume sensitivity
InTouch doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during InTouch to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your InTouch to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave InTouch
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.