Height alternative after the 2025 shutdown

A Height alternative now has to solve two problems. It must fit the work Height used to hold, and it must help you rebuild after the service closed. Height stopped operating on September 24, 2025. If you still have an export, preserve it before testing tools. If you do not, reconstruct active work from linked repositories, documents, calendars, and team messages instead of trying to recreate every historical task.

Hypertask is worth considering when external AI agents now do part of the work and people need a focused board for claims, progress, and review. Linear or Shortcut may fit product and engineering teams. ClickUp fits broader cross-functional operations. Notion fits teams that want tasks close to documents and databases.

There is no live Height workspace to trial beside these products. The right comparison uses the workflow your team remembers and the records you still control.

Height’s shutdown is complete

Height announced its sunset in March 2025 and ended service on September 24, 2025. Shortcut’s Height alternative announcement records the date, and its switch-from-Height page remains online.

This matters because some current comparison pages still describe Height in the present tense. You cannot sign up, run a side-by-side trial, or rely on a fresh export from the old service. A 2026 migration starts with whatever your team saved before shutdown and whatever traces remain in connected systems.

Height was known for combining project tasks, collaboration, customizable workflows, and an AI-led direction in one polished product. Different teams used different parts of it. One replacement may cover issue tracking while missing the lightweight chat and flexible views another team valued.

Write down the three actions your team performed most often. Examples include triaging incoming issues, planning a product cycle, discussing work on the task, or letting automation keep status current. Those actions are a better filter than an old feature list.

Preserve the workflow, not the old interface

Teams remember a discontinued product through the parts that saved time. Capture those before product demos blur the memory.

Interview three kinds of user if they existed in your Height workspace:

• The person who created and organized projects.
• The person who updated tasks every day.
• The person who reviewed status without doing the work.

Ask each person to describe the last real project they ran in Height. Which view did they open first? Which fields did they trust? Where did decisions live? What did they ignore? Which automation would create manual work if it disappeared?

Turn the answers into a short acceptance list. For example, a product team may need fast issue creation, repository links, cycles, and a reliable roadmap. An operations team may need intake forms, custom fields, and cross-project dashboards. A team using external agents may need structured task access, separate agent identities, and a human review queue.

Do not recreate every Height field because it existed. Keep the state that still changes a decision. Historical fields can remain in the archive while the new board starts with a smaller current model.

Height alternatives at a glance

All five products can be good choices. The decision is about the operating model you want now, not which product looks most like Height in a screenshot.

Pick the shortlist from your current work

Use a simple decision path before booking demos.

Start with Linear or Shortcut when most tasks belong to software delivery. Compare issue creation, repository links, cycles or iterations, roadmaps, and the review flow your engineers use. Put Shortcut first if a saved Height export makes its migration path relevant.

Start with Hypertask when external agents now create a meaningful share of output. Test whether each agent can claim work under its own identity, leave evidence on the task, and reach the right human without a copy-and-paste relay.

Start with ClickUp when several departments need one configurable work platform. Include the person who will own fields, views, dashboards, permissions, and automations in the pilot. Administration is part of the product cost.

Start with Notion when project records need to live beside specs, research, meeting notes, and structured databases. Test daily task changes as carefully as document editing.

Keep the shortlist to two products. A five-product pilot creates more setup work than evidence. If neither candidate fits, return to the acceptance list and identify the requirement that eliminated them before adding another option.

Hypertask for agent-run task execution

Hypertask is a focused project board where people and external AI agents use the same tasks. Agents can connect through a first-party MCP server or the scoped @hypertask/hypertask_cli package.

An agent can read the available queue, claim a task, post progress, track time, and return evidence under its own identity. The human reviewer receives a task-anchored inbox item instead of watching the agent session or copying its result into the board.

This fits a team whose workflow changed since Height shut down. In 2025, you may have wanted AI inside the project tool to maintain work. In 2026, you may also run coding, research, support, or marketing agents outside the tool. Those workers need structured board access and a review path.

