Easy Redmine (Easy8) to Redmine migration

easyredmine.com now 301-redirects to easy8.com, verified 2 August 2026. If your renewal is coming up and you are reconsidering, this page covers what the rebrand actually changes, what you can get out of the product, what a fork does and does not owe you, and how the per-user math compares to a flat plan. For the side-by-side product comparison rather than the migration mechanics, see RedminePRO vs Easy8.

What the rebrand means if you are an existing customer

A rename is not, by itself, a reason to leave. What a rename is, reliably, is the moment a vendor's packaging, tiering and pricing get revisited, and the moment an existing customer should read their renewal quote rather than approving it. Three things worth checking on your own account:

• Which tier you are actually on now. Easy8 publishes Essential at €6.90/user/month, Business at €13.90/user/month and Platform at €25.90/user/month, billed annually, with a 10-seat cloud minimum, a practical entry point of €69/month (easy8.com/pricing, 2 August 2026). Rebrands are a common moment for feature sets to shift between tiers. Check that the capability you bought is still in the tier you pay for.
• Your renewal price versus your original price. Per-user pricing compounds quietly. A team that grew from 12 to 30 people did not make thirty separate purchasing decisions. It made one, four years ago, and the bill followed.
• Where the product is going. A rebrand away from a name containing “Redmine” is a signal about how tightly the product intends to stay tied to Redmine. Not a criticism, but if you chose it originally because it was Redmine-based, it is worth knowing.

Per-user versus flat, at your renewal

The arithmetic that drives most of these migrations. Both figures below are list prices as published, Easy8 from easy8.com/pricing and RedminePRO from redminepro.com/pricing, both checked 2 August 2026, no currency conversion applied. Compare the shape of the two curves.

Easy8 columns are the published per-user rate multiplied by seat count, with a 10-seat cloud minimum. They are not quotes, and volume terms may be negotiable at the top of the table. RedminePRO figures are monthly billing. Annual is exactly 10× monthly, so Startup is $290/year, Plus $790/year and Business $1,990/year, with unlimited projects on every plan and 30% off Business for registered non-profits. The point of the table is not the ratio at any single row. It is that one column grows with headcount and the other does not.

What an Easy8 export contains

Easy Redmine/Easy8 is a Redmine fork, which cuts both ways for migration.

In your favor: the foundation is still Redmine's data model. Projects, issues, journals, users, attachments, time entries, custom fields and enumerations sit in tables whose shape a Redmine engineer recognizes. That is why this migration is possible at all, and why it is more tractable than migrating from a product with an unrelated schema.

Against you: everything the fork added is the fork's own. Modules that exist in Easy8 and not in Redmine (extended Gantt and resource management, CRM-style objects, WBS structures, custom dashboards) store their data in tables stock Redmine has never heard of. There is no target to migrate them into. They map to a Redmine equivalent, get rebuilt with a third-party plugin, or get dropped, and that is a decision per module rather than a technical step.

Whatever export route your tier offers, whether a full dump that makes this a clean job or CSV plus an API extraction that makes it a longer one, it still ends with your projects, issues, full journal history, users, attachments, time entries, wiki pages, versions and custom-field values on a standard Redmine instance you control. That is the done-for-you migration either way, quoted after a free assessment.

What does not come across

• Fork-specific modules and their data. Anything that is an Easy8 feature rather than a Redmine feature. Some have good third-party Redmine equivalents. Some do not. Each one is a decision made during the assessment, in writing, before anything moves.
• The Easy8 UI and its saved views. Stock Redmine looks and works like Redmine. Dashboards, custom views and layout configuration are rebuilt, not migrated. Tell your team this before cutover, not on the day.
• Fork-specific custom field types and fork-specific automation and templating. Project templates, task templates and automated behaviors added by the fork have no stock Redmine target and are rebuilt with native workflow rules or plugins.
• Anything version-locked. Plugins must support the target Redmine version, view-overriding themes are version-locked, and core patches do not travel.

None of this is a reason not to migrate. It is a reason to scope it properly, and it is the difference between a migration that lands and one that generates a month of arguments.

What you get on the other side

Stock, current, open-source Redmine, fully managed, in the US, Ireland, France or India, with full Redmine administrator access on your workspace: trackers, workflows, custom fields, roles, plugin configuration. Third-party plugins you choose, rather than modules a vendor chose. Unlimited projects on every plan. From $29/month for up to 25 users.

And no fork lock-in. The reason a fork migration is hard is that a fork's data has nowhere standard to go. Stock Redmine does not have that problem. Its schema is the reference implementation. We provide your full database dump and files archive on request, any time, and it restores onto any Redmine. That is what leaving a fork buys you, and it is worth as much as the price difference. RedminePRO vs Easy8.