Preserve data and URLs, test live paths, protect access, manage cost, scale deliberately, and own the exit.
Inventory domains, pages, contacts, consent, tags, automations, email, products, payments, access, content, analytics, and support before moving. Pilot one complete path, preserve exports, run in parallel, and define rollback.
Leave with a reversible production system and a monthly maintenance rhythm.
Read the starting guide →Start with the question that can change your decision. Each summary below gives the current bottom line and opens a complete guide with evidence, limits, and practical next steps.
Inventory domains, pages, contacts, consent, tags, automations, email, products, payments, access, content, analytics, and support before moving. Pilot one complete path, preserve exports, run in parallel, and define rollback.
Work through this decision →Clean and map the file while preserving original source, consent, suppression, dates, fields, and exceptions. Stage a small set first and prevent imports from accidentally starting campaigns.
Work through this decision →Inventory active sequences, entry rules, exclusions, templates, links, sender identities, authentication, schedules, and people currently waiting. Pause or isolate triggers during cutover and reconcile live states.
Work through this decision →Map old pages, forms, checkout, scripts, events, thank-you states, redirects, metadata, and campaign links to the new path. Test every valuable inbound URL and paid-ad destination before cutover. Preserve query parameters, campaign IDs, consent state, form destinations, payment callbacks, confirmation pages, email triggers, and the original analytics baseline.
Work through this decision →If you are beginning from scratch, this sequence moves from overall fit to the details most likely to alter cost, risk, or implementation. If you already know the basics, jump directly to the guide that resolves your remaining uncertainty.
Inventory domains, pages, contacts, consent, tags, automations, email, products, payments, access, content, analytics, and support before moving. Pilot one complete path, preserve exports, run in parallel, and define rollback. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Clean and map the file while preserving original source, consent, suppression, dates, fields, and exceptions. Stage a small set first and prevent imports from accidentally starting campaigns. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Inventory active sequences, entry rules, exclusions, templates, links, sender identities, authentication, schedules, and people currently waiting. Pause or isolate triggers during cutover and reconcile live states. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
These pages are deliberately separated when they answer different buyer questions. Related links reconnect the parts without forcing you through a fixed reading order.
Inventory domains, pages, contacts, consent, tags, automations, email, products, payments, access, content, analytics, and support before moving. Pilot one complete path, preserve exports, run in parallel, and define rollback. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Important limitationsClean and map the file while preserving original source, consent, suppression, dates, fields, and exceptions. Stage a small set first and prevent imports from accidentally starting campaigns. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideInventory active sequences, entry rules, exclusions, templates, links, sender identities, authentication, schedules, and people currently waiting. Pause or isolate triggers during cutover and reconcile live states. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideMap old pages, forms, checkout, scripts, events, thank-you states, redirects, metadata, and campaign links to the new path. Test every valuable inbound URL and paid-ad destination before cutover. Preserve query parameters, campaign IDs, consent state, form destinations, payment callbacks, confirmation pages, email triggers, and the original analytics baseline. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideInventory lessons, files, progress, comments, access, cohorts, drip dates, certificates, subscriptions, refunds, and support. Tell learners what changes and test existing as well as new access. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Important limitationsRecord active DNS, valuable URLs, verification, email, redirects, canonicals, sitemap, robots, analytics, and SSL before changing records. Preserve unrelated services and monitor the live site after cutover. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideMap each valuable old URL to the closest useful new destination. Avoid chains, loops, blanket home redirects, and retiring pages that still satisfy a distinct need. Verify status, canonical, navigation, and sitemap. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideVerify domains, pages, forms, consent, email authentication, campaigns, checkout, taxes, receipts, access, automations, analytics, legal pages, support, backups, mobile, accessibility, speed, and rollback. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideTest desktop and mobile, keyboard use, links, empty and error states, new and existing contacts, payment outcomes, emails, access, delays, cancellation, refund, support, and recovery. Save evidence for every acceptance gate. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Important limitationsSchedule exports of contacts, transactions, content, offer configuration, automation logic, and essential evidence according to business risk. Test that another person can find and use them. Include a reconstruction note for domains, payment providers, sender authentication, active offers, customer entitlements, scheduled messages, integrations, and the manual customer-support path. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Important limitationsDefine responsibilities, grant only necessary account areas, avoid shared credentials where possible, document sensitive actions, and remove access immediately when work ends. Protect billing, exports, domains, and customer data. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideDocument recurring work by outcome: what starts it, inputs, steps, decisions, protected actions, evidence, owner, service level, fallback, and completion. Link to current platform documentation rather than duplicating unstable screens. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideReview plan use, contacts, deliverability, domains, forms, links, payments, access, automations, failures, exports, integrations, stale assets, source changes, and upcoming campaigns. Prioritize by customer and revenue consequence. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideReview actual contacts, funnels, campaigns, domains, courses, automations, team use, retained tools, fees, and support work. Downgrade or consolidate only after checking limits, data retention, and recovery. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideAdd offers, audiences, domains, and operators only after naming conventions, data ownership, reusable components, tests, analytics, support, and access controls survive the first operating cycle. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Important limitationsBefore canceling or changing plans, export needed data, map live domains and links, preserve customer access and obligations, stop automations safely, reconcile billing, and communicate material changes. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Important limitationsKeep current ownership, secure authentication, recovery methods, billing access, domain control, provider access, and an emergency contact path. Do not make one person or inbox the only route to the business. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →Practical guideIdentify the observed symptom, affected people, time, page or workflow, expected state, actual state, recent changes, and business impact. Trace the path step by step before rebuilding anything. Use current primary documentation, explicit assumptions, one representative customer journey, and a recoverable operating plan.
Read the guide →