How long does an InTouch to Zoho CRM migration take?

Most InTouch-to-Zoho migrations complete in 48–72 hours of clock time for under 50,000 records. The longest phase is pre-migration: schema setup, custom field declaration, and the Zoho Lead Conversion configuration typically take 2–3 business days of admin coordination. Larger setups with 500,000+ records, many custom fields, or heavy activity history extend to 5–7 days. Zoho's bulk API rate-limit tiers (Standard: 500 req/min, Professional: 2,500 req/min) affect throughput — FlitStack sequences batches to stay within limits and flags if a temporary Zoho tier upgrade would shorten the window.

Will my InTouch workflows and automation rules migrate to Zoho CRM?

No. InTouch workflows, sequence rules, and task-assignment logic do not have a Zoho equivalent that can be imported — they require manual rebuild in Zoho's automation tools (Blueprint, Workflow Rules, Assignment Rules). FlitStack does not migrate automation data. We export your InTouch workflow definitions as a structured JSON reference document that your Zoho admin can use as a rebuild blueprint for Zoho Blueprint stages and workflow rules. Budget 1–2 hours of Zoho admin time per complex workflow you need to recreate.

What happens to my InTouch custom fields when they migrate to Zoho CRM?

InTouch custom fields — data markers tied to matter or case templates — get declared as Zoho custom fields on the appropriate module (Contact, Account, or Deal) before the migration runs. FlitStack reviews each InTouch custom field's actual data values to infer the correct Zoho data_type (text, number, date, pick-list, etc.), creates the Zoho fields via the Zoho API, and then maps the values into the import CSV. Fields with mixed data types in InTouch are flagged for your admin to decide whether to split them into separate Zoho fields or store as text for reference.

How does InTouch deal stage data map into Zoho CRM's pipeline stages?

InTouch deal stages are free-form pick-list values with no built-in pipeline concept. FlitStack maps each InTouch stage name to the closest Zoho stage pick-list value value-by-value. If a Zoho stage with the exact name does not exist, FlitStack either creates it (if your Zoho plan allows custom stage values) or writes the original InTouch stage name to a custom field (Deal_Stage_Source__c) on the Deal record so your team retains the original label. Probability and forecast-category mapping is re-applied based on Zoho's stage-configuration settings after migration.

Can I migrate InTouch contacts to Zoho Leads and Contacts simultaneously?

InTouch has a single Contact object for all people records, but Zoho separates Leads and Contacts. FlitStack routes InTouch contacts to Zoho Leads if the record has no closed-won deal association at migration time (prospect), and to Zoho Contacts if it has a won deal or is linked to a primary company (established relationship). This split is deterministic and applied across the full dataset. Your Zoho admin should pre-configure the Lead Conversion mapping (Setup > Leads > Lead Conversion) so that converting a Lead in Zoho pre-fills the correct Account and Contact fields according to your business rules.

Does the migration affect my InTouch account during the cutover?

No. FlitStack uses scoped read access on InTouch — your team keeps full read and write access to InTouch throughout the migration. No data is modified or locked in InTouch. A delta-pickup window of 24–48 hours runs after the bulk load to capture records created or modified in InTouch during the cutover. FlitStack's audit log records every import operation, and one-click rollback is available if the Zoho reconciliation reveals data integrity issues that cannot be resolved by re-import.

How does FlitStack handle InTouch attachments and files?

InTouch file attachments are downloaded from InTouch, re-uploaded to Zoho's file storage (25 GB total cap per account), and linked to the corresponding Zoho record (Contact, Account, or Deal) by name and parent record ID. Files exceeding Zoho's 2 GB per-file limit are flagged as manual-reupload candidates in the migration report. If the total attachment volume exceeds the 25 GB Zoho cap, FlitStack surfaces the overage before the migration runs so your team can upgrade Zoho storage or archive files externally. Inline images embedded in InTouch notes are extracted and attached as separate Zoho attachment records.

InTouch to Zoho CRM Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

InTouch CRM stores your core CRM data — contacts, companies, deals, and custom fields tied to matter or case records — in a relatively flat object model suited to small sales and service teams. Zoho CRM distributes equivalent data across multiple modules: Leads and Contacts for people records, Accounts for organizations, Deals for pipeline opportunities, and a separate Custom Modules section for non-standard objects. The migration carries InTouch contacts to Zoho Leads (for new prospects) or Contacts (for established relationships), InTouch companies to Zoho Accounts, and InTouch deals to Zoho Deals with stage values translated to Zoho's pick-list model. Custom fields that InTouch ties to its matter or case templates map to Zoho custom fields created per module before data lands. Zoho's migration ID system — required for cross-module relationship integrity — gets applied during the FlitStack transformation pass so Account-Contact and Deal-Contact lookups resolve correctly. Workflows, automation rules, and email sequences do not migrate; FlitStack exports InTouch workflow definitions as a rebuild reference for your Zoho admin. The migration uses Zoho's bulk API (up to 200,000 records per export job) with scoped read access on InTouch so your team keeps working throughout the cutover window.

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

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

