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

Migrate into Close: where data lands, setup, limits

What Shuttio writes into Close, where each object lands, how to connect, and what the Close API cannot do (create a meeting, set a lead's creation date or creator, undo a delete, switch off your own webhooks).

Last updated: 15 November 2026

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

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

Source by source: Close support matrix.

Connect

  • Press Connect with Close and sign in as an admin of the organization: creating custom fields, pipelines and statuses needs one. Close grants an app one access level, read and write. The user who signs in is the author of anything whose original author has no Close user of the same email.
  • Or open Use an API key instead and paste a key from Close (Settings, Developer, API Keys). Shuttio checks it with a live call before it stores anything.
  • The sign-in or the key is stored encrypted and deleted 14 days after the migration finishes; a sign-in is also revoked at Close then. A migration is pinned to the Close organization it first wrote to: another organization is refused.

What Shuttio writes

  • Companies as leads, with website, description and custom fields. A lead is matched on its exact name first; a match is linked to and never overwritten.
  • People as contacts on their company's lead, with every email and phone number and job title. A person with no company gets a lead of their own, named after them, because a Close contact always lives on a lead. A contact is matched on its exact email first.
  • Deals as opportunities on their company's lead (or their person's), with value (in cents, in your Close currency), close date, owner, pipeline and status. Pipelines and statuses are matched by name and the missing ones are created, as won or lost statuses where the source says so.
  • Notes, calls, emails, text messages and tasks with their original date. A call is logged with its direction and length, and its recording link when the source has an https one (otherwise the link is in the call note); nothing is dialled. An email or a text message is logged as already sent or already received; nothing is sent to anyone (if Close refuses to log a text message, it is written as a note). A task is created without notifying its assignee. Authors and assignees are matched to the Close user of the same email.
  • Files, when the Attachments option is on: each is uploaded to Close and attached to a note on the lead (and contact) of the record it followed; a file Close refuses is listed and the run goes on.
  • Every other source field as a custom field on the lead, contact or opportunity: reused when you already have one of that name, created otherwise. A user or owner field becomes a user field filled by email. Close has no tags, so tags go to a custom field.
  • Your source's own objects (a HubSpot or Salesforce custom object, an Attio custom object, a monday board) as Close custom objects: a type of the same name is reused or created, its fields are created with the same types as a lead's custom fields, and every record becomes an instance. Close puts every instance on a lead: the lead of the company the record is linked to, else its person's lead, else its deal's. A record linked to none of them that moved to Close is listed as a failed row and a Retry writes it once one has. Close has no field that links a custom object to a lead, contact or another custom object, so each link is also written as a text field holding the name of the linked record.

Where each thing lands

