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

Migrate into Less Annoying CRM: where data lands, setup, limits

What Shuttio writes into Less Annoying CRM, where each object lands, how to connect, and what its API reference does not show (custom field values, a note's creation date, owner emails).

Last updated: 15 November 2026

Sources that can move into Less Annoying 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.

Object by object: What objects are supported for Less Annoying CRM migrations.

Source by source: Less Annoying CRM support matrix.

Connect

  • Paste an API key (Settings, API in Less Annoying CRM). A key has its own read, create, edit and delete permissions: give it all four for a migration into Less Annoying CRM. Shuttio checks it with a live call before it stores anything.
  • The key is stored encrypted and deleted 14 days after the migration finishes; there is nothing to revoke. A migration is pinned to the Less Annoying CRM account it first wrote to: a key for another account is refused.

What Shuttio writes

  • People as Less Annoying CRM contacts, with name, every email and phone number, website, job title, background info, birthday, address and the company they work at (linked by the company's name). A person is matched on its exact email only; a match is linked to and only its empty single fields are filled.
  • Companies as Less Annoying CRM companies, with name, background info, emails, phones, websites and address. A company is matched on its exact website first, then its exact name (Less Annoying CRM allows one company of a name).
  • Deals as pipeline items on their person or company, in the pipeline and status of the same name. The deal's name, amount, expected close date, source stage and summary go in the item's note, because a pipeline item has no field for them.
  • Notes, tasks and meetings on the contact or company they belong to: a note keeps its date in the contact's history, a task its due date and whether it is done, a meeting becomes an event with its contacts as attendees. Calls become notes.

Where each thing lands

FromObjectLands in Less Annoying CRM as
HubSpotContactsContacts, as Cloze people (matched by email, linked to their company)
HubSpotCompaniesCompanies (matched by domain, then name, else created)
HubSpotDealsDeals, written as projects (segment and stage matched by name)
PipedrivePersonsContacts, as Cloze people (matched by email, linked to their company)
PipedriveOrganizationsCompanies (matched by domain, then name, else created)
PipedriveDealsDeals, written as projects (segment and stage matched by name)
AffinityPersonsContacts, as Cloze people (matched by email, linked to their company)
AffinityOrganizationsCompanies (matched by domain, then name, else created)
AffinityOpportunitiesDeals, written as projects (segment and stage matched by name)
Zoho CRMAccountsCompanies (matched by domain, then name, else created)
Zoho CRMContactsContacts, as Cloze people (matched by email, linked to their company)
Zoho CRMDealsDeals, written as projects (segment and stage matched by name)
FreshsalesAccountsCompanies (matched by domain, then name, else created)
FreshsalesContactsContacts, as Cloze people (matched by email, linked to their company)
FreshsalesDealsDeals, written as projects (segment and stage matched by name)
ActiveCampaignAccountsCompanies (matched by domain, then name, else created)
ActiveCampaignContactsContacts, as Cloze people (matched by email, linked to their company)
ActiveCampaignDealsDeals, written as projects (segment and stage matched by name)
OnePageCRMCompaniesCompanies (matched by domain, then name, else created)
OnePageCRMContactsContacts, as Cloze people (matched by email, linked to their company)
OnePageCRMDealsDeals, written as projects (segment and stage matched by name)
ClozeCompaniesCompanies (matched by domain, then name, else created)
ClozeContactsContacts, as Cloze people (matched by email, linked to their company)
ClozeDealsDeals, written as projects (segment and stage matched by name)
Less Annoying CRMCompaniesCompanies (matched by domain, then name, else created)
Less Annoying CRMContactsContacts, as Cloze people (matched by email, linked to their company)
Less Annoying CRMDealsDeals, written as projects (segment and stage matched by name)
Pipeline CRMCompaniesCompanies (matched by domain, then name, else created)
Pipeline CRMPeopleContacts, as Cloze people (matched by email, linked to their company)
Pipeline CRMDealsDeals, written as projects (segment and stage matched by name)
Zendesk SellCompaniesCompanies (matched by domain, then name, else created)
Zendesk SellPeopleContacts, as Cloze people (matched by email, linked to their company)
Zendesk SellDealsDeals, written as projects (segment and stage matched by name)
CloseLeadsCompanies (matched by domain, then name, else created)
CloseContactsContacts, as Cloze people (matched by email, linked to their company)
CloseOpportunitiesDeals, written as projects (segment and stage matched by name)
CopperCompaniesCompanies (matched by domain, then name, else created)
CopperPeopleContacts, as Cloze people (matched by email, linked to their company)
CopperOpportunitiesDeals, written as projects (segment and stage matched by name)
folkCompaniesCompanies (matched by domain, then name, else created)
folkPeopleContacts, as Cloze people (matched by email, linked to their company)
folkDealsDeals, written as projects (segment and stage matched by name)
InsightlyOrganisationsCompanies (matched by domain, then name, else created)
InsightlyContactsContacts, as Cloze people (matched by email, linked to their company)
InsightlyOpportunitiesDeals, written as projects (segment and stage matched by name)
Bitrix24CompaniesCompanies (matched by domain, then name, else created)
Bitrix24ContactsContacts, as Cloze people (matched by email, linked to their company)
Bitrix24DealsDeals, written as projects (segment and stage matched by name)
CapsuleOrganisationsCompanies (matched by domain, then name, else created)
CapsulePeopleContacts, as Cloze people (matched by email, linked to their company)
CapsuleOpportunitiesDeals, written as projects (segment and stage matched by name)
HighLevelBusinessesCompanies (matched by domain, then name, else created)
HighLevelContactsContacts, as Cloze people (matched by email, linked to their company)
HighLevelOpportunitiesDeals, written as projects (segment and stage matched by name)
SugarCRMAccountsCompanies (matched by domain, then name, else created)
SugarCRMContactsContacts, as Cloze people (matched by email, linked to their company)
SugarCRMOpportunitiesDeals, written as projects (segment and stage matched by name)
SuiteCRMAccountsCompanies (matched by domain, then name, else created)
SuiteCRMContactsContacts, as Cloze people (matched by email, linked to their company)
SuiteCRMOpportunitiesDeals, written as projects (segment and stage matched by name)
SalesflareAccountsCompanies (matched by domain, then name, else created)
SalesflareContactsContacts, as Cloze people (matched by email, linked to their company)
SalesflareOpportunitiesDeals, written as projects (segment and stage matched by name)
BreakcoldCompaniesCompanies (matched by domain, then name, else created)
BreakcoldPeopleContacts, as Cloze people (matched by email, linked to their company)
BreakcoldDealsDeals, written as projects (segment and stage matched by name)
VtigerOrganizationsCompanies (matched by domain, then name, else created)
VtigerContactsContacts, as Cloze people (matched by email, linked to their company)
VtigerOpportunitiesDeals, written as projects (segment and stage matched by name)
TwentyCompaniesCompanies (matched by domain, then name, else created)
TwentyPeopleContacts, as Cloze people (matched by email, linked to their company)
TwentyOpportunitiesDeals, written as projects (segment and stage matched by name)
AttioCompaniesCompanies (matched by domain, then name, else created)
AttioPeopleContacts, as Cloze people (matched by email, linked to their company)
AttioDealsDeals, written as projects (segment and stage matched by name)

What Shuttio does not do, and why

  • Custom field values. Less Annoying CRM's API reference shows how to define a custom field but not how to write a value onto a contact, a company or a pipeline item, so Shuttio writes each such value as a line in a note on the record instead, and the review lists them before the run.
  • Pipelines. A pipeline is matched by name and never created: a deal whose pipeline has no namesake fails with that reason, and a status with no namesake puts the deal in the pipeline's first status.
  • Owners. Every contact and company is assigned to a user. The user list carries no email, so an owner matches only the user whose key runs the migration; every other record is assigned to that user. No one is invited.
  • Creation dates. Less Annoying CRM does not let a migration set when a record, note or task was created: they show the migration date. A note keeps its original date in the contact's history.
  • Files and groups are not written yet.

Matching, and what is never changed

  • A person is matched on email and a company on website, then name, before anything is created. A record that matches one you already had is linked to; only its empty single fields are filled (its email, phone and website lists are left as they are), and a cancel never removes it.
  • A create that fails without an answer (a dropped connection, a 5xx) is never sent again. Shuttio reports it as maybe written, does not delete it on a cancel, and asks you to look for it in your account.
  • A cancel deletes the contacts, companies, pipeline items, notes, tasks and events this migration created, by the ids Less Annoying CRM gave them.

Less Annoying CRM's request limit

Less Annoying CRM publishes no request limit. Shuttio sends one request at a time, paces itself, waits out a refusal for being too fast and pauses the run, to resume where it stopped, when Less Annoying CRM keeps refusing.

Known limits

  • Files, lists, emails, products and every object other than people, companies and deals are not carried.
  • A rollback deletes what the migration created: contacts, companies, pipeline items, notes, tasks and events. Records that already existed are not touched.

Not answered here? Email help@shuttio.com.