01127
Websites & commerce
Publishing, storefronts, newsletters, and web delivery.
442 routes across 161 platformsMove with
Move with
a plan.
Step-by-step migration guides showing what transfers, where everything goes, what could go wrong, how long it takes, how to go back, and how to check everything worked.
What transfersSee what moves cleanly, needs work, or stays behind
Precise timelineActive work separated from waiting
Rollback planTriggers, deadline, and proof
Verification reportBlocking checks with evidence
The catalog
Evidence-led paths, not generic advice.
442 complete migration paths. Search by tool or filter where you are and where you’re going; every guide shows its current review status.
Browse visually
Choose an area, then a category.
0269
Data & intelligence
Operational data, analytics, search, and AI retrieval.
0352
Engineering & infrastructure
Code, deployment, runtime, storage, and production operations.
0477
Customers & operations
Revenue, service, finance, agreements, and automation.
0590
Work & collaboration
Team communication, files, knowledge, planning, and design.
0627
Identity, learning & community
Access, credentials, education, and member spaces.
442 playbooksShowing all documented paths; review status appears on every guide
Password managersneeds review
1Password → Bitwarden
Move 1Password personal and business vaults into Bitwarden while protecting plaintext exports and reconciling every login, custom field, TOTP, passkey, attachment, item type, shared vault, permission, policy, and integration.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Password managersneeds review
1Password → LastPass
Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from 1Password into LastPass with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
CRMneeds review
ActiveCampaign → HubSpot
Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from ActiveCampaign into HubSpot with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–160 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Newsletterneeds review
ActiveCampaign → Kit
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from ActiveCampaign into Kit with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newsletterneeds review
ActiveCampaign → Klaviyo
Move ActiveCampaign contacts into Klaviyo with a subscriber CSV and a separate suppression file. Klaviyo's built-in list sync does not include ActiveCampaign, and flows do not transfer.
- Elapsed
- 5 to 12 days
- Active
- 10 to 20 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Newsletterneeds review
ActiveCampaign → Mailchimp
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from ActiveCampaign into Mailchimp with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
ELT and data integrationneeds review
Airbyte → Fivetran
Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Airbyte to Fivetran with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial6 manual2 lost
ELT and data integrationneeds review
Airbyte → Stitch
Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Airbyte to Stitch with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial6 manual2 lost
Databasesagent reviewed
Airtable → Coda
Move Airtable bases, tables, records, views, linked records, attachments, formulas, rollups, interfaces, automations, permissions, and integrations into Coda using its beta first-party importer and explicit fix report.
- Elapsed
- Editorial estimate: 10–25 business days
- Active
- Editorial estimate: 45–90 hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Databasesneeds review
Airtable → Google Sheets
Each Airtable table is its own CSV. Google Sheets imports that file. Linked records, automations, and attachments do not come along as a base.
- Elapsed
- 1 to 3 weeks
- Active
- 12 to 35 hours
- Highest risk
- Critical
0 clean5 partial3 manual4 lost
Knowledgeagent reviewed
Airtable → Notion
Move Airtable records into Notion databases while preserving field meaning, relations, attachments, views, ownership, automations, permissions, and evidence for anything CSV cannot carry.
- Elapsed
- Editorial estimate: 10–20 business days
- Active
- Editorial estimate: 40–75 hours
- Highest risk
- Critical
0 clean2 partial4 manual4 lost
Hosted searchneeds review
Algolia → Elastic Cloud
Move indexes, collections, records, and object ids, field schema and searchable attributes, text analysis, tokenization, and languages, ranking, relevance, and tie-breaking, synonyms, rules, and query rewriting, facets, filters, sorting, and replicas, query api and frontend clients, analytics, personalization, and experiments from Algolia to Elastic Cloud with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Hosted searchneeds review
Algolia → Meilisearch
Browse each Algolia index and add the hits to Meilisearch. Set the primary key yourself. objectID often works, until another field also ends in id, or the id contains a character Meilisearch rejects.
- Elapsed
- 8–20 business days
- Active
- 30–70 hours
- Highest risk
- Critical
0 clean7 partial3 manual2 lost
Hosted searchneeds review
Algolia → Typesense Cloud
Move indexes, collections, records, and object ids, field schema and searchable attributes, text analysis, tokenization, and languages, ranking, relevance, and tie-breaking, synonyms, rules, and query rewriting, facets, filters, sorting, and replicas, query api and frontend clients, analytics, personalization, and experiments from Algolia to Typesense Cloud with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Data warehousesneeds review
Amazon Redshift → Google BigQuery
Move databases, schemas, tables, and rows, data types, precision, nulls, and time zones, views, materialized views, and sql dialect, primary keys, constraints, and data quality, users, roles, grants, row and column policy, pipelines, stages, external tables, and file formats, scheduled queries, tasks, procedures, and udfs, bi, dbt, notebooks, and downstream consumers from Amazon Redshift to Google BigQuery with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial7 manual1 lost
Data warehousesneeds review
Amazon Redshift → Snowflake
Move databases, schemas, tables, and rows, data types, precision, nulls, and time zones, views, materialized views, and sql dialect, primary keys, constraints, and data quality, users, roles, grants, row and column policy, pipelines, stages, external tables, and file formats, scheduled queries, tasks, procedures, and udfs, bi, dbt, notebooks, and downstream consumers from Amazon Redshift to Snowflake with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial7 manual1 lost
DNS and CDNneeds review
Amazon Route 53 → Cloudflare DNS
Move zones, record sets, names, and ttls, nameservers, delegation, and dnssec, traffic steering and health checks, proxy, cdn, origins, and host headers, tls certificates and security policy, caching, purge, and stale behavior, redirects, rewrites, edge logic, and headers, waf, bot, rate-limit, and access controls from Amazon Route 53 to Cloudflare DNS with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean1 partial8 manual1 lost
DNS and CDNneeds review
Amazon Route 53 → Fastly
Move zones, record sets, names, and ttls, nameservers, delegation, and dnssec, traffic steering and health checks, proxy, cdn, origins, and host headers, tls certificates and security policy, caching, purge, and stale behavior, redirects, rewrites, edge logic, and headers, waf, bot, rate-limit, and access controls from Amazon Route 53 to Fastly with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean1 partial8 manual1 lost
Object storageneeds review
Amazon S3 → Backblaze B2
Move buckets, object keys, and binary content, checksums, etags, and integrity evidence, metadata, tags, and content headers, versions and delete markers, acls, bucket policy, and public access, encryption and customer-managed keys, lifecycle rules and storage classes, cors, events, and application integrations from Amazon S3 to Backblaze B2 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Object storageneeds review
Amazon S3 → Cloudflare R2
Move buckets, object keys, and binary content, checksums, etags, and integrity evidence, metadata, tags, and content headers, versions and delete markers, acls, bucket policy, and public access, encryption and customer-managed keys, lifecycle rules and storage classes, cors, events, and application integrations from Amazon S3 to Cloudflare R2 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Analyticsneeds review
Amplitude → Google Analytics 4
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Amplitude into Google Analytics 4 with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Amplitude → Mixpanel
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Amplitude into Mixpanel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Amplitude → PostHog
Move Amplitude events, identities, properties, conversions, cohorts, consent, collection, and historical evidence into PostHog with a schema map, identity aliases, and a labeled historical import.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean7 partial4 manual1 lost
Backendneeds review
Appwrite → Firebase
Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Appwrite into Firebase with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Backendneeds review
Appwrite → Supabase
Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Appwrite into Supabase with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Project managementneeds review
Asana → Basecamp
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Asana into Basecamp with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementagent reviewed
Asana → ClickUp
Plan an Asana-to-ClickUp migration using the documented project-to-Space/Folder/List choices, section-to-Label/List/status choices, people dispositions, completion handling, and attachment option, with explicit manual handling for unsupported or undocumented fields and workflows.
- Elapsed
- Editorial estimate: 8–16 business days
- Active
- Editorial estimate: 30–54 active hours
- Highest risk
- Critical
0 clean8 partial4 manual0 lost
Project managementneeds review
Asana → Jira
Move Asana projects, tasks, sections, people, comments, attachments, and custom fields into Jira Cloud without treating one importer pass as a finished operating model.
- Elapsed
- 15–35 business days
- Active
- 55–120 hours
- Highest risk
- Critical
0 clean8 partial2 manual1 lost
Project managementneeds review
Asana → Linear
Move active product and engineering work from Asana to Linear while preserving comments, projects, dependencies, files, identities, and a deliberate workflow instead of importing years of stale tasks.
- Elapsed
- 8–15 business days
- Active
- 30–55 hours
- Highest risk
- Critical
3 clean4 partial1 manual2 lost
Project managementneeds review
Asana → monday.com
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Asana into monday.com with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
Asana → Smartsheet
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Asana into Smartsheet with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
Asana → Trello
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Asana into Trello with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Publishingneeds review
Astro → Ghost
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Astro into Ghost with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Publishingneeds review
Astro → WordPress
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Astro into WordPress with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Status pagesneeds review
Atlassian Statuspage → Better Stack
Move pages, domains, branding, and localization, components, groups, and current status, incidents, updates, and postmortems, scheduled maintenance and recurrence, subscribers and notification preferences, incident templates and communication policy, monitors, automation, and component mapping, apis, embeds, rss, and third-party components from Atlassian Statuspage to Better Stack with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Status pagesneeds review
Atlassian Statuspage → Instatus
Move pages, domains, branding, and localization, components, groups, and current status, incidents, updates, and postmortems, scheduled maintenance and recurrence, subscribers and notification preferences, incident templates and communication policy, monitors, automation, and component mapping, apis, embeds, rss, and third-party components from Atlassian Statuspage to Instatus with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Authentication and identityneeds review
Auth0 → Clerk
Move user profiles and stable subject ids, password hashes and hash parameters, mfa enrollments and recovery factors, social and enterprise identities, organizations, tenants, roles, and permissions, sessions, refresh tokens, and remembered devices, email, sms, and verification templates, hooks, actions, triggers, and webhooks from Auth0 to Clerk with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Authentication and identityneeds review
Auth0 → Firebase Authentication
Move user profiles and stable subject ids, password hashes and hash parameters, mfa enrollments and recovery factors, social and enterprise identities, organizations, tenants, roles, and permissions, sessions, refresh tokens, and remembered devices, email, sms, and verification templates, hooks, actions, triggers, and webhooks from Auth0 to Firebase Authentication with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Hostingneeds review
AWS Amplify Hosting → Cloudflare Pages
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from AWS Amplify Hosting into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
AWS Amplify Hosting → Vercel
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from AWS Amplify Hosting into Vercel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Code hostingagent reviewed
Azure DevOps → GitHub
Move Azure Repos and supported pull-request metadata into GitHub while separately planning Boards, Pipelines, Artifacts, permissions, identities, policies, service connections, and changes made after the final snapshot.
- Elapsed
- Editorial estimate: 18–35 business days
- Active
- Editorial estimate: 80–145 hours
- Highest risk
- Critical
1 clean6 partial5 manual2 lost
CI/CDneeds review
Azure DevOps → GitHub Actions
Move Azure Pipelines YAML, Classic builds, releases, variables, agents, and approvals into GitHub Actions without treating an importer pull request as a finished cutover.
- Elapsed
- 15–40 business days
- Active
- 60–140 hours
- Highest risk
- Critical
0 clean5 partial4 manual2 lost
Code hostingneeds review
Azure DevOps → GitLab
Move repositories, refs, pull requests, issues, users, LFS, pipelines, packages, permissions, webhooks, and audit evidence from Azure DevOps into GitLab with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
1 clean8 partial3 manual0 lost
Hostingneeds review
Azure Static Web Apps → Cloudflare Pages
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Azure Static Web Apps into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Azure Static Web Apps → Vercel
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Azure Static Web Apps into Vercel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Object storageneeds review
Backblaze B2 → Amazon S3
Move buckets, object keys, and binary content, checksums, etags, and integrity evidence, metadata, tags, and content headers, versions and delete markers, acls, bucket policy, and public access, encryption and customer-managed keys, lifecycle rules and storage classes, cors, events, and application integrations from Backblaze B2 to Amazon S3 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Object storageneeds review
Backblaze B2 → Cloudflare R2
Move buckets, object keys, and binary content, checksums, etags, and integrity evidence, metadata, tags, and content headers, versions and delete markers, acls, bucket policy, and public access, encryption and customer-managed keys, lifecycle rules and storage classes, cors, events, and application integrations from Backblaze B2 to Cloudflare R2 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Project managementagent reviewed
Basecamp → Asana
Move Basecamp projects and active to-dos into Asana while preserving an evidence archive for messages, Campfires, schedules, documents, comments, clients, and project access that cannot become ordinary tasks.
- Elapsed
- Editorial estimate: 8–16 business days
- Active
- Editorial estimate: 30–54 hours
- Highest risk
- Critical
0 clean6 partial3 manual4 lost
Project managementneeds review
Basecamp → ClickUp
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Basecamp into ClickUp with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Newsletterneeds review
Beehiiv → Ghost
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Beehiiv into Ghost with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newsletterneeds review
Beehiiv → Mailchimp
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Beehiiv into Mailchimp with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newsletterneeds review
Beehiiv → Substack
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Beehiiv into Substack with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Status pagesneeds review
Better Stack → Atlassian Statuspage
Move pages, domains, branding, and localization, components, groups, and current status, incidents, updates, and postmortems, scheduled maintenance and recurrence, subscribers and notification preferences, incident templates and communication policy, monitors, automation, and component mapping, apis, embeds, rss, and third-party components from Better Stack to Atlassian Statuspage with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Status pagesneeds review
Better Stack → Instatus
Move pages, domains, branding, and localization, components, groups, and current status, incidents, updates, and postmortems, scheduled maintenance and recurrence, subscribers and notification preferences, incident templates and communication policy, monitors, automation, and component mapping, apis, embeds, rss, and third-party components from Better Stack to Instatus with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Commerceneeds review
BigCommerce → Shopify
Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from BigCommerce into Shopify with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Commerceneeds review
BigCommerce → WooCommerce
Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from BigCommerce into WooCommerce with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Developmentagent reviewed
Bitbucket → GitHub
Move scoped Bitbucket repositories to GitHub, with pull-request metadata available only for eligible Server/Data Center 5.14+ migrations through GitHub Enterprise Importer. Cloud uses a source-and-history-only path (git clone --bare / git push --mirror, or GitHub Importer on GitHub.com for internet-reachable repos). GitHub Importer does not import issues, pull requests, or LFS objects.
- Elapsed
- Editorial estimate: 15–30 business days
- Active
- Editorial estimate: 60–110 hours
- Highest risk
- Critical
1 clean4 partial4 manual5 lost
Code hostingneeds review
Bitbucket → GitLab
Move Bitbucket repositories, branches, pull requests, issues, users, wikis, LFS data, pipelines, permissions, deployments, and integrations into GitLab with route-specific importer and identity checks.
- Elapsed
- 12–26 business days
- Active
- 58–110 hours
- Highest risk
- Critical
2 clean7 partial3 manual0 lost
Password managersneeds review
Bitwarden → 1Password
Move Bitwarden personal and organization vaults into 1Password while using the supported importer, securing export files, and reconciling logins, rich items, TOTP, passkeys, attachments, collections, access, recovery, and integrations.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Password managersneeds review
Bitwarden → LastPass
Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from Bitwarden into LastPass with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
Box → Dropbox
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from Box into Dropbox with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
Box → Google Drive
Move Box folders, files, versions, collaborations, groups, metadata, notes, shared links, and enterprise controls into Google Drive with explicit permission and scale safeguards.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Cloud storageneeds review
Box → OneDrive
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from Box into OneDrive with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Paymentsneeds review
Chargebee → Paddle
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Chargebee into Paddle with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Paymentsneeds review
Chargebee → Stripe Billing
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Chargebee into Stripe Billing with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Community platformsneeds review
Circle → Discourse
Move members, profiles, identities, and consent, spaces, categories, groups, and hierarchy, posts, topics, articles, and authorship, comments, replies, reactions, and mentions, images, uploads, video, and attachments, private messages and restricted content, roles, moderation, trust, bans, and permissions, courses, events, paywalls, and memberships from Circle to Discourse with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Community platformsneeds review
Circle → Mighty Networks
Move members, profiles, identities, and consent, spaces, categories, groups, and hierarchy, posts, topics, articles, and authorship, comments, replies, reactions, and mentions, images, uploads, video, and attachments, private messages and restricted content, roles, moderation, trust, bans, and permissions, courses, events, paywalls, and memberships from Circle to Mighty Networks with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
CI/CDneeds review
CircleCI → GitHub Actions
Move CircleCI workflows, jobs, orbs, contexts, caches, and service containers into GitHub Actions. Split one config.yml into one workflow file per workflow. Map requires to needs. Rebuild test parallelism, Docker Layer Caching, and contexts yourself.
- Elapsed
- 12–30 business days
- Active
- 50–110 hours
- Highest risk
- Critical
0 clean5 partial3 manual4 lost
CI/CDneeds review
CircleCI → GitLab
Move CircleCI jobs, workflows, images, caches, contexts, and orbs into GitLab CI/CD. Translate workflows into stages and rules. Replace contexts with group variables and orbs with CI/CD components. Keep CircleCI up until GitLab is the merge gate.
- Elapsed
- 12–28 business days
- Active
- 48–105 hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Authentication and identityneeds review
Clerk → Auth0
Move user profiles and stable subject ids, password hashes and hash parameters, mfa enrollments and recovery factors, social and enterprise identities, organizations, tenants, roles, and permissions, sessions, refresh tokens, and remembered devices, email, sms, and verification templates, hooks, actions, triggers, and webhooks from Clerk to Auth0 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Authentication and identityneeds review
Clerk → Firebase Authentication
Move user profiles and stable subject ids, password hashes and hash parameters, mfa enrollments and recovery factors, social and enterprise identities, organizations, tenants, roles, and permissions, sessions, refresh tokens, and remembered devices, email, sms, and verification templates, hooks, actions, triggers, and webhooks from Clerk to Firebase Authentication with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Project managementneeds review
ClickUp → Asana
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from ClickUp into Asana with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
ClickUp → Jira
Move ClickUp Lists into a new Jira space with Atlassian's ClickUp importer. The importer takes up to 10 Lists, always creates a new space, and cannot merge into a board you already built. Custom fields and statuses in Jira are shared, so a ClickUp-shaped workspace will not land as-is.
- Elapsed
- 8–18 business days
- Active
- 30–60 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Project managementneeds review
ClickUp → Linear
Move selected ClickUp Spaces, Folders, Lists, tasks, owners, statuses, priorities, estimates, dates, and labels into Linear while archiving collaboration and hierarchy that its CSV path cannot preserve.
- Elapsed
- 7–14 business days
- Active
- 28–48 hours
- Highest risk
- Critical
0 clean10 partial0 manual2 lost
Project managementneeds review
ClickUp → monday.com
monday.com has no ClickUp importer. You export a CSV and use the Excel import, which keeps the first tab, skips the Updates section, and will not take a second pass as an update.
- Elapsed
- 1 to 3 weeks
- Active
- 16 to 40 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
DNS and CDNneeds review
Cloudflare DNS → Amazon Route 53
Move zones, record sets, names, and ttls, nameservers, delegation, and dnssec, traffic steering and health checks, proxy, cdn, origins, and host headers, tls certificates and security policy, caching, purge, and stale behavior, redirects, rewrites, edge logic, and headers, waf, bot, rate-limit, and access controls from Cloudflare DNS to Amazon Route 53 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean1 partial8 manual1 lost
DNS and CDNneeds review
Cloudflare DNS → Fastly
Move zones, record sets, names, and ttls, nameservers, delegation, and dnssec, traffic steering and health checks, proxy, cdn, origins, and host headers, tls certificates and security policy, caching, purge, and stale behavior, redirects, rewrites, edge logic, and headers, waf, bot, rate-limit, and access controls from Cloudflare DNS to Fastly with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean1 partial8 manual1 lost
Hostingneeds review
Cloudflare Pages → AWS Amplify Hosting
Move a Cloudflare Pages application into AWS Amplify Hosting while translating Git builds, branch previews, Pages Functions, Workers bindings, redirects, headers, domains, environment values, Cloudflare data services, and observability.
- Elapsed
- 9–20 business days
- Active
- 42–82 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Hostingneeds review
Cloudflare Pages → Firebase Hosting
Move a Cloudflare Pages application into Firebase Hosting while translating builds, previews, Pages Functions, Workers bindings, redirects, headers, domains, environment values, Cloudflare data services, and operational evidence.
- Elapsed
- 8–18 business days
- Active
- 38–72 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Hostingneeds review
Cloudflare Pages → GitHub Pages
Move a static Cloudflare Pages site into GitHub Pages while preserving repository content and public URLs and explicitly extracting Functions, Workers bindings, data services, headers, previews, secrets, and observability into external systems.
- Elapsed
- 6–14 business days
- Active
- 28–56 hours
- Highest risk
- Critical
2 clean5 partial3 manual2 lost
Hostingneeds review
Cloudflare Pages → GitLab Pages
Move a static Cloudflare Pages site into GitLab Pages while preserving repository content and public routes and explicitly extracting Functions, Workers bindings, data services, response controls, secrets, previews, and observability into CI/CD or external systems.
- Elapsed
- 7–16 business days
- Active
- 32–62 hours
- Highest risk
- Critical
1 clean6 partial3 manual2 lost
Hostingneeds review
Cloudflare Pages → Netlify
Move a Cloudflare Pages site into Netlify while translating Git builds, previews, Pages Functions, Workers bindings, redirects, headers, domains, environment variables, Cloudflare data services, analytics, and deployment operations.
- Elapsed
- 7–16 business days
- Active
- 34–66 hours
- Highest risk
- Critical
1 clean6 partial5 manual0 lost
Hostingneeds review
Cloudflare Pages → Render
Move a Cloudflare Pages application into a Render static site and supporting services while translating builds, previews, Pages Functions, Workers bindings, routes, headers, domains, environment values, Cloudflare state, and operations.
- Elapsed
- 8–18 business days
- Active
- 38–74 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Hostingneeds review
Cloudflare Pages → Vercel
Move a Cloudflare Pages application into Vercel while translating Pages builds, Functions or Workers, redirects, headers, domains, environment variables, KV, R2, D1, analytics, previews, and Cloudflare DNS behavior.
- Elapsed
- 8–18 business days
- Active
- 36–70 hours
- Highest risk
- Critical
1 clean6 partial5 manual0 lost
Object storageneeds review
Cloudflare R2 → Amazon S3
Move buckets, object keys, and binary content, checksums, etags, and integrity evidence, metadata, tags, and content headers, versions and delete markers, acls, bucket policy, and public access, encryption and customer-managed keys, lifecycle rules and storage classes, cors, events, and application integrations from Cloudflare R2 to Amazon S3 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Object storageneeds review
Cloudflare R2 → Backblaze B2
Move buckets, object keys, and binary content, checksums, etags, and integrity evidence, metadata, tags, and content headers, versions and delete markers, acls, bucket policy, and public access, encryption and customer-managed keys, lifecycle rules and storage classes, cors, events, and application integrations from Cloudflare R2 to Backblaze B2 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Knowledgeneeds review
Coda → Google Docs
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Coda into Google Docs with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Documentationneeds review
Coda → Notion
Move Coda pages and table data into Notion while treating formulas, buttons, automations, Packs, controls, relations, permissions, comments, and doc history as an application redesign.
- Elapsed
- 10–22 business days
- Active
- 42–80 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Knowledgeneeds review
Coda → Obsidian
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Coda into Obsidian with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Documentationneeds review
Confluence → Notion
Move Confluence spaces, pages, comments, users, attachments, links, and selected structured content into Notion with explicit handling for permissions, macros, apps, versions, and large-space limits.
- Elapsed
- 10–22 business days
- Active
- 40–76 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Knowledgeneeds review
Confluence → Obsidian
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Confluence into Obsidian with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
CMSneeds review
Contentful → Astro
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Contentful into Astro with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
Contentful → Sanity
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Contentful into Sanity with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
Contentful → Strapi
Export Contentful with the CLI, recreate content types in Strapi, then load entries and assets with a script. Keep field names close and store the Contentful id on every type so you can rerun the import. Rich text, locales, and roles do not arrive as a one-click switch.
- Elapsed
- 15–40 business days
- Active
- 70–160 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
Contentful → WordPress
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Contentful into WordPress with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Password managersneeds review
Dashlane → 1Password
Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from Dashlane into 1Password with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Password managersneeds review
Dashlane → Bitwarden
Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from Dashlane into Bitwarden with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Observability and error trackingneeds review
Datadog → New Relic
Move applications, services, and entity identity, metrics and metric types, logs, parsing, and pipelines, traces, spans, and sampling, errors, issues, releases, and source maps, dashboards, queries, and variables, monitors, alert conditions, and notifications, slos, incidents, and burn-rate policy from Datadog to New Relic with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Observability and error trackingneeds review
Datadog → Sentry
Move applications, services, and entity identity, metrics and metric types, logs, parsing, and pipelines, traces, spans, and sampling, errors, issues, releases, and source maps, dashboards, queries, and variables, monitors, alert conditions, and notifications, slos, incidents, and burn-rate policy from Datadog to Sentry with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Hostingneeds review
DigitalOcean App Platform → Cloudflare Pages
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from DigitalOcean App Platform into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
DigitalOcean App Platform → Railway
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from DigitalOcean App Platform into Railway with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
DigitalOcean App Platform → Render
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from DigitalOcean App Platform into Render with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Communicationneeds review
Discord → Microsoft Teams
Move spaces, channels, messages, threads, users, files, private scope, apps, retention evidence, and notification operations from Discord into Microsoft Teams with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Communicationneeds review
Discord → Slack
Move an active Discord community into Slack while treating Discord history as a governed extraction, rebuilding channels and identities, copying required media, and replacing roles, bots, moderation, forums, events, and community operations.
- Elapsed
- 15–40 business days
- Active
- 70–140 hours
- Highest risk
- Critical
0 clean7 partial1 manual4 lost
Community platformsneeds review
Discourse → Circle
Move members, profiles, identities, and consent, spaces, categories, groups, and hierarchy, posts, topics, articles, and authorship, comments, replies, reactions, and mentions, images, uploads, video, and attachments, private messages and restricted content, roles, moderation, trust, bans, and permissions, courses, events, paywalls, and memberships from Discourse to Circle with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Community platformsneeds review
Discourse → Mighty Networks
Move members, profiles, identities, and consent, spaces, categories, groups, and hierarchy, posts, topics, articles, and authorship, comments, replies, reactions, and mentions, images, uploads, video, and attachments, private messages and restricted content, roles, moderation, trust, bans, and permissions, courses, events, paywalls, and memberships from Discourse to Mighty Networks with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
E-signaturesneeds review
DocuSign → Dropbox Sign
Move completed agreements and signed pdfs, certificates, audit trail, and legal evidence, templates, documents, and reusable content, recipients, roles, routing, and signing order, fields, tabs, variables, and conditional logic, identity verification and signature policy, workflows, reminders, expirations, and approvals, integrations, apis, embedded signing, and webhooks from DocuSign to Dropbox Sign with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
E-signaturesneeds review
DocuSign → PandaDoc
Move completed agreements and signed pdfs, certificates, audit trail, and legal evidence, templates, documents, and reusable content, recipients, roles, routing, and signing order, fields, tabs, variables, and conditional logic, identity verification and signature policy, workflows, reminders, expirations, and approvals, integrations, apis, embedded signing, and webhooks from DocuSign to PandaDoc with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Cloud storageneeds review
Dropbox → Box
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from Dropbox into Box with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
Dropbox → Google Drive
Move Dropbox personal and team content into Google Drive while reconciling owners, team folders, versions, sharing, links, Paper documents, native Google files, desktop sync, and compliance evidence.
- Elapsed
- 15–35 business days
- Active
- 70–130 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Cloud storageneeds review
Dropbox → OneDrive
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from Dropbox into OneDrive with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
Dropbox → SharePoint
Migration Manager copies Dropbox Business accounts into SharePoint, OneDrive, or Teams. You map identities first. A destination path cannot be edited after that task starts.
- Elapsed
- 2 to 6 weeks
- Active
- 20 to 50 hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
E-signaturesneeds review
Dropbox Sign → DocuSign
Move completed agreements and signed pdfs, certificates, audit trail, and legal evidence, templates, documents, and reusable content, recipients, roles, routing, and signing order, fields, tabs, variables, and conditional logic, identity verification and signature policy, workflows, reminders, expirations, and approvals, integrations, apis, embedded signing, and webhooks from Dropbox Sign to DocuSign with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
E-signaturesneeds review
Dropbox Sign → PandaDoc
Move completed agreements and signed pdfs, certificates, audit trail, and legal evidence, templates, documents, and reusable content, recipients, roles, routing, and signing order, fields, tabs, variables, and conditional logic, identity verification and signature policy, workflows, reminders, expirations, and approvals, integrations, apis, embedded signing, and webhooks from Dropbox Sign to PandaDoc with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Hosted searchneeds review
Elastic Cloud → Algolia
Move indexes, collections, records, and object ids, field schema and searchable attributes, text analysis, tokenization, and languages, ranking, relevance, and tie-breaking, synonyms, rules, and query rewriting, facets, filters, sorting, and replicas, query api and frontend clients, analytics, personalization, and experiments from Elastic Cloud to Algolia with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Hosted searchneeds review
Elastic Cloud → Meilisearch
Copy an Elastic Cloud index into Meilisearch with a point-in-time read, put _id on the document, and flatten nested fields. Analyzers and cluster security do not come with the documents.
- Elapsed
- 1 to 3 weeks
- Active
- 16 to 40 hours
- Highest risk
- Critical
0 clean4 partial4 manual3 lost
Hosted searchneeds review
Elastic Cloud → Typesense Cloud
Move indexes, collections, records, and object ids, field schema and searchable attributes, text analysis, tokenization, and languages, ranking, relevance, and tie-breaking, synonyms, rules, and query rewriting, facets, filters, sorting, and replicas, query api and frontend clients, analytics, personalization, and experiments from Elastic Cloud to Typesense Cloud with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Notesneeds review
Evernote → Notion
Move standard Evernote notebooks and notes into Notion while verifying tags, attachments, formatting, links, reminders, tasks, sharing, history, and editions the direct importer does not support.
- Elapsed
- 6–14 business days
- Active
- 24–44 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Notesneeds review
Evernote → Obsidian
Move Evernote notebooks, notes, tags, attachments, internal links, metadata, tasks, reminders, and OCR-dependent knowledge into a portable Obsidian vault without losing file ownership.
- Elapsed
- 6–14 business days
- Active
- 24–46 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
DNS and CDNneeds review
Fastly → Amazon Route 53
Move zones, record sets, names, and ttls, nameservers, delegation, and dnssec, traffic steering and health checks, proxy, cdn, origins, and host headers, tls certificates and security policy, caching, purge, and stale behavior, redirects, rewrites, edge logic, and headers, waf, bot, rate-limit, and access controls from Fastly to Amazon Route 53 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean1 partial8 manual1 lost
DNS and CDNneeds review
Fastly → Cloudflare DNS
Move zones, record sets, names, and ttls, nameservers, delegation, and dnssec, traffic steering and health checks, proxy, cdn, origins, and host headers, tls certificates and security policy, caching, purge, and stale behavior, redirects, rewrites, edge logic, and headers, waf, bot, rate-limit, and access controls from Fastly to Cloudflare DNS with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean1 partial8 manual1 lost
Designneeds review
Figma → Penpot
Move Figma files, components, libraries, variables, auto layout, prototypes, fonts, comments, branches, permissions, plugins, and developer handoff into Penpot through the exporter with visual and structural verification.
- Elapsed
- 20–45 business days
- Active
- 90–175 hours
- Highest risk
- Critical
0 clean10 partial1 manual1 lost
Designneeds review
Figma → Sketch
Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Figma into Sketch with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Backendneeds review
Firebase → Appwrite
Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Firebase into Appwrite with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Backendneeds review
Firebase → PostgreSQL
Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Firebase into PostgreSQL with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Backendneeds review
Firebase → Supabase
Move Firestore data, Authentication, Storage, security rules, Cloud Functions, triggers, indexes, realtime behavior, hosting dependencies, analytics hooks, and application clients into a relational Supabase architecture.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean7 partial4 manual1 lost
Authentication and identityneeds review
Firebase Authentication → Auth0
Move user profiles and stable subject ids, password hashes and hash parameters, mfa enrollments and recovery factors, social and enterprise identities, organizations, tenants, roles, and permissions, sessions, refresh tokens, and remembered devices, email, sms, and verification templates, hooks, actions, triggers, and webhooks from Firebase Authentication to Auth0 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Authentication and identityneeds review
Firebase Authentication → Clerk
Move user profiles and stable subject ids, password hashes and hash parameters, mfa enrollments and recovery factors, social and enterprise identities, organizations, tenants, roles, and permissions, sessions, refresh tokens, and remembered devices, email, sms, and verification templates, hooks, actions, triggers, and webhooks from Firebase Authentication to Clerk with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial5 manual2 lost
Hostingneeds review
Firebase Hosting → Cloudflare Pages
Move a Firebase-hosted site to Cloudflare Pages while translating build output, redirects, headers, rewrites, functions, authentication, data services, domains, previews, and rollback.
- Elapsed
- 7–15 business days
- Active
- 24–50 hours
- Highest risk
- Critical
1 clean4 partial5 manual0 lost
Hostingneeds review
Firebase Hosting → Netlify
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Firebase Hosting into Netlify with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Firebase Hosting → Vercel
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Firebase Hosting into Vercel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
ELT and data integrationneeds review
Fivetran → Airbyte
Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Fivetran to Airbyte with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial6 manual2 lost
ELT and data integrationneeds review
Fivetran → Stitch
Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Fivetran to Stitch with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial6 manual2 lost
Hostingneeds review
Fly.io → Railway
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Fly.io into Railway with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Fly.io → Render
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Fly.io into Render with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Publishingneeds review
Framer → Webflow
Rebuild a Framer site in Webflow. Export each Framer CMS collection with a plugin as CSV or JSON, then import into Webflow collections. Framer says published output is HTML, CSS, JavaScript, and assets you can download. That download is not a Webflow project. Forms and interactions are a rebuild.
- Elapsed
- 12–30 business days
- Active
- 50–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Publishingneeds review
Framer → WordPress
Move Framer CMS collections into WordPress with plugin CSV exports, then rebuild the design as a theme. Framer has no site export WordPress can import. Re-host images. Recreate redirects. Keep Framer live until WordPress no longer loads Framer URLs.
- Elapsed
- 12–28 business days
- Active
- 45–100 hours
- Highest risk
- Critical
0 clean4 partial6 manual2 lost
Accounting and invoicingneeds review
FreshBooks → QuickBooks Online
Move chart of accounts and tracking dimensions, customers, suppliers, and contact identity, invoices, bills, credits, and payments, bank accounts, feeds, and reconciliation, products, services, inventory, and cost, tax rates, returns, and jurisdiction settings, payroll, expenses, projects, and time, attachments, templates, and communications from FreshBooks to QuickBooks Online with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Accounting and invoicingneeds review
FreshBooks → Xero
Move chart of accounts and tracking dimensions, customers, suppliers, and contact identity, invoices, bills, credits, and payments, bank accounts, feeds, and reconciliation, products, services, inventory, and cost, tax rates, returns, and jurisdiction settings, payroll, expenses, projects, and time, attachments, templates, and communications from FreshBooks to Xero with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Customer supportneeds review
Freshdesk → Help Scout
Import Freshdesk tickets and customer profiles into Help Scout with Import2 after users and inboxes exist. Open becomes Active, and Resolved or Closed becomes Closed. The knowledge base, rules, and canned replies stay behind.
- Elapsed
- 1 to 3 weeks
- Active
- 12 to 24 hours
- Highest risk
- Critical
1 clean2 partial6 manual1 lost
Customer supportneeds review
Freshdesk → Intercom
Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Freshdesk to Intercom with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Customer supportneeds review
Freshdesk → Zendesk
Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Freshdesk to Zendesk with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Publishingneeds review
Ghost → Astro
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Ghost into Astro with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Newsletterneeds review
Ghost → Beehiiv
Move a Ghost publication to Beehiiv with the first-party Content Import and subscriber CSV. Temporarily un-paywall posts because Ghost's Content API only returns public content. Map paid Stripe subscriptions, then pause Ghost billing so nobody is charged twice.
- Elapsed
- 8–16 business days
- Active
- 22–44 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
CMSneeds review
Ghost → Sanity
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Ghost into Sanity with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Newsletterneeds review
Ghost → Substack
Move Ghost posts, members, and Stripe-paid subscriptions onto Substack without sending the list twice or leaving images and redirects on the old host.
- Elapsed
- 5–10 calendar days before first full send
- Active
- 10–18 hours
- Highest risk
- Critical
0 clean6 partial3 manual2 lost
Publishingneeds review
Ghost → Webflow
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Ghost into Webflow with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Publishingneeds review
Ghost → WordPress
Move Ghost content, members, themes, media, URLs, newsletters, and Stripe-linked access into WordPress without losing paid-reader state or publishing history.
- Elapsed
- 10–20 business days
- Active
- 40–72 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Code hostingneeds review
GitHub → Azure DevOps
Import a GitHub repo into Azure Repos with a clone URL. You get commits, branches, tags, and files. Issues, pull request discussion, Actions secrets, and pipeline history stay in GitHub.
- Elapsed
- 3 to 10 days
- Active
- 10 to 24 hours
- Highest risk
- Critical
0 clean2 partial6 manual3 lost
Code hostingneeds review
GitHub → Bitbucket
Move GitHub repositories and Git history into Bitbucket while rebuilding pull requests, issues, Actions, releases, packages, projects, rules, permissions, webhooks, and deployment operations that its repository importer does not carry.
- Elapsed
- 12–24 business days
- Active
- 55–100 hours
- Highest risk
- Critical
2 clean6 partial2 manual2 lost
Developmentagent reviewed
GitHub → GitLab
Move repositories and collaboration history from GitHub to GitLab with explicit handling for identities, LFS, attachments, CI/CD, protections, integrations, secrets, package registries, cutover, and mirror-based rollback.
- Elapsed
- Editorial estimate: 15–30 business days
- Active
- Editorial estimate: 70–130 active hours
- Highest risk
- Critical
1 clean7 partial4 manual2 lost
CI/CDneeds review
GitHub Actions → GitLab
Move pipelines, jobs, runners, secrets, triggers, artifacts, environments, approvals, notifications, and release operations from GitHub Actions into GitLab with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–120 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
CI/CDneeds review
GitHub Actions → Jenkins
Move pipelines, jobs, runners, secrets, triggers, artifacts, environments, approvals, notifications, and release operations from GitHub Actions into Jenkins with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–120 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Project managementneeds review
GitHub Issues → Jira
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from GitHub Issues into Jira with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
GitHub Issues → Linear
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from GitHub Issues into Linear with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Hostingneeds review
GitHub Pages → Azure Static Web Apps
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from GitHub Pages into Azure Static Web Apps with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
GitHub Pages → Cloudflare Pages
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from GitHub Pages into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
GitHub Pages → Netlify
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from GitHub Pages into Netlify with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Code hostingneeds review
GitLab → Azure DevOps
Move repositories, refs, pull requests, issues, users, LFS, pipelines, packages, permissions, webhooks, and audit evidence from GitLab into Azure DevOps with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
1 clean8 partial3 manual0 lost
Code hostingneeds review
GitLab → Bitbucket
Move repositories, refs, pull requests, issues, users, LFS, pipelines, packages, permissions, webhooks, and audit evidence from GitLab into Bitbucket with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
1 clean8 partial3 manual0 lost
Code hostingneeds review
GitLab → GitHub
Move GitLab repositories, Git history, merge requests, issues, users, releases, LFS objects, packages, CI pipelines, groups, permissions, and integrations into GitHub with a documented fidelity choice.
- Elapsed
- 15–30 business days
- Active
- 70–130 hours
- Highest risk
- Critical
2 clean8 partial2 manual0 lost
CI/CDneeds review
GitLab → GitHub Actions
Move GitLab CI pipelines, jobs, runners, variables, schedules, artifacts, environments, and release operations into GitHub Actions without treating an importer pull request as a finished cutover.
- Elapsed
- 15–40 business days
- Active
- 60–140 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Hostingneeds review
GitLab Pages → Cloudflare Pages
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from GitLab Pages into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
GitLab Pages → Netlify
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from GitLab Pages into Netlify with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Analyticsneeds review
Google Analytics → Matomo
Replace Google Analytics with Matomo while importing available historical reports, rebuilding collection and goals, handling API limits, and documenting unavoidable metric and report differences.
- Elapsed
- 12–30 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean6 partial3 manual3 lost
Analyticsneeds review
Google Analytics → Plausible
Replace Google Analytics with Plausible while preserving useful aggregate history, rebuilding goals and ecommerce measurement, documenting metric breaks, and validating a parallel collection period.
- Elapsed
- 10–20 business days
- Active
- 36–68 hours
- Highest risk
- Critical
0 clean6 partial2 manual4 lost
Analyticsneeds review
Google Analytics 4 → Amplitude
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Google Analytics 4 into Amplitude with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Google Analytics 4 → Matomo
Import GA4 reports into a new Matomo site, then track there. The import cannot be merged into a site you already created, and it is aggregated history, not the raw visits.
- Elapsed
- 1 to 3 weeks
- Active
- 8 to 20 hours
- Highest risk
- Critical
1 clean6 partial2 manual3 lost
Analyticsneeds review
Google Analytics 4 → Mixpanel
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Google Analytics 4 into Mixpanel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Google Analytics 4 → Plausible
Replace GA4 collection with Plausible, import day-level history through the official GA4 importer, rebuild goals, and treat the two datasets as different counting methods rather than a match.
- Elapsed
- 15–30 business days
- Active
- 36–70 hours
- Highest risk
- Critical
0 clean5 partial2 manual4 lost
Analyticsneeds review
Google Analytics 4 → PostHog
Move GA4 events, identities, properties, conversions, consent, collection, and historical evidence into PostHog with a BigQuery export, a schema map, and a labeled historical import.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Data warehousesneeds review
Google BigQuery → Amazon Redshift
Move databases, schemas, tables, and rows, data types, precision, nulls, and time zones, views, materialized views, and sql dialect, primary keys, constraints, and data quality, users, roles, grants, row and column policy, pipelines, stages, external tables, and file formats, scheduled queries, tasks, procedures, and udfs, bi, dbt, notebooks, and downstream consumers from Google BigQuery to Amazon Redshift with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial7 manual1 lost
Data warehousesneeds review
Google BigQuery → Snowflake
Move databases, schemas, tables, and rows, data types, precision, nulls, and time zones, views, materialized views, and sql dialect, primary keys, constraints, and data quality, users, roles, grants, row and column policy, pipelines, stages, external tables, and file formats, scheduled queries, tasks, procedures, and udfs, bi, dbt, notebooks, and downstream consumers from Google BigQuery to Snowflake with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial7 manual1 lost
Documentationneeds review
Google Docs → Notion
Move selected Google Docs into Notion while preserving readable content and media and explicitly archiving comments, suggestions, revisions, permissions, folder hierarchy, scripts, and advanced layouts.
- Elapsed
- 8–18 business days
- Active
- 32–60 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Knowledgeneeds review
Google Docs → Obsidian
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Google Docs into Obsidian with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
Google Drive → Box
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from Google Drive into Box with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Storageagent reviewed
Google Drive → Dropbox
Move files from Google Drive to Dropbox with an explicit plan for native Google formats, shared drives, permissions, versions, links, ownership, and a reversible period with no destructive source deletion.
- Elapsed
- Editorial estimate: 15–30 business days
- Active
- Editorial estimate: 45–80 active hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Cloud storageneeds review
Google Drive → OneDrive
Move Google Drive users and shared content into OneDrive and SharePoint while converting Google-native files, ownership, permissions, shortcuts, versions, links, scripts, and embedded dependencies.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean9 partial1 manual2 lost
Databasesneeds review
Google Sheets → Airtable
Airtable can import a Google Sheet into a new or existing table. The copy does not stay in sync, and a CSV merge is a separate extension with a 25,000 row cap.
- Elapsed
- 3 to 10 business days
- Active
- 8 to 24 hours
- Highest risk
- Critical
1 clean4 partial5 manual2 lost
Knowledgeneeds review
Google Sheets → Notion
Download the sheet as CSV and import it as a Notion database. The import adds rows. It does not update them, and it does not create relations, rollups, or formulas.
- Elapsed
- 3 to 10 business days
- Active
- 8 to 24 hours
- Highest risk
- Critical
1 clean5 partial4 manual2 lost
Office suitesneeds review
Google Workspace → Microsoft 365
Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Google Workspace to Microsoft 365 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean7 partial3 manual0 lost
Office suitesneeds review
Google Workspace → Zoho Workplace
Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Google Workspace to Zoho Workplace with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean7 partial3 manual0 lost
Commerceneeds review
Gumroad → Lemon Squeezy
Move Gumroad digital products, files, buyers, subscribers, memberships, licenses, discounts, posts, receipts, analytics, tax records, and integrations into Lemon Squeezy with an explicit re-subscription and entitlement plan.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Commerceneeds review
Gumroad → Polar
Move Gumroad products, files, buyers, memberships, licenses, discounts, posts, tax history, and integrations into Polar while separating customer and entitlement creation from unsupported self-service active-subscription transfer.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Customer supportneeds review
Help Scout → Freshdesk
Load Help Scout customers with Freshdesk's contact CSV, then create tickets through the API. Help Scout will not export thread text from the report screens, and Freshdesk's ticket create rate depends on the plan.
- Elapsed
- 2 to 4 weeks
- Active
- 20 to 40 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Customer supportneeds review
Help Scout → Zendesk
Export Help Scout conversations through the Inbox API, then create them with Zendesk's ticket import so closed history can go straight to the archive. In-app reports do not include thread text.
- Elapsed
- 2 to 4 weeks
- Active
- 20 to 40 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Hostingneeds review
Heroku → DigitalOcean App Platform
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Heroku into DigitalOcean App Platform with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Heroku → Fly.io
Move Heroku web and worker processes, configuration, Postgres, Redis, domains, add-ons, releases, schedules, logs, and traffic into Fly.io Machines with explicit container and regional operations.
- Elapsed
- 8–20 business days
- Active
- 40–78 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Databasesneeds review
Heroku → Neon
Copy a Heroku Postgres database into Neon with a backup and pg_restore. Neon's Import Data Assistant refuses Heroku, and pg:pull is not the same command in both docs.
- Elapsed
- 3 to 10 business days
- Active
- 10 to 30 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
Hostingneeds review
Heroku → Railway
Move a Heroku application to Railway with explicit handling for process types, databases, add-ons, variables, storage, jobs, domains, observability, deployment behavior, and rollback.
- Elapsed
- 10–20 business days
- Active
- 35–70 hours
- Highest risk
- Critical
1 clean3 partial3 manual3 lost
Hostingneeds review
Heroku → Render
Move Heroku apps, dynos, config vars, Postgres, key-value stores, workers, schedulers, domains, add-ons, release commands, logs, and traffic into Render with a rehearsed data cutover.
- Elapsed
- 8–18 business days
- Active
- 38–70 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Hostingneeds review
Heroku → Vercel
Move Heroku web dynos, config vars, Postgres, workers, schedulers, release commands, add-ons, domains, and traffic into Vercel Functions without treating a git deploy as a complete cutover.
- Elapsed
- 8–18 business days
- Active
- 38–70 hours
- Highest risk
- Critical
1 clean5 partial5 manual1 lost
CRMneeds review
HubSpot → ActiveCampaign
Move HubSpot contacts into ActiveCampaign with a cleaned CSV. HubSpot has about 200 standard contact properties. ActiveCampaign starts with six default fields. Workflows, behavioral history, and HubSpot reports do not import. Rebuild automations, then run both sides for a full sales cycle before you cancel HubSpot.
- Elapsed
- 10–25 business days
- Active
- 40–90 hours
- Highest risk
- Critical
0 clean3 partial6 manual3 lost
CRMneeds review
HubSpot → Airtable
Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from HubSpot into Airtable with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–160 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
CRMneeds review
HubSpot → Pipedrive
Move HubSpot companies, contacts, and deals into Pipedrive organizations, people, and deals. Marketing email and tickets can stay in HubSpot. A second import of the same spreadsheet is how duplicates get created.
- Elapsed
- 12–30 business days
- Active
- 35–80 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
CRMneeds review
HubSpot → Salesforce
Move HubSpot contacts, companies, deals, tickets, activities, owners, files, associations, properties, workflows, and integrations into Salesforce with controlled record identity.
- Elapsed
- 20–40 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
CRMneeds review
HubSpot → Zoho CRM
Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from HubSpot into Zoho CRM with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–160 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Status pagesneeds review
Instatus → Atlassian Statuspage
Move pages, domains, branding, and localization, components, groups, and current status, incidents, updates, and postmortems, scheduled maintenance and recurrence, subscribers and notification preferences, incident templates and communication policy, monitors, automation, and component mapping, apis, embeds, rss, and third-party components from Instatus to Atlassian Statuspage with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Status pagesneeds review
Instatus → Better Stack
Move pages, domains, branding, and localization, components, groups, and current status, incidents, updates, and postmortems, scheduled maintenance and recurrence, subscribers and notification preferences, incident templates and communication policy, monitors, automation, and component mapping, apis, embeds, rss, and third-party components from Instatus to Better Stack with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Customer supportneeds review
Intercom → Freshdesk
Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Intercom to Freshdesk with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Customer supportneeds review
Intercom → Help Scout
Import Intercom conversations into Help Scout with Import2 after users and inboxes exist. Snoozed conversations do not stay snoozed, and Help Scout's own docs say chat volume can drop because Beacon only chats when someone is available.
- Elapsed
- 1 to 3 weeks
- Active
- 12 to 24 hours
- Highest risk
- High
0 clean4 partial5 manual1 lost
Customer supportneeds review
Intercom → Zendesk
Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Intercom to Zendesk with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
CI/CDneeds review
Jenkins → CircleCI
Move Jenkins freestyle jobs and Jenkinsfiles onto CircleCI. Copy Execute Shell steps into .circleci/config.yml first. Then replace plugins, agents, credentials, and approvals with CircleCI jobs, orbs, contexts, and self-hosted runners.
- Elapsed
- 15–35 business days
- Active
- 60–130 hours
- Highest risk
- Critical
0 clean4 partial6 manual2 lost
CI/CDneeds review
Jenkins → GitHub Actions
Move Jenkins controllers, jobs, Jenkinsfiles, agents, credentials, plugins, triggers, artifacts, approvals, environments, notifications, and release operations into GitHub Actions with auditable workflow parity.
- Elapsed
- 15–35 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
CI/CDneeds review
Jenkins → GitLab
Move pipelines, jobs, runners, secrets, triggers, artifacts, environments, approvals, notifications, and release operations from Jenkins into GitLab with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–120 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Project managementneeds review
Jira → Asana
Move Jira issues, statuses, assignees, comments, attachments, and hierarchy into Asana without treating the 150-issue Cloud importer as a complete cutover.
- Elapsed
- 15–35 business days
- Active
- 55–120 hours
- Highest risk
- Critical
0 clean6 partial3 manual2 lost
Project managementneeds review
Jira → ClickUp
Move Jira issues, epics, comments, attachments, and users into ClickUp with a Cloud backup zip, without treating the importer as a complete copy of priority, time logs, or private comments.
- Elapsed
- 15–35 business days
- Active
- 55–130 hours
- Highest risk
- Critical
0 clean7 partial1 manual3 lost
Project managementneeds review
Jira → GitHub Issues
Move selected Jira issues, comments, users, labels, priorities, relationships, attachments, and active delivery work into GitHub Issues with explicit handling for projects, boards, sprints, worklogs, and automation.
- Elapsed
- 12–24 business days
- Active
- 50–90 hours
- Highest risk
- Critical
0 clean10 partial2 manual0 lost
Project managementneeds review
Jira → Linear
Move Jira issues and epics to Linear with a clear choice between one-time import and transition sync, while handling workflows, identities, custom fields, hierarchy, comments, attachments, automation, and rollback.
- Elapsed
- 15–30 business days
- Active
- 60–105 hours
- Highest risk
- Critical
1 clean7 partial1 manual1 lost
Forms and surveysneeds review
Jotform → Tally
Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Jotform to Tally with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Forms and surveysneeds review
Jotform → Typeform
Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Jotform to Typeform with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Course platformsneeds review
Kajabi → Teachable
Move courses, products, modules, and lessons, video, audio, pdfs, downloads, and embeds, students, profiles, and consent, enrollments, access, progress, and completion, quizzes, assignments, surveys, and certificates, offers, pricing, coupons, subscriptions, and tax, websites, sales pages, blogs, and domains, email, funnels, automations, and affiliates from Kajabi to Teachable with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Course platformsneeds review
Kajabi → Thinkific
Move courses, products, modules, and lessons, video, audio, pdfs, downloads, and embeds, students, profiles, and consent, enrollments, access, progress, and completion, quizzes, assignments, surveys, and certificates, offers, pricing, coupons, subscriptions, and tax, websites, sales pages, blogs, and domains, email, funnels, automations, and affiliates from Kajabi to Thinkific with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Newslettersagent reviewed
Kit → Beehiiv
Move subscribers, consent evidence, fields, tags, sending identity, forms, automations, and publication operations from Kit to Beehiiv without double-sending or silently dropping paid readers.
- Elapsed
- 8–15 business days
- Active
- 24–42 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Newsletterneeds review
Kit → Ghost
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Kit into Ghost with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newsletterneeds review
Kit → Substack
Move a Kit list and archive to Substack. Export subscribers as CSV. Import posts with Substack's importer or Kit's RSS, which may only include recent posts. Rebuild sequences, tags, and paid billing. Warm the new sending domain before the first blast.
- Elapsed
- 8–16 business days
- Active
- 20–40 hours
- Highest risk
- Critical
0 clean4 partial6 manual2 lost
Newsletterneeds review
Klaviyo → ActiveCampaign
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Klaviyo into ActiveCampaign with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newsletterneeds review
Klaviyo → Kit
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Klaviyo into Kit with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newsletterneeds review
Klaviyo → Mailchimp
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Klaviyo into Mailchimp with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Securityagent reviewed
LastPass → 1Password
Move personal and shared vault data from LastPass to 1Password with strict plaintext-export handling, shared-folder permission mapping, passkey and OTP exceptions, credential rotation, cutover, rollback, and evidence that nothing sensitive was left behind.
- Elapsed
- 15–30 business days
- Active
- 65–110 hours
- Highest risk
- Critical
1 clean8 partial0 manual4 lost
Password managersneeds review
LastPass → Bitwarden
Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from LastPass into Bitwarden with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Password managersneeds review
LastPass → Dashlane
Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from LastPass into Dashlane with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Paymentsneeds review
Lemon Squeezy → Polar
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Lemon Squeezy into Polar with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Paymentsneeds review
Lemon Squeezy → Stripe Billing
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Lemon Squeezy into Stripe Billing with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Project managementneeds review
Linear → Asana
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Linear into Asana with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
Linear → GitHub Issues
Move Linear issues, comments, labels, cycles, and projects into GitHub Issues and Projects without treating a CSV download as a finished tracker.
- Elapsed
- 10–22 business days
- Active
- 40–85 hours
- Highest risk
- Critical
0 clean6 partial2 manual3 lost
Project managementneeds review
Linear → Jira
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Linear into Jira with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Commerceneeds review
Magento → Shopify
Move a Magento or Adobe Commerce catalog to Shopify with product and customer CSVs, then orders through an app or the Order API. Themes, checkout code, and price rules stay behind.
- Elapsed
- 4 to 10 weeks
- Active
- 40 to 80 hours
- Highest risk
- Critical
0 clean4 partial6 manual1 lost
Commerceneeds review
Magento → WooCommerce
Move Magento 2 products, customers, and orders into WooCommerce. The official extension talks to the Magento API and does not import passwords. Configurable products and URL maps need a pilot.
- Elapsed
- 2 to 6 weeks
- Active
- 30 to 60 hours
- Highest risk
- Critical
0 clean6 partial3 manual2 lost
Newsletterneeds review
Mailchimp → ActiveCampaign
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Mailchimp into ActiveCampaign with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newslettersneeds review
Mailchimp → Beehiiv
Move an audience, newsletter archive, fields, segments, forms, automations, sending identity, and consent evidence from Mailchimp to Beehiiv without reactivating suppressed contacts or sending twice.
- Elapsed
- 8–15 business days
- Active
- 24–40 hours
- Highest risk
- Critical
1 clean4 partial4 manual1 lost
Newsletterneeds review
Mailchimp → Ghost
Move a Mailchimp audience into Ghost members with the built-in migrator or a member CSV. Campaign content does not come across, and people who are already Ghost members keep their old newsletter preferences.
- Elapsed
- 4 to 10 days
- Active
- 8 to 16 hours
- Highest risk
- Critical
0 clean3 partial3 manual4 lost
Newsletterneeds review
Mailchimp → HubSpot
Move Mailchimp audiences, suppressions, fields, and templates into HubSpot with audience CSVs and an opt-out import, without treating the native Mailchimp app as a reverse sync or a copy of automations.
- Elapsed
- 15–35 business days
- Active
- 50–120 hours
- Highest risk
- Critical
0 clean6 partial2 manual3 lost
Newslettersneeds review
Mailchimp → Kit
Move Mailchimp contacts, custom fields, tags, interests, forms, templates, campaigns, automations, and sending identity into Kit without reactivating inactive addresses.
- Elapsed
- 7–14 business days
- Active
- 26–46 hours
- Highest risk
- Critical
1 clean5 partial5 manual1 lost
Newsletterneeds review
Mailchimp → Klaviyo
Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from Mailchimp into Klaviyo with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–70 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Newslettersneeds review
Mailchimp → Substack
Move a consented Mailchimp audience and newsletter operation into Substack while preserving suppression evidence and rebuilding segments, automations, forms, archives, and sender expectations.
- Elapsed
- 6–12 business days
- Active
- 22–38 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Transactional emailneeds review
Mailgun → Postmark
Move sending domains and sender identities, spf, dkim, and dmarc alignment, suppressions, bounces, complaints, and unsubscribes, templates, versions, and layouts, api payloads and provider sdks, webhooks and event semantics, dedicated ips and warm-up state, inbound email routes from Mailgun to Postmark with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Transactional emailneeds review
Mailgun → Resend
Verify a Resend domain, point the app at the new API or SMTP host, and decide what to do with Mailgun suppressions. Resend suppressions are team-wide. A Mailgun unsubscribe on one domain is not the same thing.
- Elapsed
- 8–18 business days
- Active
- 24–50 hours
- Highest risk
- Critical
0 clean2 partial8 manual2 lost
Transactional emailneeds review
Mailgun → SendGrid
Move sending domains and sender identities, spf, dkim, and dmarc alignment, suppressions, bounces, complaints, and unsubscribes, templates, versions, and layouts, api payloads and provider sdks, webhooks and event semantics, dedicated ips and warm-up state, inbound email routes from Mailgun to SendGrid with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Workflow automationneeds review
Make → n8n
Move workflow graph and step order, app connectors and operation coverage, credentials and oauth connections, field mappings and expressions, schedules, polling, and webhook triggers, error handling, retries, and partial execution, data stores, variables, and shared components, execution history and replay evidence from Make to n8n with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Workflow automationneeds review
Make → Zapier
Move workflow graph and step order, app connectors and operation coverage, credentials and oauth connections, field mappings and expressions, schedules, polling, and webhook triggers, error handling, retries, and partial execution, data stores, variables, and shared components, execution history and replay evidence from Make to Zapier with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Analyticsneeds review
Matomo → Google Analytics
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Matomo into Google Analytics with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Matomo → Plausible
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Matomo into Plausible with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Communicationneeds review
Mattermost → Microsoft Teams
Move spaces, channels, messages, threads, users, files, private scope, apps, retention evidence, and notification operations from Mattermost into Microsoft Teams with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Communicationneeds review
Mattermost → Slack
Move spaces, channels, messages, threads, users, files, private scope, apps, retention evidence, and notification operations from Mattermost into Slack with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Publishingneeds review
Medium → Ghost
Move a Medium profile or publication into Ghost while preserving articles, canonical intent, images, authorship, members, URLs, and evidence for engagement that cannot transfer.
- Elapsed
- 6–12 business days
- Active
- 24–42 hours
- Highest risk
- Critical
0 clean6 partial3 manual3 lost
Newsletterneeds review
Medium → Substack
Move Medium stories into Substack with the URL importer, then bring a consented email list separately. Medium followers are not a mailing list. Imported posts publish immediately and often keep Medium chrome at the bottom.
- Elapsed
- 5–12 calendar days before first full send
- Active
- 10–20 hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Publishingneeds review
Medium → WordPress
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Medium into WordPress with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
Hosted searchneeds review
Meilisearch → Elastic Cloud
Move a Meilisearch index to Elastic Cloud when you need mappings, bulk updates, or aggregations Meilisearch is not covering. Define the mapping first. A 2023 report of indexing lag is a workload to retest, not a current benchmark.
- Elapsed
- 12–28 business days
- Active
- 40–90 hours
- Highest risk
- Critical
0 clean5 partial7 manual0 lost
Hosted searchneeds review
Meilisearch → Typesense Cloud
Typesense Cloud needs a typed collection before the first document. Meilisearch does not. Define the schema, import from the database that feeds search, and shadow queries before you turn Meilisearch off.
- Elapsed
- 10–24 business days
- Active
- 30–70 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Office suitesneeds review
Microsoft 365 → Google Workspace
Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Microsoft 365 to Google Workspace with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean7 partial3 manual0 lost
Office suitesneeds review
Microsoft 365 → Zoho Workplace
Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Microsoft 365 to Zoho Workplace with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean7 partial3 manual0 lost
Communicationneeds review
Microsoft Teams → Discord
Move spaces, channels, messages, threads, users, files, private scope, apps, retention evidence, and notification operations from Microsoft Teams into Discord with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial0 manual4 lost
Communicationneeds review
Microsoft Teams → Slack
Move Microsoft Teams collaboration into Slack while separately handling lawful message exports, users, channels, SharePoint and OneDrive files, meetings, apps, workflows, guests, retention, and compliance evidence.
- Elapsed
- 20–45 business days
- Active
- 85–165 hours
- Highest risk
- Critical
0 clean7 partial2 manual3 lost
Community platformsneeds review
Mighty Networks → Circle
Move members, profiles, identities, and consent, spaces, categories, groups, and hierarchy, posts, topics, articles, and authorship, comments, replies, reactions, and mentions, images, uploads, video, and attachments, private messages and restricted content, roles, moderation, trust, bans, and permissions, courses, events, paywalls, and memberships from Mighty Networks to Circle with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Community platformsneeds review
Mighty Networks → Discourse
Move members, profiles, identities, and consent, spaces, categories, groups, and hierarchy, posts, topics, articles, and authorship, comments, replies, reactions, and mentions, images, uploads, video, and attachments, private messages and restricted content, roles, moderation, trust, bans, and permissions, courses, events, paywalls, and memberships from Mighty Networks to Discourse with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Analyticsneeds review
Mixpanel → Amplitude
Move Mixpanel historical events and live instrumentation into Amplitude while preserving taxonomy intent, identities, properties, groups, revenue, governance, dashboards, and downstream data ownership.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean6 partial3 manual3 lost
Analyticsneeds review
Mixpanel → Google Analytics 4
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Mixpanel into Google Analytics 4 with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Mixpanel → PostHog
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Mixpanel into PostHog with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Project managementneeds review
monday.com → Asana
Move monday.com boards and active work into Asana using controlled Excel and CSV transforms while preserving an archive for updates, dashboards, formulas, automations, apps, and board permissions.
- Elapsed
- 8–16 business days
- Active
- 30–56 hours
- Highest risk
- Critical
0 clean10 partial0 manual2 lost
Project managementneeds review
monday.com → ClickUp
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from monday.com into ClickUp with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
monday.com → Jira
Move a monday.com board into a new Jira software or business space with Atlassian's monday importer. Groups can become status, epic, or category. Items become work items. Subitems become subtasks. The importer will not recreate monday's grouped spreadsheet look.
- Elapsed
- 8–18 business days
- Active
- 30–65 hours
- Highest risk
- Critical
0 clean7 partial2 manual3 lost
Project managementneeds review
monday.com → Linear
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from monday.com into Linear with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial1 manual2 lost
Databasesneeds review
MongoDB → MySQL
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from MongoDB into MySQL with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Databasesneeds review
MongoDB → PostgreSQL
Move MongoDB documents into PostgreSQL while designing a relational or JSONB model, preserving BSON types and IDs, rebuilding references, indexes, validation, transactions, change streams, application queries, and recovery.
- Elapsed
- 30–75 business days
- Active
- 160–320 hours
- Highest risk
- Critical
0 clean6 partial5 manual1 lost
Backendneeds review
MongoDB → Supabase
Move MongoDB documents, users, files, queries, and application access into Supabase Postgres, Auth, Storage, and Row Level Security without treating a JSON dump as a finished backend.
- Elapsed
- 20–45 business days
- Active
- 90–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Databasesneeds review
MySQL → MongoDB
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from MySQL into MongoDB with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Databasesneeds review
MySQL → PlanetScale
Import an internet-facing MySQL 5.6, 5.7, or 8.0 database into PlanetScale Vitess with an external keyspace and MoveTables. Foreign keys, missing unique keys, and DDL during the copy change the command you run.
- Elapsed
- 3 to 10 days
- Active
- 10 to 24 hours
- Highest risk
- Critical
0 clean5 partial6 manual0 lost
Databasesneeds review
MySQL → PostgreSQL
Move a production MySQL database into PostgreSQL while translating schemas, types, identifiers, SQL, constraints, indexes, views, procedures, users, application behavior, replication, performance, and recovery.
- Elapsed
- 25–60 business days
- Active
- 130–260 hours
- Highest risk
- Critical
0 clean5 partial7 manual0 lost
Workflow automationneeds review
n8n → Make
Move workflow graph and step order, app connectors and operation coverage, credentials and oauth connections, field mappings and expressions, schedules, polling, and webhook triggers, error handling, retries, and partial execution, data stores, variables, and shared components, execution history and replay evidence from n8n to Make with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Workflow automationneeds review
n8n → Zapier
Move workflow graph and step order, app connectors and operation coverage, credentials and oauth connections, field mappings and expressions, schedules, polling, and webhook triggers, error handling, retries, and partial execution, data stores, variables, and shared components, execution history and replay evidence from n8n to Zapier with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Databasesneeds review
Neon → PostgreSQL
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from Neon into PostgreSQL with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Databasesneeds review
Neon → Supabase
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from Neon into Supabase with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Hostingneeds review
Netlify → Cloudflare Pages
Move a Netlify project to Cloudflare Pages while translating builds, environment values, redirects, headers, forms, functions, domains, access, and a measured rollback path.
- Elapsed
- 5–12 calendar days
- Active
- 12–24 hours
- Highest risk
- Critical
2 clean4 partial4 manual5 lost
Hostingneeds review
Netlify → Render
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Netlify into Render with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Netlify → Vercel
Move a Netlify application into Vercel while translating netlify.toml, build contexts, environment variables, redirects, headers, Functions, Edge Functions, Forms, Identity, Blobs, domains, analytics, and deploy operations.
- Elapsed
- 8–18 business days
- Active
- 36–72 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Observability and error trackingneeds review
New Relic → Datadog
Move applications, services, and entity identity, metrics and metric types, logs, parsing, and pipelines, traces, spans, and sampling, errors, issues, releases, and source maps, dashboards, queries, and variables, monitors, alert conditions, and notifications, slos, incidents, and burn-rate policy from New Relic to Datadog with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Observability and error trackingneeds review
New Relic → Sentry
Move applications, services, and entity identity, metrics and metric types, logs, parsing, and pipelines, traces, spans, and sampling, errors, issues, releases, and source maps, dashboards, queries, and variables, monitors, alert conditions, and notifications, slos, incidents, and burn-rate policy from New Relic to Sentry with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Knowledgeneeds review
Notion → Coda
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Notion into Coda with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Documentationneeds review
Notion → Confluence
Move Notion pages, users, workspaces, attachments, databases, comments, links, and permissions into Confluence while separating portable knowledge from Notion-specific application behavior.
- Elapsed
- 10–22 business days
- Active
- 42–78 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Knowledgeneeds review
Notion → Evernote
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Notion into Evernote with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Knowledgeneeds review
Notion → Google Docs
Notion's workspace export is HTML or Markdown and CSV, and the download link lasts 7 days. Google Drive's convert setting is documented for Word files, not for a Notion zip.
- Elapsed
- 1 to 4 weeks
- Active
- 15 to 40 hours
- Highest risk
- Critical
0 clean4 partial4 manual4 lost
Knowledgeneeds review
Notion → Obsidian
Move a Notion workspace into a local Obsidian vault while preserving page content, attachments, links, database meaning, ownership decisions, and a testable archive of what cannot become plain files.
- Elapsed
- 7–14 business days
- Active
- 28–48 hours
- Highest risk
- Critical
1 clean5 partial0 manual6 lost
Knowledgeneeds review
Obsidian → Coda
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Obsidian into Coda with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Knowledgeneeds review
Obsidian → Notion
Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Obsidian into Notion with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 10–25 business days
- Active
- 45–90 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Cloud storageneeds review
OneDrive → Dropbox
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from OneDrive into Dropbox with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
OneDrive → Google Drive
Move OneDrive business files into Google Drive while mapping identities, My Drive and shared drives, Microsoft-native collaboration, versions, permissions, links, retention, and connected Microsoft 365 workflows.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean9 partial1 manual2 lost
Cloud storageneeds review
OneDrive → SharePoint
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from OneDrive into SharePoint with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Infrastructure as codeneeds review
OpenTofu → Pulumi
Move configuration source and language, state, resource addresses, and provider ids, providers, resources, and schema versions, modules, components, and reusable libraries, backends, locking, encryption, and history, secrets, variables, configuration, and environments, imports, moves, aliases, and replacements, plans, previews, policy, and approvals from OpenTofu to Pulumi with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Infrastructure as codeneeds review
OpenTofu → Terraform
Move configuration source and language, state, resource addresses, and provider ids, providers, resources, and schema versions, modules, components, and reusable libraries, backends, locking, encryption, and history, secrets, variables, configuration, and environments, imports, moves, aliases, and replacements, plans, previews, policy, and approvals from OpenTofu to Terraform with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Paymentsneeds review
Paddle → Polar
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Paddle into Polar with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Paymentsneeds review
Paddle → Stripe Billing
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Paddle into Stripe Billing with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
E-signaturesneeds review
PandaDoc → DocuSign
Move completed agreements and signed pdfs, certificates, audit trail, and legal evidence, templates, documents, and reusable content, recipients, roles, routing, and signing order, fields, tabs, variables, and conditional logic, identity verification and signature policy, workflows, reminders, expirations, and approvals, integrations, apis, embedded signing, and webhooks from PandaDoc to DocuSign with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
E-signaturesneeds review
PandaDoc → Dropbox Sign
Move completed agreements and signed pdfs, certificates, audit trail, and legal evidence, templates, documents, and reusable content, recipients, roles, routing, and signing order, fields, tabs, variables, and conditional logic, identity verification and signature policy, workflows, reminders, expirations, and approvals, integrations, apis, embedded signing, and webhooks from PandaDoc to Dropbox Sign with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Designneeds review
Penpot → Figma
Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Penpot into Figma with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Designneeds review
Penpot → Sketch
Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Penpot into Sketch with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Vector databasesneeds review
Pinecone → Qdrant
Move indexes, collections, classes, and namespaces, vector ids, dimensions, and numeric values, payload, metadata, properties, and schema, distance metric and score semantics, filtering, hybrid search, and sparse vectors, embeddings and source text provenance, backups, snapshots, restore, and re-indexing, tenancy, authentication, and authorization from Pinecone to Qdrant with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual0 lost
Vector databasesneeds review
Pinecone → Weaviate
Move indexes, collections, classes, and namespaces, vector ids, dimensions, and numeric values, payload, metadata, properties, and schema, distance metric and score semantics, filtering, hybrid search, and sparse vectors, embeddings and source text provenance, backups, snapshots, restore, and re-indexing, tenancy, authentication, and authorization from Pinecone to Weaviate with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual0 lost
CRMneeds review
Pipedrive → HubSpot
Export Pipedrive deals, people, organizations, and related notes into HubSpot contacts, companies, and deals. Pipelines, activities, and automations are a rebuild. HubSpot matches contacts on email and companies on domain.
- Elapsed
- 15–35 business days
- Active
- 40–90 hours
- Highest risk
- Critical
0 clean7 partial3 manual2 lost
CRMneeds review
Pipedrive → Salesforce
Move Pipedrive organizations, people, and deals into Salesforce accounts, contacts, and opportunities. Salesforce will not invent your stages, record types, or custom booking fields. Load a sandbox first.
- Elapsed
- 20–45 business days
- Active
- 50–110 hours
- Highest risk
- Critical
0 clean5 partial6 manual1 lost
Databasesneeds review
PlanetScale → Neon
Move a PlanetScale Vitess MySQL database to Neon Postgres with pgloader. Pause writes first. pgloader is a point-in-time copy. Use a direct Neon connection, put the endpoint ID in the password field, and check every type cast before you point the app at Neon.
- Elapsed
- 8–20 business days
- Active
- 30–70 hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Databasesneeds review
PlanetScale → PostgreSQL
Move a PlanetScale Vitess MySQL database to PostgreSQL with a dump plus pgloader, or a dump and a tool you already tested. Pause writes first. Vitess branches, deploy requests, and stored routines do not come along. TINYINT and DATETIME need a cast review.
- Elapsed
- 8–20 business days
- Active
- 30–70 hours
- Highest risk
- Critical
0 clean5 partial3 manual4 lost
Databasesneeds review
PlanetScale → Supabase
Move a PlanetScale Vitess MySQL database into Supabase Postgres. Dump through pscale if live queries stop at 100,000 rows. Load with pgloader into the public schema. Turn on RLS. Do not use the transaction pooler on port 6543 for the load.
- Elapsed
- 10–22 business days
- Active
- 36–80 hours
- Highest risk
- Critical
0 clean3 partial6 manual3 lost
Analyticsneeds review
Plausible → Google Analytics 4
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Plausible into Google Analytics 4 with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Plausible → Matomo
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Plausible into Matomo with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
Plausible → PostHog
Point the site at PostHog for new pageviews, and treat a Plausible history import as experimental. Plausible's portability export is aggregated, so it cannot become exact PostHog events.
- Elapsed
- 3 to 10 days
- Active
- 6 to 16 hours
- Highest risk
- Critical
0 clean4 partial5 manual2 lost
Paymentsneeds review
Polar → Lemon Squeezy
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Polar into Lemon Squeezy with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Paymentsneeds review
Polar → Stripe Billing
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Polar into Stripe Billing with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Databasesneeds review
PostgreSQL → MongoDB
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from PostgreSQL into MongoDB with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Databasesneeds review
PostgreSQL → MySQL
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from PostgreSQL into MySQL with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Databasesneeds review
PostgreSQL → Neon
Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from PostgreSQL into Neon with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial6 manual0 lost
Databasesneeds review
PostgreSQL → PlanetScale
Move a PostgreSQL database onto PlanetScale Postgres with pg_dump and pg_restore. Use --no-owner and --no-privileges. Size the PlanetScale disk to at least 150 percent of the source. Pause writes if you are not using the WAL streaming path.
- Elapsed
- 6–16 business days
- Active
- 22–55 hours
- Highest risk
- Critical
0 clean2 partial6 manual4 lost
Backendneeds review
PostgreSQL → Supabase
Move PostgreSQL schemas, data, extensions, roles, sequences, replication, and application access into Supabase Postgres without treating a dump file as a finished backend.
- Elapsed
- 10–25 business days
- Active
- 40–90 hours
- Highest risk
- Critical
0 clean7 partial2 manual3 lost
Analyticsneeds review
PostHog → Google Analytics 4
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from PostHog into Google Analytics 4 with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Analyticsneeds review
PostHog → Mixpanel
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from PostHog into Mixpanel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Transactional emailneeds review
Postmark → Mailgun
Move sending domains and sender identities, spf, dkim, and dmarc alignment, suppressions, bounces, complaints, and unsubscribes, templates, versions, and layouts, api payloads and provider sdks, webhooks and event semantics, dedicated ips and warm-up state, inbound email routes from Postmark to Mailgun with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Transactional emailneeds review
Postmark → Resend
Move Postmark sending to Resend by verifying domains, rewriting the API client, and importing each Message Stream’s suppressions. Postmark servers and streams do not exist in Resend. Mustachio templates do not import. Inbound mail needs a new receive path.
- Elapsed
- 8–18 business days
- Active
- 24–50 hours
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Transactional emailneeds review
Postmark → SendGrid
Move sending domains and sender identities, spf, dkim, and dmarc alignment, suppressions, bounces, complaints, and unsubscribes, templates, versions, and layouts, api payloads and provider sdks, webhooks and event semantics, dedicated ips and warm-up state, inbound email routes from Postmark to SendGrid with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Infrastructure as codeneeds review
Pulumi → OpenTofu
Move configuration source and language, state, resource addresses, and provider ids, providers, resources, and schema versions, modules, components, and reusable libraries, backends, locking, encryption, and history, secrets, variables, configuration, and environments, imports, moves, aliases, and replacements, plans, previews, policy, and approvals from Pulumi to OpenTofu with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Infrastructure as codeneeds review
Pulumi → Terraform
Move configuration source and language, state, resource addresses, and provider ids, providers, resources, and schema versions, modules, components, and reusable libraries, backends, locking, encryption, and history, secrets, variables, configuration, and environments, imports, moves, aliases, and replacements, plans, previews, policy, and approvals from Pulumi to Terraform with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Vector databasesneeds review
Qdrant → Pinecone
Move indexes, collections, classes, and namespaces, vector ids, dimensions, and numeric values, payload, metadata, properties, and schema, distance metric and score semantics, filtering, hybrid search, and sparse vectors, embeddings and source text provenance, backups, snapshots, restore, and re-indexing, tenancy, authentication, and authorization from Qdrant to Pinecone with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual0 lost
Vector databasesneeds review
Qdrant → Weaviate
Move indexes, collections, classes, and namespaces, vector ids, dimensions, and numeric values, payload, metadata, properties, and schema, distance metric and score semantics, filtering, hybrid search, and sparse vectors, embeddings and source text provenance, backups, snapshots, restore, and re-indexing, tenancy, authentication, and authorization from Qdrant to Weaviate with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual0 lost
Accounting and invoicingneeds review
QuickBooks Online → FreshBooks
Move chart of accounts and tracking dimensions, customers, suppliers, and contact identity, invoices, bills, credits, and payments, bank accounts, feeds, and reconciliation, products, services, inventory, and cost, tax rates, returns, and jurisdiction settings, payroll, expenses, projects, and time, attachments, templates, and communications from QuickBooks Online to FreshBooks with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Accounting and invoicingneeds review
QuickBooks Online → Xero
Move chart of accounts and tracking dimensions, customers, suppliers, and contact identity, invoices, bills, credits, and payments, bank accounts, feeds, and reconciliation, products, services, inventory, and cost, tax rates, returns, and jurisdiction settings, payroll, expenses, projects, and time, attachments, templates, and communications from QuickBooks Online to Xero with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Hostingneeds review
Railway → Fly.io
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Railway into Fly.io with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Railway → Render
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Railway into Render with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Render → Cloudflare Pages
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Render into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Render → Fly.io
Move a Render web service onto Fly.io machines, and move Render Postgres with pg_dump into Fly Managed Postgres. Disks and env vars do not come along with the image.
- Elapsed
- 3 to 10 days
- Active
- 12 to 30 hours
- Highest risk
- Critical
0 clean4 partial5 manual2 lost
Hostingneeds review
Render → Heroku
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Render into Heroku with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Render → Railway
Move Render services, workers, cron jobs, environment groups, Postgres, key-value data, persistent disks, domains, health checks, private networking, alerts, and deploy operations into Railway.
- Elapsed
- 8–18 business days
- Active
- 38–70 hours
- Highest risk
- Critical
1 clean7 partial4 manual0 lost
Hostingneeds review
Render → Vercel
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Render into Vercel with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Transactional emailneeds review
Resend → Postmark
Move Resend sending to Postmark by verifying Sender Signatures or domains, creating Servers and Message Streams, and importing Resend’s team-wide suppressions into each stream. React Email can keep rendering HTML. Postmark Templates are optional. SMTP is available on Postmark if you need it.
- Elapsed
- 8–18 business days
- Active
- 24–50 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
Transactional emailneeds review
Resend → SendGrid
Move Resend sending to SendGrid by authenticating domains again, rewriting the API client, and copying Resend’s team-wide suppressions onto SendGrid’s bounce, spam, and unsubscribe lists. React Email can keep rendering HTML. SendGrid template IDs are optional. IP reputation stays behind.
- Elapsed
- 8–18 business days
- Active
- 24–50 hours
- Highest risk
- Critical
0 clean3 partial6 manual3 lost
CRMneeds review
Salesforce → Airtable
Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from Salesforce into Airtable with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–160 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
CRMneeds review
Salesforce → HubSpot
Move Salesforce accounts, contacts, leads, opportunities, activities, files, custom fields, owners, automation, and integrations into HubSpot without duplicating or flattening critical relationships.
- Elapsed
- 20–40 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
CRMneeds review
Salesforce → Pipedrive
Move Salesforce records into Pipedrive with Import2 after the users exist. Salesforce's own export is a weekly or monthly ZIP that disappears 48 hours after it finishes, and it skips the recycle bin.
- Elapsed
- 1 to 3 weeks
- Active
- 12 to 24 hours
- Highest risk
- Critical
0 clean4 partial4 manual2 lost
CMSneeds review
Sanity → Astro
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Sanity into Astro with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
Sanity → Contentful
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Sanity into Contentful with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
Sanity → Strapi
Export a Sanity dataset to NDJSON and asset files, then create Strapi content types and load entries through the API. strapi import only accepts a Strapi archive, and it deletes the destination first.
- Elapsed
- 1 to 3 weeks
- Active
- 20 to 50 hours
- Highest risk
- Critical
0 clean5 partial3 manual3 lost
CMSneeds review
Sanity → WordPress
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Sanity into WordPress with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Transactional emailneeds review
SendGrid → Mailgun
Move sending domains and sender identities, spf, dkim, and dmarc alignment, suppressions, bounces, complaints, and unsubscribes, templates, versions, and layouts, api payloads and provider sdks, webhooks and event semantics, dedicated ips and warm-up state, inbound email routes from SendGrid to Mailgun with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Transactional emailneeds review
SendGrid → Postmark
Move sending domains and sender identities, spf, dkim, and dmarc alignment, suppressions, bounces, complaints, and unsubscribes, templates, versions, and layouts, api payloads and provider sdks, webhooks and event semantics, dedicated ips and warm-up state, inbound email routes from SendGrid to Postmark with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Transactional emailneeds review
SendGrid → Resend
Move SendGrid sending to Resend by verifying domains again, rewriting the API client, and importing suppressions. SendGrid templates and mail merge do not land as Resend templates. Use React Email or HTML you already render. Dedicated IPs and warm-up state stay behind.
- Elapsed
- 8–18 business days
- Active
- 24–50 hours
- Highest risk
- Critical
0 clean3 partial6 manual3 lost
Observability and error trackingneeds review
Sentry → Datadog
Move applications, services, and entity identity, metrics and metric types, logs, parsing, and pipelines, traces, spans, and sampling, errors, issues, releases, and source maps, dashboards, queries, and variables, monitors, alert conditions, and notifications, slos, incidents, and burn-rate policy from Sentry to Datadog with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Observability and error trackingneeds review
Sentry → New Relic
Move applications, services, and entity identity, metrics and metric types, logs, parsing, and pipelines, traces, spans, and sampling, errors, issues, releases, and source maps, dashboards, queries, and variables, monitors, alert conditions, and notifications, slos, incidents, and burn-rate policy from Sentry to New Relic with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Cloud storageneeds review
SharePoint → Box
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from SharePoint into Box with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds review
SharePoint → Google Drive
Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from SharePoint into Google Drive with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–145 hours
- Highest risk
- Critical
0 clean8 partial2 manual2 lost
Commerceneeds review
Shopify → BigCommerce
Move a Shopify store into BigCommerce while reconciling catalog models, customers, orders, inventory, subscriptions, payments, taxes, shipping, themes, content, SEO, apps, and multi-channel operations.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Commerceneeds review
Shopify → Gumroad
Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from Shopify into Gumroad with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Commerceneeds review
Shopify → Klaviyo
Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from Shopify into Klaviyo with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Commerceneeds review
Shopify → WooCommerce
Move Shopify catalog, customers, orders, coupons, pages, blogs, files, subscriptions, inventory, storefront, checkout, URLs, and integrations into a production-ready WooCommerce installation.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial1 manual2 lost
Designneeds review
Sketch → Figma
Move Sketch files, pages, artboards, symbols, libraries, styles, prototypes, fonts, comments, permissions, plugins, and handoff into Figma using the native importer and a deliberate library reconnection process.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
1 clean10 partial0 manual1 lost
Designneeds review
Sketch → Penpot
Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Sketch into Penpot with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Communicationneeds review
Slack → Discord
Move an active Slack community into Discord while archiving lawful history and rebuilding channels, roles, membership, files, threads, apps, moderation, notifications, and operational knowledge without claiming native message parity.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Communicationneeds review
Slack → Mattermost
Move spaces, channels, messages, threads, users, files, private scope, apps, retention evidence, and notification operations from Slack into Mattermost with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–35 business days
- Active
- 65–125 hours
- Highest risk
- Critical
0 clean8 partial1 manual3 lost
Collaborationneeds review
Slack → Microsoft Teams
Move Slack channels to Microsoft Teams with current Microsoft tooling while making direct-message loss, export-plan limits, identity mapping, files, apps, incremental passes, compliance, and user cutover explicit.
- Elapsed
- 20–45 business days
- Active
- 80–150 hours
- Highest risk
- Critical
0 clean6 partial1 manual3 lost
Project managementneeds review
Smartsheet → Airtable
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Smartsheet into Airtable with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
Smartsheet → monday.com
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Smartsheet into monday.com with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Data warehousesneeds review
Snowflake → Amazon Redshift
Move databases, schemas, tables, and rows, data types, precision, nulls, and time zones, views, materialized views, and sql dialect, primary keys, constraints, and data quality, users, roles, grants, row and column policy, pipelines, stages, external tables, and file formats, scheduled queries, tasks, procedures, and udfs, bi, dbt, notebooks, and downstream consumers from Snowflake to Amazon Redshift with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial7 manual1 lost
Data warehousesneeds review
Snowflake → Google BigQuery
Move databases, schemas, tables, and rows, data types, precision, nulls, and time zones, views, materialized views, and sql dialect, primary keys, constraints, and data quality, users, roles, grants, row and column policy, pipelines, stages, external tables, and file formats, scheduled queries, tasks, procedures, and udfs, bi, dbt, notebooks, and downstream consumers from Snowflake to Google BigQuery with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial7 manual1 lost
Publishingneeds review
Squarespace → Astro
Export Squarespace as one WordPress XML file, turn posts into Markdown, and serve them from an Astro content collection. Styles, extra blogs, store pages, and drafts stay behind.
- Elapsed
- 3 to 10 days
- Active
- 10 to 25 hours
- Highest risk
- Critical
0 clean4 partial3 manual4 lost
Publishingneeds review
Squarespace → Framer
Squarespace gives you one WordPress XML file, and it is a partial copy. Framer's Squarespace Import plugin loads the blog from that file. Pages, the shop, and the design are a rebuild, with redirects on the Framer domain.
- Elapsed
- 10 to 25 business days
- Active
- 30 to 70 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
Publishingneeds review
Squarespace → Ghost
Move a Squarespace blog into Ghost with the official Squarespace migrator and an XML export. Categories become tags. Squarespace only exports one primary blog and skips store, portfolio, drafts, and style. Plan redirects, because Ghost slugs will not match Squarespace date paths.
- Elapsed
- 7–14 business days
- Active
- 20–40 hours
- Highest risk
- Critical
0 clean4 partial3 manual5 lost
Commerceneeds review
Squarespace → Shopify
Move Squarespace products, customers, and fulfilled orders into Shopify with remapped CSVs, without treating the product export as a complete store, theme, review, or blog cutover.
- Elapsed
- 15–35 business days
- Active
- 55–130 hours
- Highest risk
- Critical
0 clean4 partial2 manual5 lost
Publishingneeds review
Squarespace → Webflow
Rebuild a Squarespace site in Webflow with an explicit plan for exported content, omitted page types, CMS structure, responsive design, forms, SEO, and domains.
- Elapsed
- 15–30 business days
- Active
- 60–105 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
Publishingneeds review
Squarespace → WordPress
Move Squarespace content into WordPress while accounting for the export’s strict page, block, blog, media, commerce, styling, and draft limitations.
- Elapsed
- 8–16 business days
- Active
- 32–56 hours
- Highest risk
- Critical
0 clean5 partial3 manual4 lost
ELT and data integrationneeds review
Stitch → Airbyte
Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Stitch to Airbyte with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial6 manual2 lost
ELT and data integrationneeds review
Stitch → Fivetran
Move sources, connectors, and authentication, destinations, schemas, and namespaces, streams, tables, fields, and selections, incremental cursors and replication state, historical backfill and reset behavior, transformations and normalization, schedules, concurrency, and rate limits, custom connectors and connector code from Stitch to Fivetran with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean2 partial6 manual2 lost
CMSneeds review
Strapi → Contentful
Export Strapi with strapi export, transform the JSONL entities into Contentful types, then load the space with the Contentful CLI. strapi export is built for another Strapi instance. Admin users and API tokens do not come along. Rebuild preview, roles, and webhooks.
- Elapsed
- 15–40 business days
- Active
- 70–160 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
CMSneeds review
Strapi → Sanity
Export Strapi as readable JSONL, then load Sanity with a migration script. Collection types become documents. Components become objects. Dynamic zones become arrays of named objects. Relations become references. Rich text becomes Portable Text. Upload assets first and keep Strapi documentId as a stable key.
- Elapsed
- 15–40 business days
- Active
- 70–160 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Paymentsneeds review
Stripe Billing → Chargebee
Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Stripe Billing into Chargebee with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial5 manual0 lost
Paymentsneeds review
Stripe Billing → Lemon Squeezy
Move Stripe products, customers, payment methods, invoices, subscriptions, and coupons into Lemon Squeezy through their two-phase, vendor-run PCI transfer. You send a Stripe account ID and a restricted read-only key. Indian subscription migrations are not supported. Link, SEPA, Bacs, and ACH methods may not copy. Cancel Stripe subscriptions only after Lemon Squeezy recreates them.
- Elapsed
- 20–45 business days
- Active
- 40–90 hours plus vendor wait
- Highest risk
- Critical
0 clean4 partial5 manual3 lost
Paymentsneeds review
Stripe Billing → Paddle
Move Stripe Billing customers, payment methods, subscriptions, catalog, discounts, invoices, tax, webhooks, application entitlements, and recurring revenue into Paddle through a provider-managed PCI transfer and controlled import date.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean7 partial4 manual1 lost
Paymentsneeds review
Stripe Billing → Polar
Move Stripe Billing products, customers, subscriptions, benefits, tax responsibilities, checkout, portal, webhooks, and application entitlement state into Polar without assuming paid subscriptions can be created through ordinary APIs.
- Elapsed
- 20–45 business days
- Active
- 90–170 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Newslettersneeds review
Substack → Beehiiv
Move Substack content, free and paid subscribers, podcast feeds, domains, and sending operations into Beehiiv without exposing paywalled posts or charging readers twice.
- Elapsed
- 7–15 business days
- Active
- 28–48 hours
- Highest risk
- Critical
0 clean7 partial3 manual2 lost
Newsletterneeds review
Substack → Ghost
Move a Substack publication to Ghost while reconciling content, free and paid members, Stripe continuity, custom-domain URLs, newsletter delivery, and a reversible first send.
- Elapsed
- 5–8 calendar days before first full send
- Active
- 10–16 hours
- Highest risk
- Critical
1 clean7 partial2 manual3 lost
Newsletterneeds review
Substack → Kit
Kit has no Substack importer. You export Substack, import two CSVs, and rebuild the archive as Broadcasts. Paid billing does not move. Readers have to subscribe again if you want Kit to charge them.
- Elapsed
- 10 to 25 business days
- Active
- 20 to 50 hours
- Highest risk
- Critical
0 clean1 partial9 manual2 lost
Newsletterneeds review
Substack → WordPress
Move Substack posts, images, podcasts, comments, and free or paid subscribers into WordPress.com with the official Substack importer. Keep Substack online until missing images are re-uploaded. Paid readers need the same Stripe account and a mapped newsletter tier.
- Elapsed
- 7–14 calendar days
- Active
- 14–28 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Backendneeds review
Supabase → Firebase
Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Supabase into Firebase with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Databasesneeds review
Supabase → Neon
Move the Supabase public schema to Neon with pg_dump. Leave auth, storage, realtime, and internal schemas behind unless you have a separate auth plan. Legacy Neon Auth could import bcrypt hashes. Managed Better Auth cannot. Remap user ids if you move auth at all.
- Elapsed
- 10–22 business days
- Active
- 40–85 hours
- Highest risk
- Critical
0 clean2 partial5 manual5 lost
Backendneeds review
Supabase → PostgreSQL
Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Supabase into PostgreSQL with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–45 business days
- Active
- 100–190 hours
- Highest risk
- Critical
0 clean6 partial4 manual2 lost
Forms and surveysneeds review
Tally → Jotform
Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Tally to Jotform with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Forms and surveysneeds review
Tally → Typeform
Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Tally to Typeform with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Course platformsneeds review
Teachable → Kajabi
Move courses, products, modules, and lessons, video, audio, pdfs, downloads, and embeds, students, profiles, and consent, enrollments, access, progress, and completion, quizzes, assignments, surveys, and certificates, offers, pricing, coupons, subscriptions, and tax, websites, sales pages, blogs, and domains, email, funnels, automations, and affiliates from Teachable to Kajabi with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Course platformsneeds review
Teachable → Thinkific
Move courses, products, modules, and lessons, video, audio, pdfs, downloads, and embeds, students, profiles, and consent, enrollments, access, progress, and completion, quizzes, assignments, surveys, and certificates, offers, pricing, coupons, subscriptions, and tax, websites, sales pages, blogs, and domains, email, funnels, automations, and affiliates from Teachable to Thinkific with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Infrastructure as codeneeds review
Terraform → OpenTofu
Move configuration source and language, state, resource addresses, and provider ids, providers, resources, and schema versions, modules, components, and reusable libraries, backends, locking, encryption, and history, secrets, variables, configuration, and environments, imports, moves, aliases, and replacements, plans, previews, policy, and approvals from Terraform to OpenTofu with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Infrastructure as codeneeds review
Terraform → Pulumi
Move configuration source and language, state, resource addresses, and provider ids, providers, resources, and schema versions, modules, components, and reusable libraries, backends, locking, encryption, and history, secrets, variables, configuration, and environments, imports, moves, aliases, and replacements, plans, previews, policy, and approvals from Terraform to Pulumi with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Course platformsneeds review
Thinkific → Kajabi
Move courses, products, modules, and lessons, video, audio, pdfs, downloads, and embeds, students, profiles, and consent, enrollments, access, progress, and completion, quizzes, assignments, surveys, and certificates, offers, pricing, coupons, subscriptions, and tax, websites, sales pages, blogs, and domains, email, funnels, automations, and affiliates from Thinkific to Kajabi with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Course platformsneeds review
Thinkific → Teachable
Move courses, products, modules, and lessons, video, audio, pdfs, downloads, and embeds, students, profiles, and consent, enrollments, access, progress, and completion, quizzes, assignments, surveys, and certificates, offers, pricing, coupons, subscriptions, and tax, websites, sales pages, blogs, and domains, email, funnels, automations, and affiliates from Thinkific to Teachable with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial4 manual1 lost
Project managementneeds review
Todoist → Asana
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Todoist into Asana with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
Todoist → Linear
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Todoist into Linear with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Project managementneeds review
Trello → Asana
Move Trello boards and cards into Asana projects and tasks while accounting for the CSV path’s loss of comments, activity, Power-Ups, automation, permissions, and board behavior.
- Elapsed
- 6–12 business days
- Active
- 22–40 hours
- Highest risk
- Critical
0 clean10 partial0 manual2 lost
Project managementneeds review
Trello → ClickUp
Move Trello boards, cards, members, comments, and files into ClickUp with the Trello importer, without treating the load as a complete copy of cover images, Butler rules, or unmapped assignees.
- Elapsed
- 12–30 business days
- Active
- 45–110 hours
- Highest risk
- Critical
0 clean9 partial1 manual1 lost
Project managementneeds review
Trello → Jira
Move Trello boards, cards, members, and comments into Jira without treating one importer as a complete copy of checklists, custom fields, archived lists, or Butler rules.
- Elapsed
- 12–30 business days
- Active
- 45–110 hours
- Highest risk
- Critical
0 clean9 partial1 manual1 lost
Project managementagent reviewed
Trello → Linear
Move active work from Trello boards to Linear teams without flattening list semantics, treating description-appended comments as Linear comments, duplicating notifications, or importing a backlog nobody intends to own.
- Elapsed
- Editorial estimate: 8–15 business days
- Active
- Editorial estimate: 32–55 active hours
- Highest risk
- Critical
0 clean7 partial3 manual3 lost
Knowledgeneeds review
Trello → Notion
Notion's Trello importer turns boards into databases, cards into items, and lists into groups. It is built for boards under about 5,000 cards and 5,000 comments. Power-Ups, automations, and permissions stay behind.
- Elapsed
- 8–20 business days
- Active
- 16–40 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Project managementneeds review
Trello → Todoist
Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Trello into Todoist with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–18 business days
- Active
- 35–72 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Forms and surveysneeds review
Typeform → Jotform
Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Typeform to Jotform with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Forms and surveysneeds review
Typeform → Tally
Move forms, pages, questions, and field ids, logic jumps, branching, scoring, and calculations, responses and stable submission identity, file uploads and respondent attachments, themes, layouts, localization, and accessibility, notifications, confirmations, and redirects, payments, signatures, and consent evidence, embeds, domains, links, and qr codes from Typeform to Tally with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Hosted searchneeds review
Typesense Cloud → Algolia
Move indexes, collections, records, and object ids, field schema and searchable attributes, text analysis, tokenization, and languages, ranking, relevance, and tie-breaking, synonyms, rules, and query rewriting, facets, filters, sorting, and replicas, query api and frontend clients, analytics, personalization, and experiments from Typesense Cloud to Algolia with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Hosted searchneeds review
Typesense Cloud → Elastic Cloud
Move indexes, collections, records, and object ids, field schema and searchable attributes, text analysis, tokenization, and languages, ranking, relevance, and tie-breaking, synonyms, rules, and query rewriting, facets, filters, sorting, and replicas, query api and frontend clients, analytics, personalization, and experiments from Typesense Cloud to Elastic Cloud with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean4 partial5 manual1 lost
Analyticsagent reviewed
Universal Analytics → Google Analytics 4
Rebuild measurement in GA4 and preserve any previously exported Universal Analytics history without pretending that historical UA data can be imported or that unlike metrics form one continuous series.
- Elapsed
- 15–25 business days
- Active
- 55–90 hours
- Highest risk
- Critical
0 clean7 partial2 manual3 lost
Analyticsneeds review
Universal Analytics → Matomo
Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Universal Analytics into Matomo with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean6 partial3 manual3 lost
Hostingneeds review
Vercel → Cloudflare Pages
Move a Vercel project to Cloudflare Pages while translating build settings, functions, edge behavior, environment values, domains, redirects, analytics, previews, and a measured rollback.
- Elapsed
- 7–15 business days
- Active
- 25–55 hours
- Highest risk
- Critical
1 clean2 partial5 manual2 lost
Hostingneeds review
Vercel → Fly.io
Move a Vercel app onto Fly Machines. You bring a Docker image, fly secrets, and DNS for your own certificate. The frontend can stay on Vercel.
- Elapsed
- 5 to 15 business days
- Active
- 20 to 50 hours
- Highest risk
- Critical
1 clean5 partial5 manual1 lost
Hostingneeds review
Vercel → Netlify
Move a Vercel project into Netlify while translating build settings, environments, domains, redirects, headers, functions, edge code, image handling, cron, storage, analytics, previews, and deployment operations.
- Elapsed
- 7–16 business days
- Active
- 32–62 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Hostingneeds review
Vercel → Railway
Run the same repo on Railway as a long-running service. Vercel secrets cannot be read back, and the www redirect is not a Railway checkbox.
- Elapsed
- 5 to 12 business days
- Active
- 16 to 40 hours
- Highest risk
- Critical
1 clean4 partial5 manual2 lost
Hostingneeds review
Vercel → Render
Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Vercel into Render with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 8–20 business days
- Active
- 38–80 hours
- Highest risk
- Critical
1 clean6 partial4 manual1 lost
Vector databasesneeds review
Weaviate → Pinecone
Move indexes, collections, classes, and namespaces, vector ids, dimensions, and numeric values, payload, metadata, properties, and schema, distance metric and score semantics, filtering, hybrid search, and sparse vectors, embeddings and source text provenance, backups, snapshots, restore, and re-indexing, tenancy, authentication, and authorization from Weaviate to Pinecone with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual0 lost
Vector databasesneeds review
Weaviate → Qdrant
Move indexes, collections, classes, and namespaces, vector ids, dimensions, and numeric values, payload, metadata, properties, and schema, distance metric and score semantics, filtering, hybrid search, and sparse vectors, embeddings and source text provenance, backups, snapshots, restore, and re-indexing, tenancy, authentication, and authorization from Weaviate to Qdrant with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean5 partial5 manual0 lost
Publishingneeds review
Webflow → Astro
Rebuild a Webflow site in Astro while preserving design intent, CMS content, assets, URLs, SEO, forms, search, localization, and a recoverable production path.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean3 partial2 manual5 lost
Publishingneeds review
Webflow → Framer
Rebuild a Webflow site in Framer. Export each CMS collection as CSV, then import into Framer collections. Classes, interactions, forms, memberships, and ecommerce do not arrive with the CSV. Keep URLs and add redirects before you switch DNS.
- Elapsed
- 12–30 business days
- Active
- 50–110 hours
- Highest risk
- Critical
0 clean4 partial6 manual2 lost
Publishingneeds review
Webflow → Ghost
Move a Webflow CMS blog into Ghost. Ghost has no Webflow importer. Export each collection as CSV, transform it into Ghost's JSON, and keep Webflow URLs with redirects. Design does not come along. Many teams keep Webflow for marketing pages and move only the blog.
- Elapsed
- 10–20 business days
- Active
- 40–80 hours
- Highest risk
- Critical
0 clean3 partial6 manual3 lost
Publishingneeds review
Webflow → WordPress
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Webflow into WordPress with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Commerceneeds review
Wix → Shopify
Move Wix products, customers, and fulfilled orders into Shopify with remapped CSVs or the Store Migration app, without treating the product export as a complete store, theme, review, or blog cutover.
- Elapsed
- 15–35 business days
- Active
- 55–130 hours
- Highest risk
- Critical
0 clean5 partial2 manual4 lost
Publishingneeds review
Wix → Webflow
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Wix into Webflow with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Publishingneeds review
Wix → WordPress
Move a Wix site into WordPress while rebuilding its design, apps, forms, blog archive, structured data, URLs, and domain settings around Wix’s limited content portability.
- Elapsed
- 12–24 business days
- Active
- 48–88 hours
- Highest risk
- Critical
0 clean6 partial3 manual3 lost
Commerceneeds review
WooCommerce → BigCommerce
Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from WooCommerce into BigCommerce with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 20–50 business days
- Active
- 100–200 hours
- Highest risk
- Critical
0 clean9 partial2 manual1 lost
Commerceneeds review
WooCommerce → Magento
Load WooCommerce products into Magento or Adobe Commerce with a CSV shaped like Adobe's sample file. Orders and customers are a separate export. Check Data before you import, and treat Replace as destructive.
- Elapsed
- 4 to 12 weeks
- Active
- 40 to 90 hours
- Highest risk
- Critical
0 clean3 partial7 manual1 lost
Commerceneeds review
WooCommerce → Shopify
Move WooCommerce products, customers, historical orders, reviews, subscriptions, inventory, content, URLs, taxes, shipping, payments, and operations into Shopify without treating a product CSV as a complete store migration.
- Elapsed
- 20–45 business days
- Active
- 95–180 hours
- Highest risk
- Critical
0 clean9 partial1 manual2 lost
Publishingneeds review
WordPress → Astro
Move a WordPress content site to a repository-native Astro build while preserving content, media, authorship, URLs, redirects, metadata, and a recoverable production path.
- Elapsed
- 5–11 calendar days
- Active
- 12–22 hours
- Highest risk
- Critical
1 clean4 partial5 manual3 lost
CMSneeds review
WordPress → Contentful
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Contentful with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Publishingneeds review
WordPress → Ghost
Move WordPress posts, pages, authors, media, taxonomies, subscribers, URLs, and publishing operations to Ghost without mistaking a content import for a complete site migration.
- Elapsed
- 7–14 business days
- Active
- 28–48 hours
- Highest risk
- Critical
0 clean6 partial3 manual3 lost
Publishingneeds review
WordPress → Medium
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Medium with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
WordPress → Sanity
Move WordPress posts, pages, authors, categories, tags, and media into Sanity with a CLI migration script over the REST API. Convert HTML or Gutenberg blocks to Portable Text. Rebuild the frontend. Page builders, SEO plugins, and ecommerce are out of Sanity's published course unless they appear on the API.
- Elapsed
- 15–35 business days
- Active
- 70–140 hours
- Highest risk
- Critical
0 clean4 partial6 manual2 lost
Commerceneeds review
WordPress → Shopify
Move WordPress posts into Shopify blog articles, then redirect the old paths. Shopify article handles do not keep a root-level post URL, and the WordPress export does not include the uploads folder.
- Elapsed
- 1 to 3 weeks
- Active
- 16 to 30 hours
- Highest risk
- Critical
0 clean4 partial4 manual2 lost
Publishingneeds review
WordPress → Squarespace
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Squarespace with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
CMSneeds review
WordPress → Strapi
Export WordPress with Tools Export, then create Strapi collections and post entries through the API. The WXR file is not a Strapi archive. strapi import would wipe the destination.
- Elapsed
- 1 to 3 weeks
- Active
- 20 to 45 hours
- Highest risk
- Critical
0 clean4 partial4 manual3 lost
Newsletterneeds review
WordPress → Substack
Move a WordPress blog into Substack by pasting the site URL, then import a consented subscriber CSV. Imported posts publish immediately. RSS alone can stop after about 20 posts. Images and footnotes need a pass before you send.
- Elapsed
- 6–14 calendar days
- Active
- 12–24 hours
- Highest risk
- Critical
0 clean5 partial4 manual3 lost
Publishingneeds review
WordPress → Webflow
Rebuild a WordPress site in Webflow while preserving public content, media, URLs, SEO, forms, and business integrations that cannot move through a simple CMS import.
- Elapsed
- 15–30 business days
- Active
- 60–110 hours
- Highest risk
- Critical
0 clean4 partial4 manual4 lost
Publishingneeds review
WordPress → Wix
Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Wix with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 12–30 business days
- Active
- 55–110 hours
- Highest risk
- Critical
0 clean5 partial5 manual2 lost
Accounting and invoicingneeds review
Xero → FreshBooks
Move chart of accounts and tracking dimensions, customers, suppliers, and contact identity, invoices, bills, credits, and payments, bank accounts, feeds, and reconciliation, products, services, inventory, and cost, tax rates, returns, and jurisdiction settings, payroll, expenses, projects, and time, attachments, templates, and communications from Xero to FreshBooks with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Accounting and invoicingneeds review
Xero → QuickBooks Online
Move chart of accounts and tracking dimensions, customers, suppliers, and contact identity, invoices, bills, credits, and payments, bank accounts, feeds, and reconciliation, products, services, inventory, and cost, tax rates, returns, and jurisdiction settings, payroll, expenses, projects, and time, attachments, templates, and communications from Xero to QuickBooks Online with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Workflow automationneeds review
Zapier → Make
Move workflow graph and step order, app connectors and operation coverage, credentials and oauth connections, field mappings and expressions, schedules, polling, and webhook triggers, error handling, retries, and partial execution, data stores, variables, and shared components, execution history and replay evidence from Zapier to Make with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Workflow automationneeds review
Zapier → n8n
Move workflow graph and step order, app connectors and operation coverage, credentials and oauth connections, field mappings and expressions, schedules, polling, and webhook triggers, error handling, retries, and partial execution, data stores, variables, and shared components, execution history and replay evidence from Zapier to n8n with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean3 partial6 manual1 lost
Customer supportneeds review
Zendesk → Freshdesk
Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Zendesk to Freshdesk with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
Customer supportneeds review
Zendesk → Help Scout
Import Zendesk tickets and customer profiles into Help Scout with Import2 after users and inboxes exist. The knowledge base needs Help Scout's older Zendesk tool, and macros and triggers stay behind.
- Elapsed
- 1 to 3 weeks
- Active
- 12 to 24 hours
- Highest risk
- Critical
1 clean4 partial4 manual1 lost
Customer supportneeds review
Zendesk → Intercom
Move customers, contacts, and organizations, tickets and conversations, public replies and private notes, attachments and inline media, agents, teams, roles, and permissions, custom fields, forms, tags, and statuses, macros, triggers, routing, and slas, help center articles and categories from Zendesk to Intercom with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean6 partial3 manual1 lost
CRMneeds review
Zoho CRM → HubSpot
Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from Zoho CRM into HubSpot with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–160 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
CRMneeds review
Zoho CRM → Salesforce
Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from Zoho CRM into Salesforce with an explicit exception ledger and evidence-based cutover.
- Elapsed
- 15–40 business days
- Active
- 75–160 hours
- Highest risk
- Critical
0 clean8 partial3 manual1 lost
Office suitesneeds review
Zoho Workplace → Google Workspace
Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Zoho Workplace to Google Workspace with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean7 partial3 manual0 lost
Office suitesneeds review
Zoho Workplace → Microsoft 365
Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Zoho Workplace to Microsoft 365 with a reversible cutover, explicit exception ledger, and evidence-backed verification.
- Elapsed
- 15–45 business days
- Active
- 70–180 hours
- Highest risk
- Critical
0 clean7 partial3 manual0 lost
No matching playbooks.Try another tool, category, or direction.