FromObjectLands in Close as
HubSpotContactsContacts (on their company's lead; a person with no company gets a lead of their own)
HubSpotCompaniesLeads (matched by name)
HubSpotDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
PipedrivePersonsContacts (on their company's lead; a person with no company gets a lead of their own)
PipedriveOrganizationsLeads (matched by name)
PipedriveDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
AffinityPersonsContacts (on their company's lead; a person with no company gets a lead of their own)
AffinityOrganizationsLeads (matched by name)
AffinityOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
Zoho CRMAccountsLeads (matched by name)
Zoho CRMContactsContacts (on their company's lead; a person with no company gets a lead of their own)
Zoho CRMDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
FreshsalesAccountsLeads (matched by name)
FreshsalesContactsContacts (on their company's lead; a person with no company gets a lead of their own)
FreshsalesDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
ActiveCampaignAccountsLeads (matched by name)
ActiveCampaignContactsContacts (on their company's lead; a person with no company gets a lead of their own)
ActiveCampaignDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
OnePageCRMCompaniesLeads (matched by name)
OnePageCRMContactsContacts (on their company's lead; a person with no company gets a lead of their own)
OnePageCRMDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
ClozeCompaniesLeads (matched by name)
ClozeContactsContacts (on their company's lead; a person with no company gets a lead of their own)
ClozeDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
Less Annoying CRMCompaniesLeads (matched by name)
Less Annoying CRMContactsContacts (on their company's lead; a person with no company gets a lead of their own)
Less Annoying CRMDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
Pipeline CRMCompaniesLeads (matched by name)
Pipeline CRMPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
Pipeline CRMDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
Zendesk SellCompaniesLeads (matched by name)
Zendesk SellPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
Zendesk SellDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
CloseLeadsLeads (matched by name)
CloseContactsContacts (on their company's lead; a person with no company gets a lead of their own)
CloseOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
CopperCompaniesLeads (matched by name)
CopperPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
CopperOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
folkCompaniesLeads (matched by name)
folkPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
folkDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
InsightlyOrganisationsLeads (matched by name)
InsightlyContactsContacts (on their company's lead; a person with no company gets a lead of their own)
InsightlyOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
Bitrix24CompaniesLeads (matched by name)
Bitrix24ContactsContacts (on their company's lead; a person with no company gets a lead of their own)
Bitrix24DealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
CapsuleOrganisationsLeads (matched by name)
CapsulePeopleContacts (on their company's lead; a person with no company gets a lead of their own)
CapsuleOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
HighLevelBusinessesLeads (matched by name)
HighLevelContactsContacts (on their company's lead; a person with no company gets a lead of their own)
HighLevelOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
SugarCRMAccountsLeads (matched by name)
SugarCRMContactsContacts (on their company's lead; a person with no company gets a lead of their own)
SugarCRMOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
SuiteCRMAccountsLeads (matched by name)
SuiteCRMContactsContacts (on their company's lead; a person with no company gets a lead of their own)
SuiteCRMOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
SalesflareAccountsLeads (matched by name)
SalesflareContactsContacts (on their company's lead; a person with no company gets a lead of their own)
SalesflareOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
BreakcoldCompaniesLeads (matched by name)
BreakcoldPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
BreakcoldDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
VtigerOrganizationsLeads (matched by name)
VtigerContactsContacts (on their company's lead; a person with no company gets a lead of their own)
VtigerOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
TwentyCompaniesLeads (matched by name)
TwentyPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
TwentyOpportunitiesOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)
AttioCompaniesLeads (matched by name)
AttioPeopleContacts (on their company's lead; a person with no company gets a lead of their own)
AttioDealsOpportunities (pipelines and statuses matched by name, missing ones created; each sits on a lead)

What the Close API cannot do

  • It cannot create a meeting, so a meeting is written as a note with its date and attendees.
  • It cannot set a lead's creation date or creator, or an opportunity's lost date: a lead shows the date of the move and the source's date stays in a custom date field. Contacts, opportunities, notes, calls, emails, text messages and tasks carry their original dates.
  • It cannot turn off your own webhooks and integrations (Zapier and similar), which run on every record created. Pause them before the run if they message people.
  • It cannot undo a delete: a cancel removes what this migration created for good.
  • It has no reference field between a custom object and a lead, contact or another custom object (the docs show none), so a link is a lead choice plus the linked record's name in a text field.
  • Custom activities (a Close custom activity type) are written with their original date, owner and contact, always published, so nothing is sent; no source but Close has them, and Close to Close is not offered.

Matching, and what is never changed

  • A contact is matched on email and a lead on name before anything is created. A record that matches one you already had is linked to, not written: its values are yours, and a cancel never removes it.
  • 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.

Close's request limit

Close limits requests per kind of call and per key. Shuttio reads the limit from every answer, waits when it is spent and pauses the run, to resume where it stopped, when Close keeps refusing.

Known limits

  • Lists, products, projects, leads (other than companies) and every object other than people, companies and deals are not carried.
  • A rollback deletes what the migration created: activities and tasks, opportunities, contacts and leads, then the statuses, pipelines and custom fields it added. Records that already existed are not touched.

Not answered here? Email help@shuttio.com.