Project Management migration
Field-level mapping, validation, and rollback between Easy Redmine and Microsoft Project. We move data and schema; workflows are rebuilt natively in Microsoft Project.
Easy Redmine
Source
Microsoft Project
Destination
Compatibility
11 of 11
objects map 1:1 between Easy Redmine and Microsoft Project.
Complexity
BStandard
Timeline
48–72 hours
Overview
Easy Redmine structures work as Issues organized under Projects with custom fields, versions, and time entries. Microsoft Project (Desktop and Project Online) structures work as Tasks within a Project file, where resource calendars drive scheduling and custom fields attach to individual tasks. The two models diverge on several fronts: Easy Redmine supports multi-project aggregation via sub-projects; Microsoft Project Desktop is a per-file model with no native REST API, requiring a Project Online or Project for the Web endpoint for programmatic migration. FlitStack AI extracts Easy Redmine data via its REST API (paginated, offset-based, 100-record cap per page) and reconstructs the Gantt structure in Microsoft Project using task hierarchy, predecessor links, and resource assignments. Custom fields migrate as task custom fields in Project Online or as columns in Desktop via intermediate CSV transformation. Wiki pages, helpdesk tickets, and helpdesk workflows have no Microsoft Project equivalent — we surface those as separate exports for manual rebuild in SharePoint or Planner.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Easy Redmine object lands in Microsoft Project, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Easy Redmine
Project
Microsoft Project
Project (MPP file or Project Online project)
1:1Easy Redmine Project maps to one Microsoft Project file or one Project Online project. Sub-projects in Easy Redmine become Summary Tasks under the parent Project in Microsoft Project. We preserve the original project identifier in a custom field for cross-reference.
Easy Redmine
Issue
Microsoft Project
Task
1:1Easy Redmine Issue maps to Microsoft Project Task. Issue subject becomes Task Name. Issue description maps to Task Notes. Status, priority, and assigned user are mapped to custom task fields. Sub-issues map to sub-tasks within the parent Task hierarchy.
Easy Redmine
Issue Status
Microsoft Project
Task Percent Complete or custom Status field
1:1Easy Redmine's open/closed/in-progress status workflow has no direct Microsoft Project equivalent. We map status to either a custom task field (Status__c picklist) or derive percent complete from Easy Redmine's done_ratio field, normalizing against your defined status-to-percent mapping.
Easy Redmine
Version (Milestone)
Microsoft Project
Milestone Task
1:1Easy Redmine Versions with type='standalone' (milestones) become Microsoft Project milestone tasks (Duration = 0, Milestone checkbox = true). Version due date maps to the milestone task's Finish date. Versions with type='none' are skipped or exported as informational records.
Easy Redmine
Issue Relation (predecessor)
Microsoft Project
Task Predecessor (Finish-to-Start)
1:1Easy Redmine Issue Relations (blocks, preceded by, duplicated by) map to Microsoft Project predecessor links. We translate relation type to FS (Finish-to-Start) by default; blocks relations become Finish-to-Start with lag time. Circular dependency chains are flagged and require manual resolution before migration.
Easy Redmine
User (assignee)
Microsoft Project
Resource
1:1Easy Redmine Users assigned to Issues become Microsoft Project Resources. We match Easy Redmine user email against Microsoft 365 user list for Project Online. Desktop MPP migrations require manual resource roster setup or CSV import. Material resources are not natively supported; we create them as generic resource entries.
Easy Redmine
Time Entry
Microsoft Project
Task Actual Work / Assignment Actual Work
1:1Easy Redmine Time Entries aggregate to actual work on the corresponding Task Assignment in Microsoft Project. We sum all time entry hours by user per Issue and write that as the Assignment's Actual Work field. Billable flag and comments are stored as assignment notes for reference.
Easy Redmine
Issue Custom Fields
Microsoft Project
Task Custom Fields
1:1Easy Redmine custom fields on Issues require corresponding custom fields in Microsoft Project. Project Online supports local task custom fields (Text, Number, Date, Picklist). Desktop MPP requires column mapping via a header row or enterprise custom field definition before import. We create the schema plan for your Project admin to implement.
Easy Redmine
Wiki Page
Microsoft Project
No equivalent (SharePoint / external)
1:1Easy Redmine Wiki pages have no Microsoft Project equivalent. We export all Wiki content as HTML bundles with page hierarchy preserved. Your team can upload these to SharePoint or a knowledge base. Links between Wiki pages are rewritten to relative paths for downstream upload.
Easy Redmine
Helpdesk Ticket
Microsoft Project
No equivalent (Planner / Service Desk)
1:1Easy Redmine helpdesk tickets are support-channel records with SLA tracking — not project schedule items. We export ticket history as a CSV report with parent Issue reference. Rebuild in Microsoft Planner, Dynamics 365 Customer Service, or a separate ticketing system.
Easy Redmine
Document Attachment
Microsoft Project
SharePoint Document Library / file attachment
1:1Easy Redmine file attachments on Issues are downloaded and re-uploaded to the associated Project Online SharePoint document library, or mapped to MPP file hyperlinks pointing to a shared network location for Desktop migrations. Original file names and attachment dates are preserved.
| Easy Redmine | Microsoft Project | Compatibility | |
|---|---|---|---|
| Project | Project (MPP file or Project Online project)1:1 | Fully supported | |
| Issue | Task1:1 | Fully supported | |
| Issue Status | Task Percent Complete or custom Status field1:1 | Fully supported | |
| Version (Milestone) | Milestone Task1:1 | Fully supported | |
| Issue Relation (predecessor) | Task Predecessor (Finish-to-Start)1:1 | Fully supported | |
| User (assignee) | Resource1:1 | Fully supported | |
| Time Entry | Task Actual Work / Assignment Actual Work1:1 | Fully supported | |
| Issue Custom Fields | Task Custom Fields1:1 | Fully supported | |
| Wiki Page | No equivalent (SharePoint / external)1:1 | Fully supported | |
| Helpdesk Ticket | No equivalent (Planner / Service Desk)1:1 | Fully supported | |
| Document Attachment | SharePoint Document Library / file attachment1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Easy Redmine gotchas
Pagination cap of 100 records on all collection endpoints
Easy Redmine custom fields lack standard API discovery
Wiki and document attachments stored as file blobs require separate storage access
No free trial requires paid commitment before evaluation
Microsoft Project gotchas
Project for the web is being retired and merged into Microsoft Planner
Planner-tier portfolio features are incomplete despite Plan 5 labeling
Web app constraint controls are weaker than the Windows desktop client
Project requires a separate license not bundled with standard Microsoft 365
Project Online API is edition-gated and inconsistently documented
Pair-specific challenges
Migration approach
Establish destination endpoint and validate API access
We confirm whether the migration targets Microsoft Project Desktop (MPP file export), Project Online (SharePoint-connected), or Project for the Web (Dataverse). For Desktop, we set up the CSV/XLSX schema matching your MSP version's import column definitions. For Project Online, we authenticate against the PWA REST API and validate read/write permissions on the target site. For Project for the Web, we connect to the Dataverse environment and confirm Power Platform licensing.
Pull Easy Redmine data via REST API with pagination handling
We export Projects, Issues (with sub-issues), Versions, Time Entries, Users, and Custom Fields via the Easy Redmine REST API. The API returns paginated results with a maximum of 100 records per page (offset/limit parameters). We iterate through all pages to capture the full dataset, handle rate-limit responses with exponential backoff, and log any API errors to a separate exception file. Attachments are downloaded concurrently and staged by Issue ID for downstream SharePoint upload.
Build task hierarchy and dependency graph from Issue relations
We construct the Microsoft Project task structure by resolving parent_issue_id for sub-issue nesting and translating Issue Relations to predecessor links (Finish-to-Start). Circular dependencies are flagged for manual resolution. Versions with type='standalone' are inserted as milestone tasks at their effective_date. Resource assignments are matched against the exported User roster and written as Assignment rows.
Run sample migration and generate field-level diff
A representative slice — typically one project with 50–200 tasks — migrates first. We generate a field-level diff comparing source Issue values against the resulting Task fields in Microsoft Project. You verify date mapping, custom field translation, status-to-percent-complete normalization, and resource resolution. We adjust the mapping plan based on your feedback before the full run commits.
Execute full migration with delta-pickup window
The full dataset migrates against the confirmed destination. A delta-pickup window (24–48 hours) captures any Issues created or modified in Easy Redmine during cutover. We apply deadline constraints on tasks that had explicit due_date values. Audit log records every operation. One-click rollback reverts the Project Online environment or re-generates the MPP file if reconciliation fails.
Platform deep dives
Easy Redmine
Source
Strengths
Weaknesses
Microsoft Project
Destination
Strengths
Weaknesses
Complexity grading
Standard Project Management migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Easy Redmine and Microsoft Project.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Easy Redmine: Not publicly documented; no official rate limit spec found in Easy Redmine's published API docs.
Data volume sensitivity
Easy Redmine doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Easy Redmine to Microsoft Project migration scoping. Not seeing yours? Book a call.
Walk through your Easy Redmine to Microsoft Project migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Easy Redmine
Other ways to arrive at Microsoft Project
Same-Project Management migrations
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
![]project-open[ logo](/platforms/project-open.png)
