Pick your old tool. Get your switch kit.

Honestly: most 6–20 person teams do it in 2–4 weeks running the two tools in parallel. The heavy lifting is week one (exports) and week two (rebuilding structure and importing) — weeks three and four are mostly letting the old tool wind down while new work happens in the new one. Block half a day a week for whoever owns the move and it stays painless.

No — because you export it first. That is deliberately step one of every kit on this page: tasks, contacts, time entries, campaign stats and form responses all come out as CSV or Excel before you touch anything else. What imports cleanly, import; what doesn't, archive where the team can still search it. Nothing gets deleted until you cancel — and by then you hold a full copy.

No — and be wary of any tool that promises one. Your data comes across via CSV and Excel exports and imports; your structure (boards, pipelines, automations, forms) is rebuilt with the same shape, which typically takes a few focused hours per area. That rebuild is also your one chance in years to drop the cruft — most teams migrate about 60% of what they had and never miss the rest.

Yes — plan for it. Week three of every kit is exactly that: new work starts in Landing only, while in-flight work finishes in the old tool. Two weeks in parallel is the sweet spot — long enough to catch anything the exports missed, short enough that nobody drifts back to old habits. The one exception is email: never send the same campaign from both tools to the same list.

We make Landing — the all-in-one platform this page maps your old stack onto. A genuinely useful, honest migration plan is the best introduction we know; the checklist is yours either way. No payment, no trial, no strings.