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

Migrate into Insightly: where data lands, setup, limits

What Shuttio writes into Insightly, where each object lands, how to connect, and what the Insightly API cannot do (create fields, pipelines or stages, create an email or a call, set a record's creation date, switch off your own workflow automations).

Last updated: 15 November 2026

Sources that can move into Insightly: 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. Insightly to Insightly is not offered.

Object by object: What objects are supported for Insightly migrations.

Source by source: Insightly support matrix.

Connect

  • Paste your API key and choose your pod, both from User Settings, API in Insightly (the pod is the part of the API URL between "api." and ".insightly.com", for example na1). Shuttio checks the key with a live call before it stores anything. Use the key of a user who may add and delete records, notes, tasks and events; the key writes with that user's rights.
  • The key is stored encrypted and deleted 14 days after the migration finishes; there is nothing to revoke. A migration is pinned to the Insightly instance it first wrote to: a key for another instance is refused.

What Shuttio writes

  • Companies as organisations, with website, phone, description, tags and the fields you already have. A company is matched on its exact name; a match is linked to and never overwritten.
  • People as contacts linked to their organisation, with one email address, up to four phone numbers, job title, description and tags. More organisations are added as links; a second email address or a fifth phone number goes into a note on the contact. A person is matched on their exact email first.
  • Deals as opportunities with bid amount, currency, forecast and close date, owner, organisation, contacts, pipeline, stage and state (won or lost is the opportunity's state in Insightly).
  • Notes and tasks with their original date where Insightly has a field for it: a task keeps its due date and done state, a meeting is an event with its start and end and no attendee, and a note's first line says when it was written and by whom. Insightly has no call object and its API cannot create an email, so calls and emails are notes.
  • Owners and authors are matched to the Insightly user of the same email: an owner becomes the record's owner. No user is ever created or invited.
  • Files, when you tick Attachments, are attached to the opportunity, contact or organisation they belong to.
  • Every other source field is written into the Insightly custom field of the same name when you already have one. Insightly's API cannot create custom fields: a field with no match is named on the review page, and its value goes into a note on each record. Create the fields in Insightly first to keep them as fields.

Where each thing lands

FromObjectLands in Insightly as
HubSpotContactsContacts (linked to their organisation, matched by email)
HubSpotCompaniesOrganisations (matched by name)
HubSpotDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
PipedrivePersonsContacts (linked to their organisation, matched by email)
PipedriveOrganizationsOrganisations (matched by name)
PipedriveDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
AffinityPersonsContacts (linked to their organisation, matched by email)
AffinityOrganizationsOrganisations (matched by name)
AffinityOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
Zoho CRMAccountsOrganisations (matched by name)
Zoho CRMContactsContacts (linked to their organisation, matched by email)
Zoho CRMDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
FreshsalesAccountsOrganisations (matched by name)
FreshsalesContactsContacts (linked to their organisation, matched by email)
FreshsalesDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
ActiveCampaignAccountsOrganisations (matched by name)
ActiveCampaignContactsContacts (linked to their organisation, matched by email)
ActiveCampaignDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
OnePageCRMCompaniesOrganisations (matched by name)
OnePageCRMContactsContacts (linked to their organisation, matched by email)
OnePageCRMDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
ClozeCompaniesOrganisations (matched by name)
ClozeContactsContacts (linked to their organisation, matched by email)
ClozeDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
Less Annoying CRMCompaniesOrganisations (matched by name)
Less Annoying CRMContactsContacts (linked to their organisation, matched by email)
Less Annoying CRMDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
Pipeline CRMCompaniesOrganisations (matched by name)
Pipeline CRMPeopleContacts (linked to their organisation, matched by email)
Pipeline CRMDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
Zendesk SellCompaniesOrganisations (matched by name)
Zendesk SellPeopleContacts (linked to their organisation, matched by email)
Zendesk SellDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
CloseLeadsOrganisations (matched by name)
CloseContactsContacts (linked to their organisation, matched by email)
CloseOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
CopperCompaniesOrganisations (matched by name)
CopperPeopleContacts (linked to their organisation, matched by email)
CopperOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
folkCompaniesOrganisations (matched by name)
folkPeopleContacts (linked to their organisation, matched by email)
folkDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
InsightlyOrganisationsOrganisations (matched by name)
InsightlyContactsContacts (linked to their organisation, matched by email)
InsightlyOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
Bitrix24CompaniesOrganisations (matched by name)
Bitrix24ContactsContacts (linked to their organisation, matched by email)
Bitrix24DealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
CapsuleOrganisationsOrganisations (matched by name)
CapsulePeopleContacts (linked to their organisation, matched by email)
CapsuleOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
HighLevelBusinessesOrganisations (matched by name)
HighLevelContactsContacts (linked to their organisation, matched by email)
HighLevelOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
SugarCRMAccountsOrganisations (matched by name)
SugarCRMContactsContacts (linked to their organisation, matched by email)
SugarCRMOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
SuiteCRMAccountsOrganisations (matched by name)
SuiteCRMContactsContacts (linked to their organisation, matched by email)
SuiteCRMOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
SalesflareAccountsOrganisations (matched by name)
SalesflareContactsContacts (linked to their organisation, matched by email)
SalesflareOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
BreakcoldCompaniesOrganisations (matched by name)
BreakcoldPeopleContacts (linked to their organisation, matched by email)
BreakcoldDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
VtigerOrganizationsOrganisations (matched by name)
VtigerContactsContacts (linked to their organisation, matched by email)
VtigerOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
TwentyCompaniesOrganisations (matched by name)
TwentyPeopleContacts (linked to their organisation, matched by email)
TwentyOpportunitiesOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)
AttioCompaniesOrganisations (matched by name)
AttioPeopleContacts (linked to their organisation, matched by email)
AttioDealsOpportunities (pipelines and stages matched by name; a missing one is named and the deal goes to the first; won and lost are the opportunity state)

What the Insightly API cannot do

  • It cannot create custom fields, pipelines or pipeline stages: pipelines and stages are matched by name, and a deal whose pipeline or stage you do not have goes to your first pipeline and stage with the source ones written into a note.
  • It cannot create an email or a call, so emails and calls are notes.
  • It does not let a record's creation date or creator be set: records show the date of the move. A note and an event carry their original date where Insightly accepts it.
  • It does not say whether your own workflow automations and integrations (Zapier and similar) run on records created through the API, or how to switch them off. A task owned by a colleague may email that colleague under their notification settings. Pause automations before the run if they message people, and try a sample first.
  • Leads, projects, products, custom objects and lists are not carried in this version.

Insightly's request limit

Insightly allows 10 API requests a second and a daily total by plan (1,000 on Free up to 100,000 on Enterprise). Shuttio stays under the per-second limit and pauses the run when the day's requests are used: resume it the next day and it carries on from where it stopped. Matching a record takes one request and writing it a few more, so a large move on a small plan takes several days.

Known limits

  • A rollback deletes what the migration created: notes, tasks, events and files, then opportunities, contacts and organisations. Records that already existed are not touched, and nothing in your fields, pipelines or stages was changed, so nothing there is removed. 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.