Zoho CRM

What's pulling them in

Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.
Small-business reviewers highlight real-time team visibility, daily time savings of 60–90 minutes, and the ability to mold the CRM to any industry vertical.

Object mapping

How InTouch objects map to Zoho CRM

Each row shows how a InTouch object lands in Zoho CRM, 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

Zoho CRM

Lead / Contact

1:many

Fully supported

InTouch Contact is a single object for all people records. FlitStack routes records to Zoho Lead if the InTouch record has no closed deal association (new prospect), and to Zoho Contact if it has a won deal or active deal association (established relationship). The split is determined by InTouch's deal-link metadata at migration time.

InTouch

Company

maps to

Zoho CRM

Account

1:1

Fully supported

InTouch company records map 1:1 to Zoho Accounts. The company name becomes Account Name; domain becomes Website. If the InTouch contact record lacks a linked company, FlitStack creates a placeholder 'Unassigned Account' entry so the Contact can be imported; your admin can later merge or reassign the contact to the correct Account using Zoho's AccountId lookup.

InTouch

Deal

maps to

Zoho CRM

Deal

1:1

Fully supported

InTouch deals migrate to Zoho Deals with the deal name, amount, close date, and stage preserved. Zoho Deal stages are pick-list values — InTouch stage names get mapped value-by-value to matching Zoho stage names, with unmatched values written as a custom pick-list field (Deal_Stage_Source__c) on the Deal record for reference.

InTouch

Activity (Task / Event / Call)

maps to

Zoho CRM

Tasks / Events / Calls

1:1

Fully supported

InTouch tasks map to Zoho Tasks with Subject, Status, Priority, and Due Date preserved. InTouch events and meetings map to Zoho Events with start/end times, location, and description. InTouch calls map to Zoho Calls with call type, duration, and outcome preserved. Original owner and timestamp on each activity are retained.

InTouch

Note / Attachment

maps to

Zoho CRM

Notes / Attachments

1:1

Fully supported

InTouch notes migrate to Zoho Notes with body text, last-modified date, and owner preserved. InTouch file attachments are re-uploaded to Zoho's file storage (25 GB cap per account). Inline images embedded in InTouch notes are extracted and attached as separate Zoho Attachment records linked to the parent Contact or Deal.

InTouch

Custom Fields (Matter / Case)

maps to

Zoho CRM

Custom Fields (per module)

1:1

Fully supported

InTouch custom fields tied to matter or case templates get declared as Zoho custom fields on the appropriate module (Contact, Account, or Deal) before the migration run. Each InTouch custom field's data_type is reviewed — text becomes Zoho single-line or multi-line text, numeric values become Zoho number fields, and date values become Zoho date fields. Pick-list or multi-select InTouch fields require Zoho pick-list creation with matching values.

InTouch

User / Owner

maps to

Zoho CRM

User

1:1

Fully supported

InTouch owner records are resolved by email match against Zoho users. Unmatched owners are flagged before the migration run — your team either pre-creates Zoho users for those email addresses or assigns those records to a designated fallback Zoho user. No record lands without an OwnerId in Zoho.

InTouch

Contact → Company Link

maps to

Zoho CRM

Contact → AccountId Lookup

1:1

Fully supported

InTouch contact-to-company association is a direct relationship field on the Contact record. This maps to Zoho's AccountId lookup on the Contact record. For contacts linked to multiple InTouch companies, the primary (most-recently-modified) company becomes the Zoho AccountId; secondary links are stored in Zoho's Account Contact Relations section.

InTouch

Deal → Contact Link

maps to

Zoho CRM

Deal → Contact (Multi-linked)

1:1

Fully supported

InTouch deal-to-contact links migrate as Zoho DealContactRel junction records, which is Zoho's built-in multi-contact linking for Deals. If InTouch stores a primary contact flag per deal, that contact gets priority in Zoho's deal view. Other linked contacts attach via standard DealContactRel records.

InTouch

Workflow / Automation Rules

maps to

Zoho CRM

Blueprint / Workflow Rules

1:1

Fully supported

