Supported CRMs

QuillSwitch supports migration between 20+ CRM platforms today, with more on the way. Every supported CRM includes data migration and workflow migration. Workflows are read automatically from Salesforce and HubSpot and captured through guided intake for the rest, then translated and run on the new CRM.

Tier 1 — Full Bidirectional

Records, owners, pipelines and workflows move between every pair. The table below shows exactly what each one reads and writes.

Salesforce logoSalesforce
DataWorkflowsBidirectional
Workflows read automatically

Record-triggered Flows and Process Builder, read automatically with conditions, updates, tasks and emails.

Apex triggers, screen flows and scheduled flows are flagged in a manual-rebuild checklist.

HubSpot logoHubSpot
DataWorkflowsBidirectional
Workflows read automatically

Contact, company and deal workflows, read automatically with branches, delays, property updates and tasks.

Sales sequences, list memberships and form or email-event triggers are flagged in a manual-rebuild checklist.

Pipedrive logoPipedrive
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically (Pipedrive has no automation API).

Saved filters are documented in a manual-rebuild checklist.

Zoho CRM logoZoho CRM
DataWorkflowsBidirectional
Workflows discovered automatically, confirmed with you

Workflow rules are discovered automatically; their conditions and actions are confirmed in guided intake.

Blueprints and macros are documented in a manual-rebuild checklist.

Microsoft Dynamics 365 logoMicrosoft Dynamics 365
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Power Automate cloud flows and business rules are documented in a manual-rebuild checklist.

Tier 2 — Full Migration

Full data migration and workflow migration between these CRMs and any Tier 1 CRM.

Attio logoAttio
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Close logoClose
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Copper logoCopper
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Freshsales logoFreshsales
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

ActiveCampaign logoActiveCampaign
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Insightly logoInsightly
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Monday.com CRM logoMonday.com CRM
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Monday board automations and integrations recipes are documented in a manual-rebuild checklist.

Map each CRM object to a Monday board before migrating.

Clarify logoClarify
DataWorkflowsBidirectional

Salesforce flows become native Clarify workflows, created disabled for review: triggers, conditions, decisions, field and owner updates, tasks, emails, waits and webhooks.

Email alerts whose template lives outside the flow, callouts through named credentials, sequences and lists are listed to add in Clarify.

Connects with a Clarify API key

Airtable logoAirtable
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Airtable automations and scripts are documented in a manual-rebuild checklist.

Map each CRM object to an Airtable base and table before migrating.

Tier 3 — Source Only

Migrate data and workflows out of these CRMs into any Tier 1 platform.

Agile CRM logoAgile CRM
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically on the destination CRM.

Zendesk Sell logoZendesk Sell
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically on the destination CRM.

Tier 4 — Expanding

Full data migration and workflow migration between these CRMs and any Tier 1 CRM. More pairs coming soon.

Capsule CRM logoCapsule CRM
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Nimble logoNimble
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

SugarCRM logoSugarCRM
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Keap logoKeap
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

NetSuite CRM logoNetSuite CRM
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Nutshell logoNutshell
DataWorkflowsBidirectional
Workflows captured through guided intake

Automations captured through guided intake, then translated and run automatically.

Tier 5 — Planned

Data migration support planned. Contact us for timelines.

Streak logoStreak
DataWorkflowsBidirectional
Less Annoying CRM logoLess Annoying CRM
DataWorkflowsBidirectional
Vtiger logoVtiger
DataWorkflowsBidirectional
Bitrix24 logoBitrix24
DataWorkflowsBidirectional

What data moves, Tier 1 CRM by CRM

“From” is reading that CRM as the source; “Into” is writing to it as the destination. Anything marked partial or not yet is reported in the migration, never dropped silently.

FeatureSalesforceHubSpotPipedriveZoho CRMMicrosoft Dynamics 365
Companies, contacts, deals, notes, tasksMoved with their links to each other and their owners.From FullInto FullFrom FullInto FullFrom FullInto FullFrom FullInto FullFrom FullInto Full
Test run, undo, catch-up, resumeRun a small sample first, remove what a run created, move only what changed since, and pick up after a restart.From FullInto FullFrom FullInto FullFrom FullInto FullFrom FullInto FullFrom FullInto Full
Deal pipelines and stagesDeals land in the same-named pipeline and stage, won and lost kept.From PartialInto Partial1From FullInto FullFrom FullInto FullFrom FullInto FullFrom PartialInto Partial2
Custom fieldsRead from the source; created in the destination when it has no matching field.From FullInto FullFrom FullInto FullFrom FullInto FullFrom FullInto Partial3From FullInto Partial4
Calls, emails, meetingsLogged activity moved with its details.From PartialInto Partial5From FullInto FullFrom PartialInto Partial6From Not yetInto Not yet7From Not yetInto Not yet8
Files and attachmentsAttached files copied onto the migrated records.From FullInto FullFrom FullInto FullFrom FullInto FullFrom Not yetInto Not yet9From Not yetInto Not yet10
Email opt-outsUnsubscribe and do-not-contact flags carried over.From FullInto FullFrom FullInto FullFrom FullInto Partial11From FullInto FullFrom FullInto Full
Original created datesKept, so reports by age still work.From FullInto FullFrom FullInto FullFrom FullInto Partial11From FullInto Partial12From FullInto Not yet13
  1. The org's opportunity stages are read, with which are won and lost, and deals are matched to them by name. Sales processes that limit the stages of a record type aren't read.
  2. Open deals arrive at the default stage; won and lost are carried by closing the opportunity.
  3. Into Zoho, only to fields that already exist; create them there first.
  4. Into Dynamics, only to columns that already exist; creating them needs System Customizer rights.
  5. Logged emails, calls and events (meetings) are read; what arrives in the destination depends on that CRM.
  6. Activities (tasks, calls, emails, meetings) move as the same type where the other CRM has it.
  7. Tasks move. Calls and meetings in the source become plain tasks.
  8. Tasks and notes move. Appointments, calls and emails don't.
  9. Files attached to records aren't copied to or from Zoho yet; each run says so.
  10. Files attached to records aren't copied to or from Dynamics 365 yet; each run says so.
  11. Into Pipedrive, written to a field.
  12. Written where the Zoho org has a field for it.
  13. Read from Dynamics; not written into it yet.

What workflow migration covers

Translated workflows run on the destination CRM. Anything that can't run automatically comes with a manual-rebuild checklist that preserves the original logic.

Automation triggers

Record created, record updated and field-change triggers run automatically. Time-based, form and email-event triggers are documented for manual rebuild.

Conditions and branching

Multi-condition logic, AND/OR groups and if/else branches.

Field updates, tasks and owner changes

Run automatically on the destination CRM.

Delays

Wait steps of minutes to weeks.

Email notifications

Sent through your connected email service. Multi-step sales sequences and drip campaigns are documented for manual rebuild.

Assignment and routing

Owner-assignment steps run automatically. Round-robin rotation rules are documented for manual rebuild.

Lead scoring, custom views and filters

Documented in a manual-rebuild checklist with the original logic.

Don't see your CRM?

We're actively adding new platforms. Reach out and we'll prioritize your CRM.

Request a CRM