How to Migrate from Jira to Plane

Jira's pricing ($8.15-16/user/month) and complexity drive teams to look for alternatives. Plane is the modern, open source project management tool with a cleaner UX and no per-user fees. Here's how to migrate.

What Transfers

Jira Feature	Plane Status
✅ Issues/tickets	Import via Jira integration
✅ Issue titles and descriptions	Full text preserved
✅ Labels/tags	Mapped to labels
✅ Priority levels	Mapped to priority
✅ Assignees	Mapped to members
✅ Status/workflow	Mapped to states
✅ Comments	Imported
⚠️ Attachments	Links preserved, files may need re-upload
⚠️ Custom fields	Partial support
❌ Automation rules	Rebuild in Plane
❌ Boards configuration	Recreate views
❌ Dashboards	Recreate in Plane
❌ Confluence links	Update manually

Step 1: Deploy Plane

# Self-hosted with Docker
git clone https://github.com/makeplane/plane.git
cd plane
./setup.sh

# Follow the interactive setup
# Configure database, Redis, storage
docker compose up -d

Or use Plane Cloud (free for up to 5 members).

Step 2: Import from Jira

Plane has a built-in Jira importer:

1. Open Plane → Settings → Imports
2. Select Jira
3. Enter your Jira instance URL and API token
4. Select the project(s) to import
5. Map Jira statuses → Plane states
6. Map Jira users → Plane members
7. Start import

Generate Jira API Token

1. Go to id.atlassian.com/manage-profile/security/api-tokens
2. Click Create API token
3. Name it "Plane Migration"
4. Copy the token

Step 3: Map Workflows

Jira Status	Plane State
To Do	Backlog
In Progress	In Progress
In Review	In Review
Done	Done
Won't Do	Cancelled

Plane uses customizable states. Create states that match your team's workflow before importing.

Step 4: Set Up Plane Workspace

Jira Concept	Plane Equivalent
Project	Project
Board	Board view
Backlog	Backlog
Sprint	Cycle
Epic	Module
Component	Label
Version/Release	Module
Filter	View (saved filters)
Dashboard	Analytics

Key Differences

Cycles vs Sprints — Plane's Cycles are similar to Jira Sprints. Create a cycle, add issues, set start/end dates.

Modules vs Epics — Plane's Modules group related issues. Use them like Jira Epics for feature-level tracking.

Views — Plane's saved views replace Jira's saved filters. Create views for your common queries.

Step 5: Invite Team

1. Settings → Members → Invite
2. Set roles: Admin, Member, Guest
3. Share the Plane URL with your team
4. Walk through key differences from Jira

Cost Savings

Team Size	Jira Standard	Plane Self-Hosted	Savings
10 users	$82/month	$10/month (VPS)	$864/year
25 users	$204/month	$20/month	$2,208/year
50 users	$408/month	$40/month	$4,416/year
100 users	$816/month	$80/month	$8,832/year

Migration Timeline

Week	Task
Week 1	Deploy Plane, import Jira data, configure workflows
Week 2	Set up views, invite team, run both tools
Week 3	Primary work moves to Plane
Week 4	Sunset Jira, archive data

Self-Hosting Plane: Infrastructure and Deployment

Plane's self-hosted deployment is one of the more involved setups in the open source project management space, but the interactive setup script makes the process manageable even without deep Docker expertise.

The Plane stack consists of several containers: the Next.js frontend, a Django API server, a Celery worker for background task processing, Redis for the task queue and caching, and PostgreSQL as the primary database. The full stack runs comfortably on 4 GB of RAM — a Hetzner CX32 at $14 per month handles small to medium teams (up to 50 users) without issue. For larger teams or high-throughput environments with many concurrent users editing issues simultaneously, 8 GB is the recommended starting point.

The setup script (./setup.sh in the Plane repository) handles Docker Compose file generation, prompts for domain configuration, database credentials, and S3-compatible storage settings. File attachments in Plane — screenshots attached to issues, design files, documents linked in comments — require S3-compatible storage. Backblaze B2, Cloudflare R2, and MinIO (self-hosted) are all viable options. MinIO is particularly interesting for organizations that want completely self-contained storage with no external cloud dependencies: a MinIO instance on the same server handles object storage without any third-party service.

Reverse proxy configuration follows the standard pattern for Next.js applications: Caddy or Nginx proxies both the frontend (default port 3000) and the API server (default port 8000) under the same domain, with separate location blocks routing /api/ traffic to the Django backend. The setup script generates a starter nginx.conf that handles this routing correctly for most deployments. TLS via Let's Encrypt is the standard approach, and Caddy's automatic HTTPS makes this particularly simple.

Database backups should be automated from day one. A daily pg_dump of the Plane database compressed and shipped to Backblaze B2 via rclone costs essentially nothing and protects all your project history, issue data, and comments. The backup script from the Vaultwarden section of this guide is a useful template — adapt it to the Plane database name and credentials. Test restoration from backup before relying on the instance for production work.

For teams already running a self-hosted PaaS layer, Plane is available as a one-click application on Coolify and as a managed service on Elestio. The Coolify path is particularly convenient: the template handles the multi-container orchestration, reverse proxy, and environment configuration through the Coolify dashboard. See the best one-click deploy platforms for a comparison of deployment management options.