InTouch workflows, sequences, and task-assignment rules do not have a Zoho equivalent that can be imported. FlitStack exports InTouch workflow definitions as a structured JSON reference document so your Zoho admin can rebuild equivalent Blueprint stages, workflow rules, and assignment macros in Zoho's automation tools.

InTouch	Zoho CRM	Compatibility
Contact	Lead / Contact1:many	Fully supported
Company	Account1:1	Fully supported
Deal	Deal1:1	Fully supported
Activity (Task / Event / Call)	Tasks / Events / Calls1:1	Fully supported
Note / Attachment	Notes / Attachments1:1	Fully supported
Custom Fields (Matter / Case)	Custom Fields (per module)1:1	Fully supported
User / Owner	User1:1	Fully supported
Contact → Company Link	Contact → AccountId Lookup1:1	Fully supported
Deal → Contact Link	Deal → Contact (Multi-linked)1:1	Fully supported
Workflow / Automation Rules	Blueprint / Workflow Rules1:1	Fully supported

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

Zoho CRM gotchas

High

API access requires Professional tier or above

High

Subform fields do not export cleanly via CSV

Medium

API credit consumption is non-linear

Medium

Export download links expire in 7 days

Medium

Owner (User) assignments require pre-mapped user IDs

InTouch gotchas		Zoho CRM gotchas
Severity	Issue	Severity	Issue
High	Custom fields are template-bound and require pre-migration schema review	High	API access requires Professional tier or above
Medium	Contact export runs asynchronously and can exceed one hour for large rolls	High	Subform fields do not export cleanly via CSV
Medium	Legacy flash-era data may have inconsistent field encoding in exports	Medium	API credit consumption is non-linear
Low	Matter export is not a self-service feature on all tiers	Medium	Export download links expire in 7 days
		Medium	Owner (User) assignments require pre-mapped user IDs

Pair-specific challenges

Zoho's Lead/Contact split requires routing logic that InTouch does not have

InTouch has a single Contact record for all people — a prospect and a customer live in the same object. Zoho separates Leads (unqualified, pre-conversion) from Contacts (post-conversion, tied to an Account). FlitStack routes InTouch contacts to Zoho Leads if they have no won-deal association at migration time, and to Zoho Contacts if they have a closed-won deal or are linked to a primary company. This logic is deterministic, but it means your Zoho instance will initially have more Leads than Contacts if InTouch was used primarily for early-stage pipeline tracking. Your Zoho admin should pre-configure the Lead Conversion mapping (Setup > Leads > Lead Conversion) before data lands.
Zoho's Data Migration wizard enforces a Migration ID requirement that InTouch does not provide natively

Zoho's import process requires a Migration_ID field per module to establish foreign-key relationships — Contact records need the Account's Migration_ID to link to the correct Account, and Deal records need both Contact and Account Migration_IDs. InTouch CSV exports do not include a migration-ID field. FlitStack generates migration IDs (alphanumeric strings) during the transformation pass and injects them into the import CSV files so Zoho's wizard can resolve the lookups correctly. If you run Zoho's native import without FlitStack's pre-processing, the Contact-to-Account links will break and contacts will land without parent Account records.
Custom field data types must be declared in Zoho before import — InTouch is type-agnostic

InTouch custom fields store values without enforcing a strict data type at the field level. Zoho requires a specific data_type (text, number, date, pick-list, multi-select, checkbox, etc.) when a custom field is created, and this cannot be changed after records are imported. FlitStack reviews each InTouch custom field during the assessment phase, infers the appropriate Zoho data_type from the actual values present in the data, and creates the Zoho custom fields via the Zoho CRM API (POST /settings/fields) before the import CSV is generated. Fields with mixed data (e.g., some values are numeric, others are text) are flagged for your admin to decide whether to split into separate Zoho fields or store as text.
Zoho's 25 GB total attachment cap may be lower than InTouch's effective storage for large files

InTouch stores file attachments inline on records without a clearly documented per-file or total storage cap published in its standard tiers. Zoho enforces a 2 GB per-file limit and a 25 GB total attachment cap per account on most Standard and Professional plans. FlitStack inventories all InTouch attachments before migration: any single file exceeding 2 GB is flagged as a manual-reupload candidate, and total attachment volume is compared against the 25 GB Zoho cap. If the migration would exceed the cap, FlitStack flags the overage so your team can either upgrade Zoho storage or archive large files externally before the migration run.
Zoho API rate limits apply during migration and differ by Zoho edition

