Done-for-you migrations are open: our consultants run yours. See the migration service

Migrate into Zoho CRM: where data lands, setup, limits

What Shuttio writes into Zoho CRM, where each object lands, how to connect, and what the Zoho CRM API cannot do (create pipelines or stages, log an email, set a record's creation date or creator, switch off your own webhooks).

Last updated: 15 November 2026

Sources that can move into Zoho CRM: Spreadsheet / CSV, HubSpot, Pipedrive, Affinity, Zoho CRM, Freshsales, ActiveCampaign, OnePageCRM, Cloze, Less Annoying CRM, Pipeline CRM, Zendesk Sell, Close, Copper, folk, Insightly, Bitrix24, Capsule, HighLevel, SugarCRM, SuiteCRM, Salesflare, Breakcold, Vtiger, Twenty, Attio. A CSV import is free. A CRM migration is free under 20,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced by record count. The sample is free. See pricing. Zoho CRM to Zoho CRM is not offered.

Source by source: Zoho CRM support matrix.

Connect

  • Sign in to Zoho CRM as an administrator and allow read and change access to your modules and settings. Zoho asks which data centre your organisation is on; the connection is tied to that one. Creating custom fields needs an administrator, and records are written as the signed-in user unless an owner or author matches a Zoho user by email.
  • The sign-in is deleted 14 days after the migration finishes, and you can remove Shuttio in Zoho under Setup, Developer Space, Connected Apps at any time. A migration is pinned to the organisation it first wrote to: a connection to another organisation is refused.

What Shuttio writes

  • Companies as accounts with website, description and your custom fields. A company is matched on its exact name, then on its website domain; a match is linked to and never overwritten.
  • People as contacts linked to their account, with first and last name, two emails, two phone numbers, title and description. A third email or phone goes into a note on the contact. A person is matched on their exact email first.
  • Deals with amount, close date, account, contact, pipeline and stage; a won or lost deal goes to the pipeline's closing stage of that outcome. A Zoho deal holds one contact and one account, so a note on the deal says how many more the source named.
  • Notes, tasks, meetings as events and calls as completed calls. Zoho takes no original created time or author on them, so the first line of each says when it happened and who wrote it, and the author becomes the owner when a Zoho user has the same email. Emails are notes with sender, recipients, subject and text: the only email call Zoho has sends an email, and Shuttio never calls it.
  • Every other source field becomes a custom field of the right type (text, number, date, date and time, checkbox, picklist, multi-select, user), reused when you already have a field of that name. Tags are added to the record. Files are attached to the deal, contact or account they belong to when you tick Attachments.
  • Owners are matched to the Zoho user of the same email. No user is created or invited.

Where each thing lands

FromObjectLands in Zoho CRM as
HubSpotContactsContacts (linked to their account, matched by email)
HubSpotCompaniesAccounts (matched by name, then website domain)
HubSpotDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
PipedrivePersonsContacts (linked to their account, matched by email)
PipedriveOrganizationsAccounts (matched by name, then website domain)
PipedriveDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
AffinityPersonsContacts (linked to their account, matched by email)
AffinityOrganizationsAccounts (matched by name, then website domain)
AffinityOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
Zoho CRMAccountsAccounts (matched by name, then website domain)
Zoho CRMContactsContacts (linked to their account, matched by email)
Zoho CRMDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
FreshsalesAccountsAccounts (matched by name, then website domain)
FreshsalesContactsContacts (linked to their account, matched by email)
FreshsalesDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
ActiveCampaignAccountsAccounts (matched by name, then website domain)
ActiveCampaignContactsContacts (linked to their account, matched by email)
ActiveCampaignDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
OnePageCRMCompaniesAccounts (matched by name, then website domain)
OnePageCRMContactsContacts (linked to their account, matched by email)
OnePageCRMDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
ClozeCompaniesAccounts (matched by name, then website domain)
ClozeContactsContacts (linked to their account, matched by email)
ClozeDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
Less Annoying CRMCompaniesAccounts (matched by name, then website domain)
Less Annoying CRMContactsContacts (linked to their account, matched by email)
Less Annoying CRMDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
Pipeline CRMCompaniesAccounts (matched by name, then website domain)
Pipeline CRMPeopleContacts (linked to their account, matched by email)
Pipeline CRMDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
Zendesk SellCompaniesAccounts (matched by name, then website domain)
Zendesk SellPeopleContacts (linked to their account, matched by email)
Zendesk SellDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
CloseLeadsAccounts (matched by name, then website domain)
CloseContactsContacts (linked to their account, matched by email)
CloseOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
CopperCompaniesAccounts (matched by name, then website domain)
CopperPeopleContacts (linked to their account, matched by email)
CopperOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
folkCompaniesAccounts (matched by name, then website domain)
folkPeopleContacts (linked to their account, matched by email)
folkDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
InsightlyOrganisationsAccounts (matched by name, then website domain)
InsightlyContactsContacts (linked to their account, matched by email)
InsightlyOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
Bitrix24CompaniesAccounts (matched by name, then website domain)
Bitrix24ContactsContacts (linked to their account, matched by email)
Bitrix24DealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
CapsuleOrganisationsAccounts (matched by name, then website domain)
CapsulePeopleContacts (linked to their account, matched by email)
CapsuleOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
HighLevelBusinessesAccounts (matched by name, then website domain)
HighLevelContactsContacts (linked to their account, matched by email)
HighLevelOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
SugarCRMAccountsAccounts (matched by name, then website domain)
SugarCRMContactsContacts (linked to their account, matched by email)
SugarCRMOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
SuiteCRMAccountsAccounts (matched by name, then website domain)
SuiteCRMContactsContacts (linked to their account, matched by email)
SuiteCRMOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
SalesflareAccountsAccounts (matched by name, then website domain)
SalesflareContactsContacts (linked to their account, matched by email)
SalesflareOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
BreakcoldCompaniesAccounts (matched by name, then website domain)
BreakcoldPeopleContacts (linked to their account, matched by email)
BreakcoldDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
VtigerOrganizationsAccounts (matched by name, then website domain)
VtigerContactsContacts (linked to their account, matched by email)
VtigerOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
TwentyCompaniesAccounts (matched by name, then website domain)
TwentyPeopleContacts (linked to their account, matched by email)
TwentyOpportunitiesDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)
AttioCompaniesAccounts (matched by name, then website domain)
AttioPeopleContacts (linked to their account, matched by email)
AttioDealsDeals (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the closing stages)

