Versioned migration intelligence

Move without losing
what matters.

Exact migration playbooks with loss matrices, field mappings, risk warnings, realistic timelines, rollback plans, and evidence-based verification.

Loss matrixClean, partial, manual, or lost
Precise timelineActive work separated from waiting
Rollback planTriggers, deadline, and proof
Verification reportBlocking checks with evidence
The catalog

Tested paths, not generic advice.

240 complete migration paths. Search by tool or filter where you are and where you’re going; every guide shows its current review status.

240 playbooksShowing documentation-reviewed and tested paths
Password managersneeds-review

1Password → Bitwarden

Move 1Password personal and business vaults into Bitwarden while protecting plaintext exports and reconciling every login, custom field, TOTP, passkey, attachment, item type, shared vault, permission, policy, and integration.

Elapsed
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Password managersneeds-review

1Password → LastPass

Move vault items, custom fields, TOTP, passkeys, attachments, shared access, identity policy, recovery, and audit evidence from 1Password into LastPass with an explicit exception ledger and evidence-based cutover.

Elapsed
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean8 partial2 manual2 lost
CRMneeds-review

ActiveCampaign → HubSpot

Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from ActiveCampaign into HubSpot with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–160 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Newsletterneeds-review

ActiveCampaign → Kit

Move subscribers, suppressions, fields, segments, content, automations, forms, domains, billing, analytics, and sender operations from ActiveCampaign into Kit with an explicit exception ledger and evidence-based cutover.

Elapsed
8–18 business days
Active
35–70 hours
Highest risk
Critical
0 clean6 partial5 manual1 lost
Newsletterneeds-review

ActiveCampaign → 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
Databasesneeds-review

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
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Knowledgeneeds-review

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
10–20 business days
Active
40–75 hours
Highest risk
Critical
1 clean2 partial3 manual4 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 managementneeds-review

Asana → ClickUp

Move Asana projects, sections, tasks, subtasks, users, comments, attachments, milestones, fields, dependencies, recurring work, and permissions into ClickUp without changing who can see or act on work.

Elapsed
8–16 business days
Active
30–54 hours
Highest risk
Critical
0 clean11 partial1 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
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 hostingneeds-review

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
18–35 business days
Active
80–145 hours
Highest risk
Critical
1 clean7 partial2 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
Project managementneeds-review

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
8–16 business days
Active
30–54 hours
Highest risk
Critical
0 clean9 partial1 manual2 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
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
Developmentneeds-review

Bitbucket → GitHub

Move Bitbucket repositories to GitHub with verified Git history, LFS, identities, pull-request context, branch policy, pipelines, secrets, webhooks, deployment keys, and a mirror-based rollback.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
1 clean3 partial4 manual2 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
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
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
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
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
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
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
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
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
Hostingneeds-review

Fly.io → Railway

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Fly.io into Railway with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Hostingneeds-review

Fly.io → Render

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Fly.io into Render with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Publishingneeds-review

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
Developmentneeds-review

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
15–30 business days
Active
70–130 hours
Highest risk
Critical
1 clean7 partial3 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
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
Storageneeds-review

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
15–30 business days
Active
45–80 hours
Highest risk
Critical
1 clean5 partial3 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
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
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
Newslettersneeds-review

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
1 clean4 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
Securityneeds-review

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
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
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
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
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
Highest risk
Critical
1 clean7 partial4 manual0 lost
Knowledgeneeds-review

Notion → Coda

Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Notion into Coda with an explicit exception ledger and evidence-based cutover.

Elapsed
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Documentationneeds-review

Notion → Confluence

Move Notion pages, users, workspaces, attachments, databases, comments, links, and permissions into Confluence while separating portable knowledge from Notion-specific application behavior.

Elapsed
10–22 business days
Active
42–78 hours
Highest risk
Critical
0 clean8 partial2 manual2 lost
Knowledgeneeds-review

Notion → Evernote

Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Notion into Evernote with an explicit exception ledger and evidence-based cutover.

Elapsed
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Knowledgeneeds-review

Notion → Obsidian

Move a Notion workspace into a local Obsidian vault while preserving page content, attachments, links, database meaning, ownership decisions, and a testable archive of what cannot become plain files.

Elapsed
7–14 business days
Active
28–48 hours
Highest risk
Critical
1 clean5 partial0 manual6 lost
Knowledgeneeds-review

