If you're reading this, you already got the email. Height is shutting down, and the tool your team has run sprints in for the last few years now has an expiration date on it. Annoying. The work doesn't stop just because the vendor did.

The good news: you have time to move deliberately instead of in a panic. The bad news: if you wait until the last week, you'll lose two things that are hard to recover — the structured data trapped inside Height, and every link pointing at a Height task that's about to start returning a 404.

This is a step-by-step migration plan written for Height users specifically. Export, audit, rebuild. We'll move you into Zoobbe, but the export and audit steps apply no matter where you land.

Key takeaways

  • Export your Height data to CSV now, while the app is still up — don't wait for the deadline.
  • Run a dead-link audit: every Height task URL shared in Slack, docs, PRs, and tickets will break when the app goes dark.
  • Rebuild structure first (boards, lists, labels), then pour tasks in — Zoobbe's text-to-tasks parser turns pasted task lists into cards.
  • Use the migration as a chance to drop the cruft: dead projects, stale labels, the board nobody opened since Q2.
  • Zoobbe natively imports Trello and Fluent Board, so if any of your data already lives there, that path is one step.

Step 1: Export everything from Height before the lights go out

The single rule of any shutdown migration: get your data out while the source is still live. A dead app exports nothing.

Open Height and export your workspace data to CSV. Pull every project, not just the active ones — the archived stuff is where decisions and context tend to hide, and you'll want it for reference even if you never reactivate those tasks. Save the files somewhere durable: a shared drive, a repo, anywhere that isn't the tool you're leaving.

What the CSV typically gives you: task titles, statuses, assignees, due dates, and descriptions. What it usually doesn't preserve cleanly: threaded comments, attachments, and the visual structure of your workflow. That's fine. The CSV is your source of truth for what the work is. You'll rebuild the how in the next steps.

This is the step that saves you months of quiet confusion later, and almost nobody does it.

Over the years, your team has pasted Height task links everywhere. In Slack threads. In GitHub pull request descriptions. In Google Docs and meeting notes. In other tools' tickets. Every one of those links points at a domain that's about to stop resolving. When Height shuts down, they don't redirect — they break. Anyone who clicks one in six months gets a dead page and zero context.

Here's how to get ahead of it:

  1. Search your connected tools for Height URLs. Grep your Slack export, search your docs, search your codebase and PR history for the Height domain. Make a list.
  2. Prioritize the load-bearing links. A throwaway link in a closed thread doesn't matter. A Height task linked from your engineering runbook, your onboarding doc, or an open epic absolutely does.
  3. Replace as you rebuild. As each task gets recreated in its new home, swap the old Height URL for the new one in those load-bearing places.

You won't catch every link. You don't need to. You need to catch the ones people actually follow, and you can only do that while Height is still up to tell you what each link was.

Step 3: Rebuild your structure in Zoobbe (skeleton first)

Resist the urge to dump 800 tasks into a fresh board and sort it out later. Build the skeleton first, then fill it.

In Zoobbe, set up your boards to match how your team actually works — lists for your real stages, not Height's defaults. Recreate your labels as reusable, color-coded board labels so a card's status reads at a glance. Set card priorities (Normal, High, Low, Urgent) and due dates with reminders so nothing that mattered in Height quietly slips through the move.

A migration is a rare licensed opportunity to throw things away. That board nobody's opened since spring? Don't migrate it. The seven overlapping labels that all meant "needs review"? Collapse them into one. You're not obligated to carry every piece of organizational debt across the border.

Step 4: Pour the tasks in

Now the skeleton is ready and you have CSV files full of task titles. Instead of retyping them card by card, Zoobbe's text-to-tasks parser takes a natural-language list and turns it into multiple tasks at once. Paste a column of task titles from your export, and it creates the cards for you. For anything more conversational — "set these up as cards on the Sprint board" — the AI chatbot can create and move cards directly from a plain-language request.

Work board by board rather than all at once. Bring one project fully across, confirm it looks right, replace its dead links, then move to the next. A migration done in clean passes is one you can actually finish.

Step 5: Rebuild the automation you took for granted

Half of what a tool does for you is invisible until it's gone. Before you call the move done, recreate the rules that ran quietly in the background.

Zoobbe automations follow a trigger → condition → action shape. When a card moves to a list, when a due date approaches, when a checklist completes, when a label gets added — fire an action: assign someone, set a due date, move the card, add a comment, send a notification. Scheduled automations run on cron expressions for recurring work. Spend twenty minutes here and your new boards will feel like home instead of a spreadsheet with extra steps.

What you get on the other side

Once you're across, the day-to-day is the part that actually matters. Zoobbe gives you Kanban boards plus Notion-style Pages for specs and docs, with real-time collaborative editing built on Yjs CRDTs — two people editing the same page, no refresh, no overwrite. There's time tracking per card with start/pause/resume timers, a personal My Day list for what's in front of you today, and AI Insights for bottleneck detection and workload balance once you've got history built up.

The point isn't a feature list. The point is that you land somewhere your team can run sprints the day after the move, not three weeks later.

A shutdown is a forced migration. It's also the cleanest excuse you'll ever get to leave the dead weight behind.

FAQ

When should I start migrating off Height?

Now, while the app is live. Exports only work from a running tool, and the dead-link audit depends on Height being up to show you what each link pointed at. Don't wait for the deadline.

Can I move my Height data into Zoobbe directly?

Export your Height data to CSV, then use Zoobbe's text-to-tasks parser to turn your task lists into cards, or have the AI chatbot create them. If any of your work already lives in Trello or Fluent Board, Zoobbe imports those natively in one step.

They break when Height shuts down. That's why the dead-link audit matters: find Height URLs in Slack, docs, and PRs while you still can, and replace the load-bearing ones as you rebuild each task in its new home.

Will I lose my comments and attachments?

CSV exports preserve task titles, statuses, assignees, due dates, and descriptions well, but comment threads and attachments often don't survive cleanly. Save anything critical separately before the shutdown, and treat the CSV as your record of what the work is.

Do I have to migrate everything?

No, and you shouldn't. A shutdown is a chance to drop the dead projects and duplicate labels. Migrate the work that's alive; archive or abandon the rest.

Don't let the deadline make the decision for you

The teams that come out of a shutdown clean are the ones that move early and deliberately. Export this week. Audit your links next. Rebuild your boards in passes. Start your move to Zoobbe and have your team running sprints again before Height's lights even go off.

Photo by Giorgio Trovato on Unsplash