What the Zoho CRM API cannot do

  • This version does not create pipelines or stages: they are matched by name, and a deal whose pipeline or stage you do not have goes to your default pipeline and its first stage with the source ones written into the description.
  • It cannot log a historic email, so emails are notes.
  • A record's creation date and creator cannot be set through the documented API: records show the date of the move, and the original date is in the text of notes, tasks, events and calls.
  • A source link field has no Zoho field to go to and is named on the review page. Read-only fields are skipped.
  • Every record is written with Zoho's workflow rules, approvals and blueprints switched off, and tasks, events and calls are written without a reminder or a participant. Zoho may still email a record's new owner under your notification settings, and your own webhooks and integrations (Zapier and similar) may run: pause them before the run and try a sample first.
  • Products, quotes, orders, cases, campaigns, custom modules and lists are not carried in this version.

Zoho's API credits

Zoho CRM gives each organisation a number of API credits a day (5,000 on Free; from 50,000 on paid editions up to 100,000 on Standard, more on higher editions) and limits concurrent calls to between 5 and 25. A record is one credit or more, so a large move on a small edition takes days: the run pauses when the day's credits are nearly used and carries on when you resume it.

Known limits

  • A rollback deletes what the migration created: notes, tasks, events, calls and files, then deals, contacts and accounts, then the custom fields it added. Records that already existed are not touched. Deleted records wait in Zoho's Recycle Bin, where an administrator can restore them for a limited time. Tags the migration used stay in your tag list.
  • A create that fails without an answer (a dropped connection, a 5xx) is never sent again: the row is reported as maybe written, and a Retry looks the contact up by its email first.

Not answered here? Email help@shuttio.com.