Hypertask does not try to recreate Height’s complete product shape. It is not a company wiki, a portfolio suite, or a flexible database canvas. If Height held complex roadmaps, rich custom fields, resource planning, or documentation, keep those needs in the comparison.

Hypertask fits when:

• External agents already execute real tasks.
• Agent identity and an auditable task history matter.
• Humans review work asynchronously from one queue.
• A small team prefers a strong default over a highly configurable workspace.

Choose another option when:

• Deep product roadmaps and engineering planning are the central job.
• Several departments need different workflow schemas and dashboards.
• Documents and relational databases should live in the same product as tasks.

The AI agent task management guide shows the claim, update, report, and close loop. Check Hypertask pricing for current trial and plan terms.

Linear for product and engineering teams

Linear is a strong Height alternative for software teams that want a fast, opinionated system around issues, projects, and product delivery. Its product model is closer to engineering planning than to general company work.

Choose Linear when the board primarily tracks bugs, features, cycles, and product initiatives. Teams with Git-based delivery and a clear product process may value that focus more than a flexible all-company workspace.

The tradeoff is scope. Marketing operations, client delivery, knowledge management, and mixed department workflows may need another system or a deliberate adaptation. External-agent access also deserves a real workflow test. Confirm how your agents authenticate, claim work, post evidence, and reach a reviewer.

The Linear alternative comparison covers its product-development strengths beside Hypertask’s human-agent task loop.

Shortcut for software planning and a Height import path

Shortcut targets software teams and product development. It is the only option in this shortlist with a public switch-from-Height page still available after the shutdown.

That makes it the first place to ask when you have a saved Height export and want a supported migration path. Confirm what the current importer accepts, which fields transfer, and whether the service can help with an old file. Public pages can outlive an importer version, so verify before planning around it.

Shortcut fits teams that want stories, epics, iterations, roadmaps, and software delivery context. It may be less natural for company-wide operations that do not follow a product-development model.

Do not choose it only because a migration page exists. Run current work through the product and check the daily actions your team performs most often.

ClickUp for a broad replacement

ClickUp is the broadest replacement in this group. It combines tasks, documents, dashboards, views, automations, integrations, and AI in one work platform.

Choose ClickUp when Height was one part of a larger tool-consolidation problem. Different departments can build different workflows while managers use shared dashboards and reporting. It also has APIs, automations, and MCP access for agent or integration work.

The risk is replacing one product with a workspace that needs its own administrator. Fields, statuses, views, dashboards, automations, permissions, templates, and integrations all need decisions. That breadth earns its cost when teams use it. It becomes overhead when the real workflow is a simple task and review loop.

Read the ClickUp alternative guide for a detailed comparison with Hypertask.

Notion when tasks belong beside documents

Notion fits teams that want project tables beside specifications, meeting notes, wikis, and other knowledge. Its databases can represent tasks in boards, lists, calendars, and related views.

Choose Notion when the connection between documents and structured information matters more than task-processing speed. A small product team can keep the brief, decisions, research, and task table in one workspace.

The tradeoff is that the team designs the system. Properties, views, templates, relations, and status rules need an owner. If Height’s appeal was a polished workflow that required little maintenance, a blank Notion database may feel like a rebuilding project.

The best Notion alternatives by use case includes options for docs, local notes, team knowledge, and task execution. The Notion versus Hypertask guide explains why some teams keep Notion for specs and use a separate board for work.

Recover your work after the export window

The shutdown date has passed, so begin with an inventory. Do not upload the only copy of an old export into the first tool you test.

If you have a Height export

1. Duplicate the original file and keep one copy read-only.
2. Record the format, export date, workspace name, and expected project count.
3. Inspect a sample of tasks, comments, owners, statuses, dates, attachments, and links.
4. Create a mapping from Height fields to the candidate tool.
5. Import one small project or rebuild it manually.
6. Compare record counts and inspect the awkward records before moving more.

An import that succeeds can still lose meaning. A status may map to the wrong column. A former user may become plain text. Comments may lose authorship. Attachments may remain as dead links. Count and inspect.