Obsidian → Coda

Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Obsidian into Coda with an explicit exception ledger and evidence-based cutover.

Elapsed
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Knowledgeneeds-review

Obsidian → Notion

Move documents, hierarchy, links, attachments, structured data, comments, permissions, search, templates, and integrations from Obsidian into Notion with an explicit exception ledger and evidence-based cutover.

Elapsed
10–25 business days
Active
45–90 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Cloud storageneeds-review

OneDrive → Dropbox

Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from OneDrive into Dropbox with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–145 hours
Highest risk
Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds-review

OneDrive → Google Drive

Move OneDrive business files into Google Drive while mapping identities, My Drive and shared drives, Microsoft-native collaboration, versions, permissions, links, retention, and connected Microsoft 365 workflows.

Elapsed
15–40 business days
Active
75–145 hours
Highest risk
Critical
0 clean9 partial1 manual2 lost
Cloud storageneeds-review

OneDrive → SharePoint

Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from OneDrive into SharePoint with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–145 hours
Highest risk
Critical
0 clean8 partial2 manual2 lost
Paymentsneeds-review

Paddle → Polar

Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Paddle into Polar with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean7 partial5 manual0 lost
Paymentsneeds-review

Paddle → Stripe Billing

Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Paddle into Stripe Billing with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean7 partial5 manual0 lost
Designneeds-review

Penpot → Figma

Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Penpot into Figma with an explicit exception ledger and evidence-based cutover.

Elapsed
15–35 business days
Active
70–140 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Designneeds-review

Penpot → Sketch

Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Penpot into Sketch with an explicit exception ledger and evidence-based cutover.

Elapsed
15–35 business days
Active
70–140 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Analyticsneeds-review

Plausible → Google Analytics 4

Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Plausible into Google Analytics 4 with an explicit exception ledger and evidence-based cutover.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean6 partial4 manual2 lost
Analyticsneeds-review

Plausible → Matomo

Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Plausible into Matomo with an explicit exception ledger and evidence-based cutover.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean6 partial4 manual2 lost
Paymentsneeds-review

Polar → Lemon Squeezy

Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Polar into Lemon Squeezy with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean7 partial5 manual0 lost
Paymentsneeds-review

Polar → Stripe Billing

Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Polar into Stripe Billing with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean7 partial5 manual0 lost
Databasesneeds-review

PostgreSQL → MongoDB

Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from PostgreSQL into MongoDB with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
100–190 hours
Highest risk
Critical
0 clean6 partial6 manual0 lost
Databasesneeds-review

PostgreSQL → MySQL

Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from PostgreSQL into MySQL with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
100–190 hours
Highest risk
Critical
0 clean6 partial6 manual0 lost
Databasesneeds-review

PostgreSQL → Neon

Move schemas, records, types, relationships, indexes, queries, permissions, logic, replication, backups, and application cutover from PostgreSQL into Neon with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
100–190 hours
Highest risk
Critical
0 clean6 partial6 manual0 lost
Analyticsneeds-review

PostHog → Google Analytics 4

Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from PostHog into Google Analytics 4 with an explicit exception ledger and evidence-based cutover.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean6 partial4 manual2 lost
Analyticsneeds-review

PostHog → Mixpanel

Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from PostHog into Mixpanel with an explicit exception ledger and evidence-based cutover.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean6 partial4 manual2 lost
Hostingneeds-review

Railway → Fly.io

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Railway into Fly.io with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Hostingneeds-review

Railway → Render

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Railway into Render with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Hostingneeds-review

Render → Cloudflare Pages

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Render into Cloudflare Pages with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Hostingneeds-review

Render → Heroku

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Render into Heroku with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Hostingneeds-review

Render → Railway

Move Render services, workers, cron jobs, environment groups, Postgres, key-value data, persistent disks, domains, health checks, private networking, alerts, and deploy operations into Railway.

Elapsed
8–18 business days
Active
38–70 hours
Highest risk
Critical
1 clean7 partial4 manual0 lost
Hostingneeds-review

Render → Vercel

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Render into Vercel with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
CRMneeds-review

Salesforce → Airtable

Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from Salesforce into Airtable with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–160 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
CRMneeds-review

Salesforce → HubSpot

Move Salesforce accounts, contacts, leads, opportunities, activities, files, custom fields, owners, automation, and integrations into HubSpot without duplicating or flattening critical relationships.

