YouTrack Server licensing change: what perpetual license owners need to decide
If you hold a perpetual YouTrack Server license, JetBrains moved the product to annual subscriptions on June 23, 2026, so your next decision is about the license you already own. You have three paths: renew under the subscription model, stay on the last release your perpetual license covers, or move to self-hosted OpenProject, Plane or Redmine. Renewal fits teams whose workflows, query language and integrations depend heavily on YouTrack and whose budget already accounts for a recurring fee. Staying on your covered release works as a bridge while you evaluate, but it is a time-limited position, not a long-term plan. Moving is the right route when you want no recurring license fee for the tracker itself and are willing to take on hosting and upkeep.
Before you choose, get the facts in writing from JetBrains. Confirm which release your perpetual license covers, whether that coverage includes security fixes and how long they continue, what the subscription conversion terms are for your user count, and whether any add-ons such as Helpdesk agents are priced separately. Also check how your license is recorded in your JetBrains account, because the license key and entitlement will matter for any later upgrade or downgrade. Keep the answers with your procurement records. If you stay on an older line, track its security support in the same way you would for any self-hosted product, since open-source lines also reach end of support at different points.
Use the answers to test each option against your own requirements. List the features your teams rely on, including agile boards, custom workflows, Helpdesk, single sign-on and LDAP group sync, and check which of these sit in paid tiers on the candidate platforms. OpenProject places SSO and LDAP synchronization in its Enterprise plans, Plane lists LDAP as an Enterprise feature, and Redmine relies on its built-in LDAP authentication with plugins for many agile and SSO needs. Run a pilot on a copy of one active project before you commit, and confirm each gap with the vendor or the community rather than assuming a match.
What a licensing decision has to satisfy
A renewal decision turns on six conditions that are easy to overlook until a subscription lapses. Each card names one condition, the fact you can check now and the term to confirm with JetBrains before you sign. Read them together, because the answers on access and support decide how urgent an exit plan becomes.
Access to the installed release
Confirm whether your perpetual license still lets you run the release you installed if you do not renew, and whether that right covers future restarts, reinstalls and new hosts. A lapse can end the right to run newer builds while the old one keeps working, or it can end access altogether. Ask JetBrains for this in writing, and record your build number and license dates so you can show what you are entitled to. This answer decides whether staying on your current release is a viable option.
Security updates after renewal
Ask JetBrains which fixes and security updates a renewed or lapsed license receives, and for how long. Redmine's public support policy shows the range you should expect from a vendor: its 7.0.x line gets new features and security updates, 6.1.x gets only bug fixes and security updates, and 6.0.x gets only important security updates. If you stay on an old YouTrack build, you carry the patch risk yourself, so ask whether advisories will cover your release.
Data ownership and exit terms
Your issues, comments, attachments and workflow configuration live on your servers, but the exit path depends on what you can export and in which format. Ask JetBrains which export formats are supported, whether attachments travel with issues, and whether a lapsed license restricts exports. Test an export of one sample project before the renewal deadline. The importers for OpenProject's Jira Migrator and Plane's listed sources do not read YouTrack directly, so an export file is usually the bridge to any target tool.
Named users and helpdesk agents
Count named users, service accounts and helpdesk agents separately, because each may be billed differently under the new subscription model. Our brief lists YouTrack Helpdesk as free for 3 agents and charged per agent beyond that, so confirm current counts, user packs and agent fees with JetBrains. On the OpenProject side, Enterprise on-premises is priced per named user per month, with Basic at 5.95 euros per user. Community has no per-user fee but omits the Enterprise features.
SSO, LDAP and directory integration
List every login path your renewal must keep working, including single sign-on, LDAP group sync and links to source control or CI. OpenProject lists SSO with SAML, OIDC, CAS, Kerberos and Okta, along with LDAP group synchronization, as Enterprise features. On Plane, SAML and OIDC start at the Pro plan, and LDAP sits in Enterprise. Redmine supports multiple LDAP authentication sources, but other SSO options usually depend on plugins, so test them before you choose.
Upgrade and operations work
Staying on a self-hosted tool or moving to one both create recurring work: backups, upgrades, plugin compatibility and database maintenance. Redmine's upgrade guide asks you to back up the database and uploaded files, copy configuration, uploads and plugins to the new installation, then run the migrations and restart. OpenProject's sizing guide starts at 4 cores and 4 GB RAM for up to 200 users. Name the person who owns each step before you compare total cost.
When renewing YouTrack Server still makes sense
Renewing is the right call when your team depends on YouTrack features that would take months to rebuild elsewhere. A perpetual license gave you the right to run a release you bought indefinitely. An annual subscription instead gives you the right to run covered releases and receive updates for the term, and it stops at the end of the term unless you renew. Teams with heavily customized workflows, scripted automations, custom fields tied to reports, or a large body of YouTrack-specific query language and integrations often find that the cost of rewriting those pieces exceeds the subscription fee for several years. Before you decide, confirm the exact scope in the written terms with JetBrains or your reseller.
Read the order form and license agreement for three things. First, which releases are covered, and whether security fixes for older branches are included after the term ends. Second, your update rights during the subscription, including whether major version upgrades are covered or only minor releases. Third, the renewal pricing mechanism and how it applies to user packs and add-ons such as Helpdesk agents. Ask for these answers in writing, because a subscription's entitlements can differ from what a perpetual license implied. Also confirm whether your current perpetual license keeps its last covered release running on your own servers after the change, since that determines how much runway you have.
Renewal is a holding position, not a permanent answer. Record the renewal end date, the last covered release and the features you rely on most, then set a review point well before the term expires. If you choose to stay, plan a backup and upgrade routine on your own schedule, and keep a current export of issues and attachments so a later move is possible without an emergency. The migration options are covered in the sections that follow.
Staying, renewing or replacing by situation
If your team is small and your perpetual license covers a release you already run, staying put is the lowest-effort option for now. The open question is how long that release remains useful to you, and the answer depends on support terms that only JetBrains can state. Confirm in writing which release your license covers and what updates or support it includes, then decide how long you can run it safely.
- Confirm coverage first: Get the covered version and its support terms from JetBrains before you rely on them.
- Build a fallback trial: Redmine 7.0.2 and 6.1.5 are current stable lines under GPL v2 with no paid edition, so a test install gives you a concrete comparison.
- Test OpenProject Community: The free edition includes work packages, Gantt charts, agile boards, time tracking and dashboards, with community support only.
- Price the operating work: Hosting, administration, backups and upgrades recur whatever the license fee is, so include them in every option.
First step: export your current issues and a sample of projects, then stand up a small test instance of one candidate and check whether your team can work in it without paid support.
Teams with single sign-on or audit requirements should not decide on price alone, because the identity and logging features differ by platform and by tier. OpenProject lists SSO through SAML, OIDC, CAS, Kerberos and Okta, along with LDAP group synchronization, among its Enterprise features. On self-hosted Plane, SAML and OIDC are available from the Pro plan upward, while LDAP support and API-enabled audit logs are Enterprise features. Redmine supports multiple LDAP authentication sources under GPL v2, but other SSO options depend on plugins you would need to evaluate and maintain.
- Map controls to features: List the access, logging and retention controls your auditors expect, then match each one to a feature and the tier that includes it.
- Check OpenProject pricing: Its pricing page lists Enterprise on-premises plans per named user per month, starting at 5.95 euros for Basic, so confirm which tier carries the SSO and LDAP features you need.
- Check Plane tier boundaries: Confirm whether SAML and OIDC on Pro meet your requirements and whether audit logs need Enterprise.
- Review Redmine plugins: Identify any SSO or logging plugin, check its maintenance status, and include its upgrade effort in your plan.
First step: send each candidate a written list of the identity and logging requirements and ask them to confirm which edition provides each one. DeployOpen can prepare the configuration and evidence for your assessment, but independent auditors issue any audit report.
Teams with heavily customized workflows face the highest migration risk, because custom states, fields, roles and links rarely carry over unchanged. Redmine offers flexible role-based access control, custom fields, email-based issue creation and plugin extension, which gives strong control but means every plugin must be checked on each upgrade. OpenProject's Jira Migrator, as a benchmark for what a tracker migration can carry, imports basic custom fields and standard statuses and types. Plane's importers, which run on Plane Cloud and on the self-hosted Commercial Edition, cover several sources, so confirm whether a YouTrack export maps to Plane's model before choosing it.
- Inventory the workflow: List every state, transition, custom field, link type and permission rule that your teams depend on.
- Run a mapping test: Export one representative project and see which fields, comments and attachments arrive intact on each candidate.
- Account for plugins: For Redmine, count the plugins you need and confirm each has a version for your target release.
- Plan for manual rework: Anything that does not map cleanly will need a rebuild or a documented change for users.
First step: choose one complex project, export it, and test the import on a sandbox instance before you decide which platform to move the rest to.
Air-gapped networks and strict data residency rules change the question from features to deployability. Each candidate has its own dependency chain that must run inside your boundary. Plane offers a proprietary Airgapped edition and documents air-gapped installs, but its self-hosted stack also needs PostgreSQL, Redis or Valkey, RabbitMQ and S3-compatible object storage such as MinIO. OpenProject ships Docker images, .deb and .rpm packages for 64-bit Linux and Helm charts, and requires PostgreSQL 16 or later with the pg_trgm, btree_gist and unaccent extensions. Redmine runs on PostgreSQL, MySQL 8.0 to 8.4, SQL Server 2012 or later, and SQLite, which the installation guide does not recommend for multi-user production.
- Document the boundary: Write down which networks, storage and identity systems the tool may reach.
- Mirror every dependency: Plan internal copies of packages, container images, Helm charts and database extensions.
- Confirm offline licensing: Ask JetBrains whether your license terms permit continued use without outside connections, and confirm the answer in writing.
- Ask for an offline procedure: Request a complete offline install and upgrade document from each candidate.
First step: produce a dependency list for each candidate and confirm which items you must mirror before any pilot starts.
How OpenProject, Plane and Redmine compare with YouTrack Server
This table compares the three replacement options on the points that decide a renewal: licence, free tier, self-hosting, sign-in, boards, planning and migration. Items marked as confirm were not covered by researched sources, so check them with the vendor or in a test install before you commit. The main takeaway is that the free tiers differ in what they include, so SSO and LDAP needs often decide the edition.
| Capability | OpenProject | Plane | Redmine |
|---|---|---|---|
| Licence | GPL-3.0 for Community edition | AGPL-3.0 for Community edition; Commercial and Airgapped are proprietary | GPL v2, with no paid edition |
| Free tier | Community edition is free with community support | Community edition matches the Cloud Free feature set | Full product is free; costs are hosting, plugins and staff |
| Self-hosting method | Docker (recommended), .deb and .rpm packages, Kubernetes with Helm | Docker Compose, Kubernetes with Helm, Podman and air-gapped installs | Ruby on Rails application installed by hand or by packages; confirm your path |
| SSO and LDAP | SSO and LDAP group sync are Enterprise features | SAML and OIDC on Pro and above; LDAP on Enterprise | Multiple LDAP authentication built in; confirm SSO options |
| Agile boards | Included in Community edition | Confirm board and cycle features in your edition | Confirm whether boards need a plugin |
| Gantt and time tracking | Gantt charts and time tracking included in Community edition | Confirm Gantt and time tracking support | Gantt charts, calendars and time tracking are built in |
| Migration from YouTrack | Jira Migrator is for Jira only; confirm YouTrack export options | CSV importer on the Commercial edition; confirm YouTrack field mapping | No supported YouTrack importer; confirm with a test import |
How a move off YouTrack Server runs in practice
The sequence below turns a move off YouTrack Server into a set of checked stages, so each target tracker receives data that has been inventoried, tested and reconciled before any team switches over. Each step closes with an output you can review.
Inventory projects, fields and integrations
Someone who administers YouTrack lists every project, its workflow states, custom fields, tags, saved queries, agile boards, and each integration such as Git hooks, CI notifications or the Helpdesk mailbox. Record which items are in active use and which are legacy. Note any custom fields with values that have no obvious equivalent on the target. The output is a signed-off inventory that defines what the migration must carry across, and what it may leave behind with an archived export.
Export issues, comments and attachments
Export issues from YouTrack with their fields, comments, links and attachments, and keep the export in a location on your own servers. Confirm with your YouTrack administrator which export format and scope your installed release supports, since options vary by version. Store a checksum or record count per project so the later import can be compared against the source. The output is a complete, dated export set that remains the reference copy until the cutover is finished.
Run a test import on a non-production instance
Stand up the target tracker on a non-production server, using the same major version you plan to run in production, and import one representative project first. Check the importer documentation for the target you chose, because support differs: OpenProject's Jira Migrator, for example, is documented as beta and covers only specific Jira versions, so you should confirm whether any YouTrack path exists before relying on it. Where no native importer exists, plan a scripted import through the target's API. The output is a test report listing what imported, what was skipped and what needed manual correction.
Map states, fields and permissions
Using the test report, map each YouTrack state and workflow transition to a status or work package type on the target, and map custom fields to native fields or to documented custom fields. Decide how roles and per-project permissions will be recreated, and where single sign-on or directory synchronization is needed, confirm which edition provides it. Assign an owner for each mapping decision. The output is a written mapping specification that the project leads approve before the full import.
Carry attachments and verify the data
Move attachments in a separate pass so large binary files do not block issue data, and confirm that each file opens and is linked to the correct issue. Compare issue counts, comment counts and attachment counts per project against the export record, and sample issues from each project for field accuracy. Resolve discrepancies in the mapping, then rerun the affected project. The output is a reconciliation sign-off per project showing matching counts and reviewed samples.
Run both trackers until links are updated
Keep YouTrack read-only or available in parallel for a defined period agreed by the project leads, while teams begin work in the new tracker. Update commit references, CI notifications, wiki links, email routing and bookmarks that point to old issue IDs, and record which links remain in YouTrack. Confirm with the owners of each integration when their updates are complete. The output is a link-update checklist with each dependency marked done, and a documented date when YouTrack access is withdrawn.
Retain the archive and close the migration
Keep the final YouTrack export and reconciliation reports in a controlled archive that meets your records retention policy, and confirm with your compliance owner which retention period applies. Remove YouTrack Server access only after the archive is verified and the license position is settled with JetBrains. Record the lessons from the test import in the runbook for the next project. The output is a closed migration record that shows the archive location, the approvals and the retained evidence.
Deploying OpenProject, Plane or Redmine on your own servers
Each candidate has a different deployment shape, and that shape decides how much operational work lands on your team. OpenProject supports Docker-based installation, which the project recommends, plus .deb and .rpm packages for 64-bit Linux and Kubernetes with Helm charts for horizontal scaling. Packaged installs support Ubuntu 22.04, Debian 12, CentOS or RHEL 9.x and SUSE Linux Enterprise Server 15. OpenProject officially supports PostgreSQL 16 or later and requires the pg_trgm, btree_gist and unaccent extensions, so confirm that your database platform can provide them before you size the server. The sizing guide is a starting point only: check it against your user count, since the published tiers run from 4 cores and 4 GB RAM for up to 200 users to 16 cores and 16 GB for about 1,500 users.
Plane is heavier to run. Its documented methods include Docker Compose for small and mid-size teams and Kubernetes with Helm for high availability, along with Podman and air-gapped installs. A self-hosted deployment depends on PostgreSQL, Redis or Valkey, RabbitMQ and S3-compatible object storage such as MinIO. The Helm chart can point each of these at an external managed service, which many regulated teams prefer for backups and patching. Decide early whether you need the Community Edition or the Commercial Edition, because the Kubernetes guide installs the Commercial Edition and the paid tiers require switching editions. Redmine has the lightest footprint: it runs on Ruby on Rails 8.1 for the 7.0 line, which supports Ruby 3.2, 3.3, 3.4 and 4.0 but not JRuby. It supports PostgreSQL, MySQL 8.0 to 8.4 with READ COMMITTED isolation, SQL Server 2012 or higher and SQLite, though the installation guide says SQLite is not suited to multi-user production.
Upgrades and backups are the duties most often underestimated. For Redmine, the upgrade guide calls for backing up the database and uploaded files, copying configuration, uploads and third-party plugins to the new installation, then running rake db:migrate and rake redmine:plugins:migrate before clearing the cache and restarting. Plugin compatibility is the usual blocker, so check each plugin against the target version first. OpenProject and Plane ship their own upgrade procedures with each release, and the OpenProject release notes and Plane release page show how frequently they change. Set a written backup schedule covering the database, attachments and object storage, test restores on a schedule, and ask your implementation partner or vendor to confirm the upgrade path from your current version before you commit.
Questions buyers ask before choosing a path
What does each licensing path cost, and what drives the total?
The total depends on recurring costs, not the first invoice. For YouTrack Server, the cost is the JetBrains subscription for your user count, plus any Helpdesk agent fees under the new model, which your JetBrains quote should itemize. Self-hosted alternatives add hosting, staff time, backups and upgrades. OpenProject Community is free with community support, while Enterprise on-premises is priced per named user per month: Basic at 5.95 euros and Professional at 10.95 euros with a 25-user minimum, and Premium at 15.95 euros with a 100-user minimum (OpenProject pricing). Plane Community is free, but paid self-hosted plans need the Commercial Edition. Redmine has no paid edition, so its cost is hosting, implementation, plugins and maintenance. Ask each vendor for a quote on the same user count and the same time horizon so the comparison holds.
How long does a YouTrack migration take, and what does it depend on?
No duration can be stated without a written scope, because the work depends on what you migrate. The main drivers are the number of projects and issues, how much history you keep, the number of custom fields, workflows and states, the volume of attachments, and which integrations must keep working. Importer coverage also matters. OpenProject's Jira Migrator is in beta and supports only Jira Data Center, so it does not cover a YouTrack move directly. Plane offers a CSV importer on the Commercial Edition. Redmine's built-in importers for Trac and Mantis are obsolete, and its third-party scripts are neither tested nor supported, so expect custom mapping work. Plan a parallel-run period before cutover. Ask for a scope that lists item counts, a field mapping table and a cutover plan.
What does the team need to run a self-hosted tracker?
You need a platform owner, someone who administers Linux and the database, and a person who runs upgrades and backups. OpenProject recommends Docker for installation and also ships packages for Ubuntu 22.04, Debian 12, RHEL 9 and SUSE Linux Enterprise Server 15. It requires PostgreSQL 16 or later with the pg_trgm, btree_gist and unaccent extensions. Its sizing guide starts at 4 cores and 4 GB RAM for up to 200 users. Plane needs PostgreSQL, Redis or Valkey, RabbitMQ and S3-compatible object storage, and it can run with Docker Compose or Kubernetes with Helm. Redmine 7.0 runs on Ruby 3.2, 3.3, 3.4 or 4.0 and supports PostgreSQL, MySQL, SQL Server and SQLite, though SQLite is not suited to multi-user production. Confirm these requirements against your own platform standards before you size hardware.
Can our own engineers do the migration without an implementation partner?
Yes, if your team has the skills and capacity, and the answer depends on that capacity more than on the software. Installing OpenProject, Plane or Redmine is documented well enough for a skilled Linux team to follow. The harder work is the data: exporting YouTrack issues with history and comments, mapping states and custom fields, carrying attachments and validating results. An implementation partner adds value when you need a fixed-scope plan, hardening, a tested backup and restore routine, an upgrade runbook and documentation that outlives the project. DeployOpen plans, implements, integrates, hardens, backs up, upgrades and documents self-hosted platforms in your own infrastructure. Its engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts, and ongoing support is available as a retainer.
How do SSO and LDAP work on OpenProject, Plane and Redmine?
Each platform handles identity differently, so confirm the path for your identity provider before you choose. On OpenProject, the pricing page lists single sign-on through SAML, OIDC, CAS, Kerberos and Okta, plus LDAP group synchronization and SCIM provisioning, as Enterprise features (OpenProject pricing). Confirm exactly what the Community edition supports. On self-hosted Plane, SAML and OIDC are available on the Pro plan and above, and LDAP support is an Enterprise feature. Redmine lists multiple LDAP authentication support among its core features, but SSO protocols beyond that depend on plugins, so confirm each plugin's maintenance status before you rely on it. Document which accounts, groups and roles map to which permissions, and test deprovisioning as carefully as provisioning.
Is staying on our last covered YouTrack Server release safe long term?
It can work for a defined period, but the answer depends on your support status with JetBrains, which should be confirmed in writing for your specific license. Ask JetBrains which security fixes apply to your last covered release, whether that release supports your operating system and database versions, and what happens to your access to updates after the coverage ends. Staying put without a documented exit date increases risk, because unpatched components accumulate over time. Redmine's download page offers a useful model for checking any tracker: 7.0.x receives new features and security updates, 6.1.x receives only bug fixes and security updates, 6.0.x receives only important security updates, and 5.1.x and older are unsupported. Ask for the equivalent table from your vendor and record the date you plan to leave.
What compliance evidence does a self-hosted tracker produce?
A self-hosted tracker produces the records you choose to keep, so decide the evidence list before go-live. Typical items include who has access and when access was reviewed, the change history on work items, backup and restore test records, upgrade records and the configuration baseline. Audit logging varies: Plane lists API-enabled audit logs as an Enterprise feature, and OpenProject's identity features sit in its paid Enterprise plans. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. Independent auditors and certification bodies do that work. If your organization follows a specific control framework, ask your auditor which records they will sample and build the collection process around those samples.
How DeployOpen plans a move off YouTrack Server
DeployOpen plans, implements, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For a YouTrack Server licensing decision, we start by agreeing what the organization needs to keep running, then build the replacement or the stay-or-renew path in the client's own environment.
How we scope
- Inventory the YouTrack Server release, user count, projects, workflows, integrations and any Helpdesk agents in use
- Record which teams depend on boards, Gantt views, time tracking, wiki pages and repository links
- Agree in writing whether the engagement covers staying on the current release, renewing, or moving to OpenProject, Plane or Redmine
- Confirm the deliverables, timeline and exclusions in a fixed-scope document before work starts
How we build
- Stand up the chosen platform in the client's cloud account, data center or air-gapped network
- Configure projects, roles, single sign-on and directory synchronization against the client's identity provider
- Test exported data for issues, comments, attachments and custom fields on a copy before any production cutover
- Run security testing on the new platform before users are moved to it
How we hand over
- Document the configuration, access model, backup routine and upgrade steps for the client's own administrators
- Provide a written record of which data was migrated, which was not, and why, so gaps are known
- Hand over backup and restore procedures and confirm they have been exercised by the client's team
- Agree a plan for running both trackers in parallel until links and bookmarks are updated
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Retainers can cover platform patching, release upgrades and plugin maintenance on the client's schedule
- Ask for a written support scope that names response expectations before signing any retainer
- Compliance readiness work prepares systems and evidence, while independent auditors issue any attestation

