Switching to Cyril.

Bring your records across from Salesforce, HubSpot, Pipedrive or a spreadsheet. You see the counts and the mapping before anything moves, and any import can be rolled back for 30 days.

Four ways in.

Every route is a one-way import into Cyril. Cyril reads from your old system and never writes back to it.

Migration sources, how each connects, what comes across, and status
FromConnect withWhat comes acrossStatus
SalesforceYour Salesforce sign-inAccounts, contacts, leads, opportunities and their contact roles, tasks, events, notes, attachments and files, campaigns and members, and custom objects.Sales Cloud only. Marketing Cloud is out of scope.Available
PipedriveAn API tokenOrganisations, people, deals, activities and notes, with custom fields on organisations, people and deals mapped by you.Available
HubSpotYour HubSpot sign-inContacts, companies, deals and tickets.Built and tested against a simulated account. Not yet run against a real HubSpot portal.Coming soon
Anything elseA CSV file, up to 50 MBRecords from any tool that exports a spreadsheet, mapped column by column. Save the mapping as a template for the next file.Available

You see the mapping first.

Cyril suggests where each field should go. You confirm, change or skip every one before a single record moves.

Fields that have no home in Cyril can land in a custom field rather than being dropped. Fields you choose to skip are listed in the report.

Mapping, Salesforce AccountRowan Hill demo workspace
Where Salesforce records land in Cyril, by business model
In SalesforceCyril, B2BCyril, B2C
Business accountCompanySkipped, or flattened if you choose
Person accountContact under a placeholder company, or skippedContact
ContactContact, on its companyContact
LeadLeadLead
OpportunityDeal, on its companyDeal, on its contact
Custom object Engagement__cExternal recordExternal record

You choose B2B or B2C once, when your workspace is set up, and it does not change. If your Salesforce data leans the other way, preflight says so before mapping starts, and you decide whether to skip or flatten.

Nothing moves until you have seen it.

Six steps, in this order. Imports run in the background and tell you when they finish.

  1. Connect

    Sign in to the old system, add a token or upload a file. Cyril only reads.

  2. Preflight

    Counts what is there, lists custom objects, and names any field the connected user cannot read.

  3. Map

    Review a suggested home for every field. Change it, send it to a custom field, or skip it.

  4. Preview

    For spreadsheets, the first ten rows with mapped fields shown, and errors flagged before you start.

  5. Import

    Choose to skip bad rows, stop on the first error, or fix common problems. Then it runs.

  6. Check the report

    Rows imported, rows skipped, and every error with its row number.

Changed your mind? Roll it back.

Any import can be rolled back for 30 days. You see exactly what will be removed before you confirm, and records your team has edited since are left alone.

Running both for a while.

Most teams keep the old system open until the numbers match. Cyril is built for that stretch.

Re-pull on a schedule
During the transition, Salesforce can be pulled again daily or weekly, using the mapping from your last run.
Run it twice, safely
A second run updates the records it matched last time instead of creating duplicates.
Disconnect when you are sure
Check the counts, spot-check a few records, then disconnect. The access is revoked and the imported data stays.

What stays behind

Said plainly now, so it is not a surprise later.

  • Any systemChanges made in Cyril never flow back to the old tool. There is no two-way sync.
  • SalesforceMarketing Cloud, and Service Cloud customisations beyond the standard objects. Custom objects arrive as records you can browse; search, linking and automation on them come later.
  • HubSpotMarketing emails, forms, lists, workflows, ads and website content.
  • PipedriveProducts, files, email and pipeline stages.
  • Locked fieldsAnything the connected person cannot read in the source. These are listed by name, so you can grant access and run again.

Leaving is free, too.

Your data belongs to you. Exporting it costs nothing, on every plan, whenever you like.

Any record type
Companies, contacts, invoices, projects, tickets and the rest, filtered how you need.
Three formats
CSV, Excel or JSON. Large exports run in the background.
The whole organisation
Every module, in one zip file, from one button.
On a schedule
Daily, weekly or monthly, with the file waiting in Recent exports.
A team around a table while one person maps out a plan on a whiteboard

Help moving in.

Migration is real work. Several systems of record have to become one, and the data in them disagrees. That reconciliation happens once, up front, whoever does it. Founding members do not do it alone.

  • Priority onboarding with our team
  • Founding pricing, locked in
  • A say in what we build next, importers included