Elapsed
20–40 business days
Active
90–170 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
CMSneeds-review

Sanity → Astro

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Sanity into Astro with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
CMSneeds-review

Sanity → Contentful

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Sanity into Contentful with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
CMSneeds-review

Sanity → WordPress

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Sanity into WordPress with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Cloud storageneeds-review

SharePoint → Box

Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from SharePoint into Box with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–145 hours
Highest risk
Critical
0 clean8 partial2 manual2 lost
Cloud storageneeds-review

SharePoint → Google Drive

Move files, folders, ownership, permissions, versions, native documents, shared containers, links, compliance evidence, and integrations from SharePoint into Google Drive with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–145 hours
Highest risk
Critical
0 clean8 partial2 manual2 lost
Commerceneeds-review

Shopify → BigCommerce

Move a Shopify store into BigCommerce while reconciling catalog models, customers, orders, inventory, subscriptions, payments, taxes, shipping, themes, content, SEO, apps, and multi-channel operations.

Elapsed
20–50 business days
Active
100–200 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Commerceneeds-review

Shopify → Gumroad

Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from Shopify into Gumroad with an explicit exception ledger and evidence-based cutover.

Elapsed
20–50 business days
Active
100–200 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Commerceneeds-review

Shopify → Klaviyo

Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from Shopify into Klaviyo with an explicit exception ledger and evidence-based cutover.

Elapsed
20–50 business days
Active
100–200 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Commerceneeds-review

Shopify → WooCommerce

Move Shopify catalog, customers, orders, coupons, pages, blogs, files, subscriptions, inventory, storefront, checkout, URLs, and integrations into a production-ready WooCommerce installation.

Elapsed
20–50 business days
Active
100–200 hours
Highest risk
Critical
0 clean9 partial1 manual2 lost
Designneeds-review

Sketch → Figma

Move Sketch files, pages, artboards, symbols, libraries, styles, prototypes, fonts, comments, permissions, plugins, and handoff into Figma using the native importer and a deliberate library reconnection process.

Elapsed
15–35 business days
Active
70–140 hours
Highest risk
Critical
1 clean10 partial0 manual1 lost
Designneeds-review

Sketch → Penpot

Move files, pages, components, libraries, styles, variables, layouts, prototypes, fonts, comments, permissions, and handoff from Sketch into Penpot with an explicit exception ledger and evidence-based cutover.

Elapsed
15–35 business days
Active
70–140 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Communicationneeds-review

Slack → Discord

Move an active Slack community into Discord while archiving lawful history and rebuilding channels, roles, membership, files, threads, apps, moderation, notifications, and operational knowledge without claiming native message parity.

Elapsed
15–35 business days
Active
65–125 hours
Highest risk
Critical
0 clean8 partial1 manual3 lost
Communicationneeds-review

Slack → Mattermost

Move spaces, channels, messages, threads, users, files, private scope, apps, retention evidence, and notification operations from Slack into Mattermost with an explicit exception ledger and evidence-based cutover.

Elapsed
15–35 business days
Active
65–125 hours
Highest risk
Critical
0 clean8 partial1 manual3 lost
Collaborationneeds-review

Slack → Microsoft Teams

Move Slack channels to Microsoft Teams with current Microsoft tooling while making direct-message loss, export-plan limits, identity mapping, files, apps, incremental passes, compliance, and user cutover explicit.

Elapsed
20–45 business days
Active
80–150 hours
Highest risk
Critical
0 clean6 partial1 manual3 lost
Project managementneeds-review

Smartsheet → Airtable

Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Smartsheet into Airtable with an explicit exception ledger and evidence-based cutover.

Elapsed
8–18 business days
Active
35–72 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Project managementneeds-review

Smartsheet → monday.com

Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Smartsheet into monday.com with an explicit exception ledger and evidence-based cutover.

Elapsed
8–18 business days
Active
35–72 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Publishingneeds-review

Squarespace → Webflow

Rebuild a Squarespace site in Webflow with an explicit plan for exported content, omitted page types, CMS structure, responsive design, forms, SEO, and domains.

Elapsed
15–30 business days
Active
60–105 hours
Highest risk
Critical
0 clean5 partial4 manual3 lost
Publishingneeds-review

Squarespace → WordPress

Move Squarespace content into WordPress while accounting for the export’s strict page, block, blog, media, commerce, styling, and draft limitations.

