Migrate from Easy Redmine to monday Work Management

Each Easy Redmine Project becomes one Monday.com Board. Project name maps to Board name; project description maps to a Text column on the board. Board URL and workspace are set during migration; subprojects become separate boards with cross-board link columns.

Easy Redmine Trackers (Bug, Feature, Task, Support) are not native to Monday.com. We map them to a dedicated Status column value or a Label column — for example, all Bug-tracked items get Status='Bug', Feature items get Status='Feature'. Teams can alternatively create separate boards per tracker; we document both approaches.

Every Easy Redmine Issue migrates as one Monday.com Item on the board corresponding to its parent Project. Subject maps to Item name; description maps to a Long Text column. Original created date maps to a Date column (Created__c); updated date maps to another Date column.

Easy Redmine issues that have a parent_issue_id migrate as Monday.com Subitems linked to the parent Item. Subitems inherit the parent's board context and appear in the subitem panel. This preserves the hierarchical relationship that would otherwise be lost in a flat item list.

Easy Redmine issue statuses (New, In Progress, Resolved, Closed, etc.) map to Monday.com Status column values. Each source status gets a corresponding Status column option with a color assignment. If Easy Redmine uses custom statuses per tracker, we create a separate Status column per tracker or use a Labels column to encode tracker+status together.

Easy Redmine priorities (Low, Normal, High, Urgent) migrate to a Monday.com Labels column with tag values or to a Number column with numeric values (1–4). The choice depends on whether the team wants priority visible as a visual tag or as a sortable number for dashboard filtering.

Easy Redmine assigned_to_id resolves against Monday.com users matched by email address. Unmatched users are flagged before migration — teams either invite them to the Monday.com workspace or reassign to a fallback owner. The Person column displays the assignee's avatar and name on each item.

Easy Redmine versions (with name, effective date, description) migrate as a Text column holding the version name plus a Date column for the target date, or as a Timeline column covering the project's planned date range. We preserve version status (open, locked, closed) in a secondary Labels column.

Easy Redmine time entries (linked to issue, user, hours, activity, spent_on) have no direct Monday.com equivalent. We create a Number column on each item storing the total hours sum, or create a separate Time Tracking board with item-level hour entries linked by issue reference. Custom field notes document the original activity type.

Easy Redmine custom fields on issues map to Monday.com columns of the equivalent type: string/text → Text, integer/float → Number, date → Date, boolean → Checkbox, list → Dropdown, user → Person. Enumeration option values are mapped to Dropdown options or Labels. All column names are prefixed with cf_ during mapping to avoid conflicts with native column names.

Project-level custom fields migrate as additional columns on the board itself (for simple fields like text or date) or as a dedicated board titled 'Project Settings' with one item per project holding the field values. The approach depends on the field type and whether the team needs the values visible on every item.

Easy Redmine issue categories (per project, with name and assigned_to) migrate as a Labels column on the board. Category names become label values. If a category has a default assignee, we document that rule for manual re-application in Monday.com automations.

Easy Redmine file attachments are downloaded and re-uploaded to Monday.com's native file storage via the File column type. If the attachment lives on a URL, it migrates as a Link column. Files without a download URL are noted in the migration report for manual re-upload.

Easy Redmine wiki pages (per project, with content, attachments, and versioning) have no Monday.com equivalent. We export each wiki page as a formatted HTML or Markdown file and deliver it alongside the migration. Teams typically move wiki content to Confluence, Notion, or Google Docs post-migration.

Easy Redmine issue relations (blocks, duplicated by, relates to, follows, precedes) have no Monday.com native equivalent. We map them to a Connect Boards column (linking items across boards) or store the related issue ID in a Text column with the relation type as a label. Complex relation chains require manual re-drawing in Monday.com.