Into Capsule

Sources that can move into Capsule: Spreadsheet / CSV, HubSpot, Pipedrive, Affinity, Freshsales, ActiveCampaign, OnePageCRM, Zendesk Sell, Close, folk, Insightly, Bitrix24, HighLevel, SugarCRM, SuiteCRM, Salesflare, Vtiger, Twenty, Attio. A CSV import is free. A CRM migration is free under 5,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. Capsule to Capsule is not offered.

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

Connect

• Press Connect Capsule, sign in to Capsule and allow read and write access (OAuth).
• Sign in as an administrator: only an administrator can add pipelines, custom fields and tags, and a user without that right makes the run skip them and say so.
• Shuttio's access is stored encrypted and revoked and deleted 14 days after the migration finishes; you can revoke it in Capsule sooner. A migration is pinned to the Capsule account it first wrote to: a sign-in to another account is refused.

What Shuttio writes

• People and companies as Capsule people and organisations, with every email, phone number, website, social profile and address the source gives, job title, description and owner. A person is linked to their organisation.
• Deals as opportunities with their value, expected close date, milestone, owner and party. Pipelines and stages become Capsule pipelines and milestones, created when Capsule has none of that name.
• Projects as projects, linked to their person or company and to their opportunity.
• Your own fields as Capsule custom fields, created for you: text, number, date, yes/no, a list of choices and a multiple-choice list (several choices on one record). A field Capsule already has under that name and a type that fits is reused, never retyped. Tags are created when Capsule lacks them.
• A deal or project that names several people or companies: the first is its party, the others are added to it. A lost deal's lost reason, a project's board and stage, and a person's title (Mr, Ms) are matched by name in Capsule and created when missing. Only an administrator can create them, Capsule holds at most 50 titles and 30 boards, and a value Capsule will not take is left off the record and counted in the run summary.
• Notes, and meetings and calls as notes of the Meeting and Call activity type, with the original date; tasks with their due date, description and done state. Each hangs off the first record it names that migrated: a deal, then a project, a person, a company.
• Owners are matched to the Capsule user with the same email, for records, tasks and the author of a note. No user is invited: each is a paid seat. A record or task whose owner has no user stays with the user who connected Capsule, and a note's author is named in its first line ("Author: ..."). A task of a custom type (Lunch) is filed under the task category of that name, created when missing. A task that repeats weekly, monthly or yearly repeats in Capsule.
• Attachments, with the full migration only (the sample moves none): each file is a note, "Attachment: <file name>", on the opportunity, project, person or organisation it was on. Capsule keeps attachments only on notes. The Attachments checkbox ticked Options turns them off.

Where each thing lands

Matching, and what is never changed

• A person is matched on email and an organisation on website domain, then 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. The run counts them.
• Rows that share an email or a domain in one run become one record.

Capsule's request limit

Capsule allows 4,000 requests an hour for each user, and a record is one request (a person costs two, for the lookup). Shuttio keeps under the limit, so 10,000 records take about three hours. When the hour is used up the run pauses and says when the quota comes back; press Resume then.

Known limits

• A file over 50 MB, and a file that is only a link, is listed as a failed row and not copied.
• A logged email is written as a note (subject, from, to, date, body): Capsule's API creates notes only.
• Source lists are not carried: Capsule has tags and filters, not static lists.
• A note or task hangs off one record: anything that names more is written on the first and the run counts them. A person has one organisation: a second company on a person is not linked.
• A deal or project needs a person or company. One whose person and company did not migrate is reported as failed and written by a Retry once they exist.
• A rollback deletes what the migration created: records with their notes, tasks and attachments, then the milestones, pipelines, tags and custom fields it added. Records that already existed are not touched.