Elapsed
8–16 business days
Active
32–56 hours
Highest risk
Critical
0 clean5 partial3 manual4 lost
Paymentsneeds-review

Stripe Billing → Chargebee

Move products, prices, customers, payment methods, subscriptions, invoices, tax settings, webhooks, entitlements, and financial evidence from Stripe Billing into Chargebee with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean7 partial5 manual0 lost
Paymentsneeds-review

Stripe Billing → Paddle

Move Stripe Billing customers, payment methods, subscriptions, catalog, discounts, invoices, tax, webhooks, application entitlements, and recurring revenue into Paddle through a provider-managed PCI transfer and controlled import date.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean7 partial4 manual1 lost
Paymentsneeds-review

Stripe Billing → Polar

Move Stripe Billing products, customers, subscriptions, benefits, tax responsibilities, checkout, portal, webhooks, and application entitlement state into Polar without assuming paid subscriptions can be created through ordinary APIs.

Elapsed
20–45 business days
Active
90–170 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
Newslettersneeds-review

Substack → Beehiiv

Move Substack content, free and paid subscribers, podcast feeds, domains, and sending operations into Beehiiv without exposing paywalled posts or charging readers twice.

Elapsed
7–15 business days
Active
28–48 hours
Highest risk
Critical
0 clean7 partial3 manual2 lost
Newslettertested

Substack → Ghost

Move a Substack publication to Ghost while reconciling content, free and paid members, Stripe continuity, custom-domain URLs, newsletter delivery, and a reversible first send.

Elapsed
5–8 calendar days before first full send
Active
10–16 hours
Highest risk
Critical
1 clean7 partial2 manual3 lost
Backendneeds-review

Supabase → Firebase

Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Supabase into Firebase with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
100–190 hours
Highest risk
Critical
0 clean6 partial4 manual2 lost
Backendneeds-review

Supabase → PostgreSQL

Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Supabase into PostgreSQL with an explicit exception ledger and evidence-based cutover.

Elapsed
20–45 business days
Active
100–190 hours
Highest risk
Critical
0 clean6 partial4 manual2 lost
Project managementneeds-review

Todoist → Asana

Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Todoist into Asana with an explicit exception ledger and evidence-based cutover.

Elapsed
8–18 business days
Active
35–72 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Project managementneeds-review

Todoist → Linear

Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Todoist into Linear with an explicit exception ledger and evidence-based cutover.

Elapsed
8–18 business days
Active
35–72 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Project managementneeds-review

Trello → Asana

Move Trello boards and cards into Asana projects and tasks while accounting for the CSV path’s loss of comments, activity, Power-Ups, automation, permissions, and board behavior.

Elapsed
6–12 business days
Active
22–40 hours
Highest risk
Critical
0 clean10 partial0 manual2 lost
Project managementneeds-review

Trello → Linear

Move active work from Trello boards to Linear teams without flattening list semantics, losing attachment or comment context, duplicating notifications, or importing a backlog nobody intends to own.

Elapsed
8–15 business days
Active
32–55 hours
Highest risk
Critical
1 clean7 partial1 manual4 lost
Project managementneeds-review

Trello → Todoist

Move projects, work items, hierarchy, statuses, users, comments, attachments, custom fields, automation, permissions, and reports from Trello into Todoist with an explicit exception ledger and evidence-based cutover.

Elapsed
8–18 business days
Active
35–72 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Analyticsneeds-review

Universal Analytics → Google Analytics 4

Rebuild measurement in GA4 and preserve any previously exported Universal Analytics history without pretending that historical UA data can be imported or that unlike metrics form one continuous series.

Elapsed
15–25 business days
Active
55–90 hours
Highest risk
Critical
0 clean6 partial3 manual3 lost
Analyticsneeds-review

Universal Analytics → Matomo

Move events, properties, identities, conversions, attribution, ecommerce, reports, audiences, consent, collection, and historical evidence from Universal Analytics into Matomo with an explicit exception ledger and evidence-based cutover.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean6 partial3 manual3 lost
Hostingneeds-review

Vercel → Cloudflare Pages

Move a Vercel project to Cloudflare Pages while translating build settings, functions, edge behavior, environment values, domains, redirects, analytics, previews, and a measured rollback.

Elapsed
7–15 business days
Active
25–55 hours
Highest risk
Critical
1 clean2 partial5 manual2 lost
Hostingneeds-review