Zoho CRM throttles API calls per edition: Standard tier allows 500 requests per minute, Professional allows 2,500 per minute, Enterprise allows 10,000 per minute. FlitStack uses Zoho's bulk API endpoints (bulk write with batched records) to maximize throughput within the rate limit, but record counts above 200,000 may require multi-page bulk read cycles. If your Zoho instance is on Standard tier, the migration clock time extends because each batch of 200 records counts against the API credit system. FlitStack surfaces the rate-limit impact in the pre-migration assessment so you can decide whether to temporarily upgrade to Professional for the migration window.

Migration approach

Six steps for a successful InTouch to Zoho CRM data migration

Audit InTouch data and create Zoho schema

FlitStack exports a full CSV snapshot of all InTouch modules — Contacts, Companies, Deals, Activities, Notes, Attachments, and custom field data — via InTouch's export API. We then review the inventory: count records per module, enumerate all custom field names and inferred data types, and identify owner email addresses. Before any data lands in Zoho, we create the corresponding custom fields via the Zoho CRM API (POST /settings/fields) and configure the Zoho Lead Conversion mapping so your admin can pre-approve how Leads convert to Accounts and Contacts. This schema-setup step typically takes 2–3 business days.
Generate migration IDs and build import CSV files

FlitStack assigns a unique Migration_ID (alphanumeric string) to every InTouch Account, Contact, and Deal record. These IDs are embedded in the import CSV as a dedicated column so Zoho's Data Migration wizard can resolve foreign-key relationships during import — Contact records carry their parent Account's Migration_ID, and Deal records carry both Contact and Account Migration_IDs. Owner email addresses are matched against Zoho user records; any unmatched owners generate a pre-flight error list so your team can invite them to Zoho or designate a fallback owner before the migration runs.
Run sample migration with field-level diff

A representative slice of 100–500 records migrates first — typically spanning Accounts, Contacts, Deals, and Activities from different owners and deal stages. FlitStack generates a field-level diff comparing source InTouch values against the resulting Zoho records so you can verify that stage mappings, custom field values, and owner resolution are correct before the full run commits. You sign off on the diff output; no full migration proceeds without your approval.
Execute full migration with delta-pickup window

The full dataset loads into Zoho via Zoho's bulk write API, sequenced: Accounts first, then Leads and Contacts (which reference Account Migration_IDs), then Deals (which reference both Contact and Account Migration_IDs), then Activities, Notes, and Attachments. A delta-pickup window — typically 24–48 hours — runs after the bulk load completes to capture any InTouch records created or modified during the cutover. FlitStack's audit log records every operation; one-click rollback reverts Zoho to its pre-migration state if reconciliation reveals data integrity issues.
Deliver workflow reference export and reconciliation report

FlitStack exports InTouch workflow definitions and automation rules as a structured JSON reference document — not the rules themselves, but a machine-readable map of triggers, conditions, and actions that your Zoho admin can use to rebuild equivalent Blueprint stages, workflow rules, and assignment macros in Zoho. The reconciliation report shows record counts per module in InTouch versus Zoho post-migration, identifies any records that skipped due to validation errors, and flags attachment overages against Zoho's 25 GB cap.

Platform deep dives

Context on both ends of the pair

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.

Zoho CRM

Destination

Strengths

Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases.
Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices.
Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement.
Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role.
Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.

Weaknesses

Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support.
Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent.
Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings.
User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields.
No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

	InTouch Source	Zoho CRM Destination
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.	Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases. Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices. Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement. Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role. Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.
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.	Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support. Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent. Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings. User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields. No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from InTouch to Zoho CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

InTouch

Zoho CRM

How InTouch objects map to Zoho CRM

What specifically takes care here

Six steps for a successful InTouch to Zoho CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your InTouch to Zoho CRM migration cost

What are you migrating?

Frequently asked questions about InTouch to Zoho CRM data migrations

Can't find your answer?

Related migrations to explore

Move from InTouch.
Land in Zoho CRM, intact.

Migrate from InTouch to Zoho CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

InTouch

Zoho CRM

How InTouch objects map to Zoho CRM

What specifically takes care here

Six steps for a successful InTouch to Zoho CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your InTouch to Zoho CRM migration cost

Frequently asked questions about InTouch to Zoho CRM data migrations

Can't find your answer?

How long does an InTouch to Zoho CRM migration take?

Will my InTouch workflows and automation rules migrate to Zoho CRM?

What happens to my InTouch custom fields when they migrate to Zoho CRM?

How does InTouch deal stage data map into Zoho CRM's pipeline stages?

Can I migrate InTouch contacts to Zoho Leads and Contacts simultaneously?

Does the migration affect my InTouch account during the cutover?

How does FlitStack handle InTouch attachments and files?

Related migrations to explore

Move from InTouch. Land in Zoho CRM, intact.

Move from InTouch.
Land in Zoho CRM, intact.