Migrate your Easy Redmine data

Projects are the top-level container in Easy Redmine's schema and are fully supported via the REST API. We migrate project metadata, status, and hierarchy including subproject relationships as first-class records.

Issues are the core work-record object and map 1:1 to the upstream Redmine schema. We carry all standard fields — tracker, status, priority, assignee, due date, estimated hours, done ratio — plus custom properties defined at the project level.

Versions (milestones and releases) are stable API resources in Redmine 1.3+. We migrate versions with their target date and status, preserving the linkage to parent Projects and the issues assigned to each version.

Wiki Pages are available via the Alpha API endpoint in Redmine 2.2+. Content migration is text-faithful, but page hierarchy and attachment metadata require manual review post-import because Easy Redmine extends the standard wiki schema.

Time Entries are a Stable API resource introduced in Redmine 1.1. We map hours, activity, spent-on date, and user attribution. Billing rate mapping requires a pre-flight review because Easy Redmine extends time entry fields beyond standard Redmine.

Documents are stored as separate file-attachment records with title and description metadata. The document content itself is migrated as a blob; we flag any documents exceeding 25MB for a separate transfer process.

User accounts migrate via the Stable Users API endpoint. We preserve login, email, first/last name, admin flag, and auth mode. Group memberships are migrated as a separate association step because Groups is a join table, not a top-level resource.

Groups exist in Easy Redmine's schema as a many-to-many join between users and group assignments. There is no standalone REST endpoint for group CRUD. We reconstruct group memberships by querying member roles at the project level.

Issue Relations are available in the Alpha API from Redmine 1.3+. Relation types (blocks, precedes, duplicates, relates) are preserved as typed associations, but the API does not support bulk creation so we chunk relation writes into batches.

Easy Redmine extends Redmine's custom field model significantly with project-level field definitions and custom field sets. We inspect the available_values schema for each custom field during scoping and map enumerated fields to equivalent drop-down or tag structures in the destination.

File attachments are stored as blobs linked to Issues, Projects, or Documents. We download each attachment from Easy Redmine's storage and re-upload to the destination, preserving original filenames and MIME types. Attachments larger than 100MB are flagged for manual transfer.

Scrum and Kanban boards in Easy Redmine are UI-state objects that derive from issue statuses and sprint assignments. Board configuration (column ordering, WIP limits) is a custom Easy Redmine extension without a standard API equivalent, so we migrate the underlying sprint and issue state data.

Resource allocation data is an Easy Redmine extension over standard Redmine. We migrate user-assignment hours and capacity data where exposed via the API, but allocation matrices with role breakdowns require custom field mapping.

Helpdesk is a separate module in Easy Redmine that creates tickets linked to Issues. Email threads and SLA metadata are Easy Redmine-specific fields not present in upstream Redmine. We migrate ticket text and status; SLA rules must be reconfigured in the destination.