Vercel → Netlify

Move a Vercel project into Netlify while translating build settings, environments, domains, redirects, headers, functions, edge code, image handling, cron, storage, analytics, previews, and deployment operations.

Elapsed
7–16 business days
Active
32–62 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Hostingneeds-review

Vercel → Render

Move builds, previews, functions, routing, domains, environment configuration, stateful services, observability, and deployment controls from Vercel into Render with an explicit exception ledger and evidence-based cutover.

Elapsed
8–20 business days
Active
38–80 hours
Highest risk
Critical
1 clean6 partial4 manual1 lost
Publishingneeds-review

Webflow → Astro

Rebuild a Webflow site in Astro while preserving design intent, CMS content, assets, URLs, SEO, forms, search, localization, and a recoverable production path.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean3 partial2 manual5 lost
Publishingneeds-review

Webflow → WordPress

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Webflow into WordPress with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Publishingneeds-review

Wix → Webflow

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from Wix into Webflow with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Publishingneeds-review

Wix → WordPress

Move a Wix site into WordPress while rebuilding its design, apps, forms, blog archive, structured data, URLs, and domain settings around Wix’s limited content portability.

Elapsed
12–24 business days
Active
48–88 hours
Highest risk
Critical
0 clean6 partial3 manual3 lost
Commerceneeds-review

WooCommerce → BigCommerce

Move catalog, customers, orders, subscriptions, discounts, inventory, taxes, shipping, storefront routes, apps, and financial evidence from WooCommerce into BigCommerce with an explicit exception ledger and evidence-based cutover.

Elapsed
20–50 business days
Active
100–200 hours
Highest risk
Critical
0 clean9 partial2 manual1 lost
Commerceneeds-review

WooCommerce → Shopify

Move WooCommerce products, customers, historical orders, reviews, subscriptions, inventory, content, URLs, taxes, shipping, payments, and operations into Shopify without treating a product CSV as a complete store migration.

Elapsed
20–45 business days
Active
95–180 hours
Highest risk
Critical
0 clean9 partial1 manual2 lost
Publishingtested

WordPress → Astro

Move a WordPress content site to a repository-native Astro build while preserving content, media, authorship, URLs, redirects, metadata, and a recoverable production path.

Elapsed
5–11 calendar days
Active
12–22 hours
Highest risk
Critical
1 clean4 partial5 manual3 lost
CMSneeds-review

WordPress → Contentful

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Contentful with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Publishingneeds-review

WordPress → Ghost

Move WordPress posts, pages, authors, media, taxonomies, subscribers, URLs, and publishing operations to Ghost without mistaking a content import for a complete site migration.

Elapsed
7–14 business days
Active
28–48 hours
Highest risk
Critical
0 clean6 partial3 manual3 lost
Publishingneeds-review

WordPress → Medium

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Medium with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Publishingneeds-review

WordPress → Squarespace

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Squarespace with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
Publishingneeds-review

WordPress → Webflow

Rebuild a WordPress site in Webflow while preserving public content, media, URLs, SEO, forms, and business integrations that cannot move through a simple CMS import.

Elapsed
15–30 business days
Active
60–110 hours
Highest risk
Critical
0 clean4 partial4 manual4 lost
Publishingneeds-review

WordPress → Wix

Move content, assets, authors, URLs, SEO, design, forms, permissions, integrations, and publishing operations from WordPress into Wix with an explicit exception ledger and evidence-based cutover.

Elapsed
12–30 business days
Active
55–110 hours
Highest risk
Critical
0 clean5 partial5 manual2 lost
CRMneeds-review

Zoho CRM → HubSpot

Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from Zoho CRM into HubSpot with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–160 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
CRMneeds-review

Zoho CRM → Salesforce

Move contacts, companies, deals, activities, fields, owners, permissions, automation, reports, files, and integrations from Zoho CRM into Salesforce with an explicit exception ledger and evidence-based cutover.

Elapsed
15–40 business days
Active
75–160 hours
Highest risk
Critical
0 clean8 partial3 manual1 lost
No matching playbooks.Try another tool, category, or direction.
Need an operating document?

Take the playbook into the migration room.

The $29 kit turns a guide into a polished PDF, day-by-day schedule, risk register, editable worksheets, and a fillable verification report.

See what’s in the kit