Versioned migration intelligence

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.

354 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.

Websites & commerce

Publishing, storefronts, newsletters, and web delivery.

Data & intelligence

Operational data, analytics, search, and AI retrieval.

Engineering & infrastructure

Code, deployment, runtime, storage, and production operations.

Customers & operations

Revenue, service, finance, agreements, and automation.

Work & collaboration

Team communication, files, knowledge, planning, and design.

Identity, learning & community

Access, credentials, education, and member spaces.

Migrating from Migrating to

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 → 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

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 → 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

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 → 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

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 manual3 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 source-and-history-only migration.

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

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 → 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

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 → 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

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 → 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

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 → 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

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

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 → 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

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 → 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

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

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

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

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

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 → 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 → 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 → 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 → 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 clean5 partial5 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

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 → 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

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

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 → 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

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

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 → 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

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 → 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

Hostingtested

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
Hi

Move witha plan.

Evidence-led paths, not generic advice.

Choose an area, then a category.

Websites & commerce

Data & intelligence

Engineering & infrastructure

Customers & operations

Work & collaboration

Identity, learning & community

Move with
a plan.