Migrate from InTouch CRM to Zoho CRM

InTouch Contact records map to Zoho CRM Lead. We extract the contact's full name, email address, phone, company affiliation, and any custom fields from the InTouch CSV export and map them to the corresponding Zoho Lead field names. If InTouch stores a separate Company record linked to the Contact, we create a corresponding Zoho Account first and attach the Lead to it via the Account Name lookup. Email addresses serve as the dedupe key; duplicates are flagged for the customer's admin to resolve before import.

InTouch Company records map to Zoho CRM Account. The company name becomes the Account Name, domain data maps to the Website field, and address fields map to the Zoho address compound field. We create Accounts before any Lead import so that the Account-Name lookup is satisfied at the moment of Lead insert. If InTouch stores account-level custom fields, we create matching Zoho custom fields on the Account module before migration.

InTouch Deal records map to Zoho Potentials by default. The deal name, amount, closing date, and pipeline stage migrate to Potential Name, Amount, Closing Date, and Stage respectively. If InTouch Deals have a pipeline structure that does not map cleanly to Zoho's standard Potentials module (for example, if Deals carry custom fields or sub-entities unique to InTouch), we create a Zoho Custom Module named Deals and map the InTouch Deal fields to it. The customer chooses the module strategy during scoping based on their reporting needs.

InTouch pipeline stages are stored as free-text labels in the CSV export. We extract the distinct stage values, create corresponding Zoho Stage entries in the Potentials module (or the custom Deals module if that path is chosen), and build a stage-mapping table during scoping. Stages are imported as Zoho picklist values; the customer configures stage probability and stage order within Zoho after migration. We preserve any closed-lost or closed-won metadata as custom fields in Zoho.

InTouch activity records map to Zoho CRM Tasks (for tasks and calls) and Events (for meetings). We resolve the parent record reference (Contact or Deal) at migration time using email-based matching to the migrated Lead or Potential. Activity timestamps migrate as Activity Date on Task and Start Time / End Time on Event. Call duration and disposition data migrate to Zoho Call custom fields if the customer's Zoho edition supports them.

InTouch custom fields stored within Pipelines (Contacts, Companies, Deals, Activities) migrate to Zoho CRM custom fields of the closest matching type. We pre-create all destination custom fields in Zoho before any data import begins, using the Zoho API for field creation. Multi-select picklist values, date fields, and numeric fields are type-mapped to avoid Zoho validation rule rejections. Drop-down constraint fields from InTouch must have corresponding picklist values pre-created in Zoho.

InTouch Owner records map to Zoho CRM Users by email address. We extract every distinct Owner referenced across Contact, Company, and Deal records and match against the Zoho destination org's User table. Any Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive users in Zoho are mapped to inactive Owner records if the historical assignment must be preserved.

InTouch notes migrate to Zoho CRM Notes attached to the corresponding Lead, Account, or Potential record via ContentDocumentLink. If InTouch exports attachments as file paths or URLs rather than binary blobs, we flag this during scoping because Zoho's CSV import does not handle file attachment references natively; a file migration step using Zoho's attachment API or a document migration tool is required for attachment preservation.

InTouch Pipelines (the structural containers for Deals) do not have a direct Zoho equivalent at the module level. We map each InTouch Pipeline to a Zoho Record Type on Potentials or the custom Deals module, with a corresponding Sales Process that restricts the visible stage values per Pipeline. The customer configures stage order and probability percentages in Zoho after migration; we deliver a written stage-mapping document as part of the handoff.

If InTouch stores email engagement metadata (send timestamps, subject, body) within activity records, we map this to Zoho CRM Tasks with an email-specific type flag and preserve the original timestamp in a custom date field. Zoho's native Email module (Full Email Sync) is available from Standard tier and captures actual synced emails; InTouch's logged email metadata is a structural substitute rather than a live email sync. We document this distinction in scoping.