Workflow Redesign: Jira Concepts vs Plane Concepts

The conceptual differences between Jira and Plane go beyond terminology. Understanding how Plane thinks about project work helps you design a workflow in Plane that takes advantage of its strengths rather than trying to recreate Jira's patterns exactly.

Jira's model centers on issues organized into projects, with sprints (Scrum) or kanban boards driving active work. The backlog is a first-class concept: issues live in the backlog until they are pulled into a sprint. Epics group related issues and can span multiple sprints. Custom workflows with complex status transitions, mandatory fields, and screen configurations add power but also complexity. The result is a highly configurable system that many teams underuse because the configuration overhead is high.

Plane's model is simpler by design. Issues are the core unit, and they live in projects. Views are flexible — you can look at issues as a list, board, spreadsheet, or calendar — without committing to a single workflow type. Cycles (Plane's sprints equivalent) are time-boxed containers you add issues to, but unlike Jira sprints, they are optional. You can run a board-based kanban workflow without ever creating a cycle. Modules group issues by feature or theme, equivalent to Jira epics but with a slightly different UX: you create a module first, then add issues to it, rather than setting an epic field on each issue.

The state system in Plane is customizable per project. Default states include Backlog, To Do, In Progress, and Done, but you can add states like In Review, Blocked, or Pending Design approval. States are grouped into categories (Unstarted, Started, Completed, Cancelled), and Plane's analytics use these categories for velocity tracking. Mapping your Jira workflow statuses to Plane states before the migration — and cleaning up any Jira statuses that accumulated over years of workflow evolution — is worth the time investment.

Label usage in Plane replaces several Jira concepts simultaneously: Jira components, Jira labels, and some custom field use cases all map to Plane labels. If your Jira projects use components heavily for filtering and assignment, plan to recreate those as Plane labels with a consistent naming convention before the import, so the imported issues can be tagged correctly during the mapping process.

Team Adoption Strategy and Change Management

Technical migration is the easier half of switching from Jira to Plane. The harder half is getting teams that have used Jira for years to change their habits, especially if those habits are deeply embedded in how they run standups, sprint ceremonies, and stakeholder reporting.

The most successful migration approach is parallel running with clear sunset date. Announce a specific date when Jira goes read-only. Run both systems simultaneously for two to four weeks. Encourage the team to use Plane for new work while Jira remains available for referencing historical data. This approach reduces resistance because team members have time to get comfortable with Plane before the safety net is removed.

Identify champions in each team — typically the engineer or PM who is most enthusiastic about the change — and have them become the Plane experts. Champions help their teammates with workflow questions, validate that the import was complete, and advocate for Plane in team retrospectives. Bottom-up adoption driven by internal champions is more durable than top-down mandates.

Address the tooling gap proactively. If your team uses Jira's GitHub integration heavily (linking commits and PRs to issues), evaluate Plane's GitHub integration before migration and configure it during the parallel period. If you have Jira dashboards that managers rely on for portfolio visibility, recreate equivalent views in Plane's analytics before cutting over. Eliminate surprises during the hard cutover.

The cost savings reinforce adoption. A 25-person team saving $2,208 per year by moving from Jira Standard to self-hosted Plane represents meaningful budget that can be redirected to engineering tooling, team benefits, or product development. Making these savings visible to the team builds goodwill around the change and frames the migration as investment in the team rather than cost-cutting. The how much you can save switching from Jira to Plane analysis breaks down the ROI in detail for teams at different sizes. For teams also considering the broader Atlassian stack, the best open source alternatives to Jira article covers additional options beyond Plane, including Linear-style alternatives and GitLab's built-in project management, which may suit specific team workflows better.

Plane's Project Viability and Community Trajectory

Plane is venture-backed — the company raised a $6.7 million seed round in 2023 — which funds both the cloud product (plane.so) and the open source self-hosted version. The dual commercial/open source model is sustainable and has delivered a development pace that has seen Plane grow from an early-stage project to a production-ready Jira alternative in under three years. With over 30,000 GitHub stars and hundreds of contributors, the community is active and growing.

The project's governance model is transparent. The roadmap is public, feature requests are tracked in GitHub Issues, and the development team is responsive in the community Discord. For organizations evaluating long-term commitment to a project management tool, Plane's combination of commercial backing, active development, and open source licensing provides reasonable assurance of continuity.

Plane's API is comprehensive and well-documented, enabling integrations that are not available through the built-in UI. Teams have built GitHub Actions workflows that automatically create Plane issues from bug reports, Slack bots that post issue updates to team channels, and reporting scripts that export sprint data to spreadsheets for stakeholder communication. The open API also means that if Plane does not implement a specific feature you need, you can build it yourself — a flexibility that proprietary project management tools cannot offer.

For teams running documentation alongside their project management — the natural companion to a ticketing system — Plane integrates well with self-hosted wiki tools. Linking a Plane module to an Outline or BookStack documentation section that describes the feature's design creates a bidirectional connection between the work tracking layer and the knowledge layer of your engineering organization. The best open source note-taking and wiki tools covers the documentation side of this equation for teams looking to replace Confluence alongside Jira.

---

Compare project management tools on OSSAlt — features, pricing, and self-hosting options side by side.

See open source alternatives to Jira on OSSAlt.