Ask each vendor whether it supports your exact export format today. Do not assume a generic CSV importer understands Height’s relationships.

If you do not have an export

Rebuild active work, not the whole historical workspace.

Start with systems that linked to Height:

• Git repositories and pull requests can reveal open implementation work.
• Product documents may contain project scopes, owners, and decisions.
• Calendar events can identify current milestones and review dates.
• Team messages may hold links, blockers, and decisions that never reached another system.
• Customer systems can reveal promised work and unresolved requests.

Create one recovery board with three groups: confirmed active, needs owner confirmation, and archive reference. Assign a person to every recovered active item. If nobody can explain why a task still matters, do not make it active by default.

Preserve old Height URLs as reference text even if they no longer resolve. The URL may still appear in messages, commits, or documents and can help connect records during recovery.

Avoid the expensive migration mistakes

The first mistake is choosing the product with the longest feature table. A broad suite can still be wrong for the five actions your team performs every day.

The second is importing the full archive before testing current work. Old tasks inflate search results, create unclear owners, and make record-count checks harder. Keep the archive protected and move active records first.

The third is rebuilding custom fields without an owner. Every new status, view, automation, and permission creates a rule somebody must maintain. Start with the smallest model that can run the pilot.

The fourth is trusting a successful import message. Verify counts, authors, dates, attachments, links, and status mapping. Open records that contain unusual characters, long comments, missing owners, or deleted users.

The last mistake is running two live systems without naming the source of truth. During a pilot, decide whether Height’s recovered archive is read-only and whether the candidate tool owns new status. People should never wonder which copy to update.

Protect customer and company data

Old exports may contain private comments, attachments, email addresses, and access details. Store them according to your current data policy. Remove credentials before sharing a sample with a vendor or support team.

Give the migration worker access only to the data it needs. If an AI agent helps classify tasks, define which fields it may read and where its output can be stored.

Run a one-week replacement pilot

Choose one live project that resembles the work Height used to hold. Avoid the easiest demo project and the messiest company-wide program.

For one week, measure:

• Time to create, assign, and update an ordinary task.
• Whether the team can find decisions and current status without asking in chat.
• How much configuration the workspace owner performs.
• Whether external agents can work without a person relaying every update.
• How reviewers find completed work and request changes.
• Which old Height behavior people still miss after real use.

Keep the candidate only if it improves the daily workflow. A successful import into a product people avoid is another stale board.

Frequently Asked Questions

Is Height still available?

No. Height ended operations on September 24, 2025. Current articles that describe it as a live service are stale. Look for a replacement based on your saved data and current workflow rather than planning a live comparison.

What is the best Height alternative?

Linear and Shortcut fit product and engineering teams. ClickUp fits broad cross-functional work. Notion fits document-centered workspaces. Hypertask fits small teams where humans and external AI agents need one task board and a task-based review inbox.

Can I still export data from Height?

The service has shut down, so do not assume a fresh export is possible. Preserve any export your team saved before the deadline. If you have none, reconstruct active work from repositories, documents, calendars, messages, and customer systems.

Can Shortcut import an old Height export?

Shortcut maintains a public switch-from-Height page. Contact the company with your exact file format and export date before relying on the importer. Verify field mapping and attachment handling with a small project first.

Does Hypertask import Height data?

Plan on a small manual pilot unless Hypertask support confirms a current path for your export. Recreate active tasks, owners, priorities, and sections first. Avoid moving old custom structure that the team no longer needs.

Which Height alternative is best for AI agents?

Hypertask is built around external agents using the same board as people through CLI and MCP. Other products also provide APIs, automations, or MCP access. Test the full loop: authenticate, claim, update, attach evidence, request review, and recover a failed run.

Should we move every old Height task?

Usually not. Move active work and records with legal, customer, or operational value. Keep the original export as a protected archive. Rebuilding years of stale tasks adds noise and makes it harder to verify the records that still matter.

Preserve the old data first. Then run one current project through the two products closest to your workflow.

If external agents are now part of that workflow, start a 14-day Hypertask trial and test one project through CLI or MCP.