Migrate from OpenProject to monday Work Management

OpenProject Projects map directly to monday.com Workspaces. Each OpenProject Project controls permissions via Member-Role assignments and hosts activated Modules (work packages, wiki, forums, documents, time tracking). We map the project name, description, and public/private visibility to the workspace equivalent. The Module activation state does not transfer directly—Boards in monday.com are created per Module type and the customer configures board visibility post-migration.

OpenProject Work Packages map to monday.com Items. Each Work Package carries Type (Task, Bug, Feature, Phase, Milestone), Status, Priority, Assignee, Responsible, start/due dates, estimated hours, and custom field values. We map Type to an Item's group label or a label column, Status to the board's status column, Priority to a number or label column, and dates to date columns. Parent-child Work Package hierarchy maps to monday.com subitems or item dependencies depending on the destination board structure chosen during scoping.

OpenProject Versions (milestones or sprints) group Work Packages and carry target dates. We create a monday.com Timeline view per OpenProject Version, mapping the Version's target date range and associated Work Package count. Version sharing across projects requires one Timeline view per workspace with items tagged to the relevant Version.

OpenProject custom fields are instance-specific definitions (name, type, options, required flag) that vary between installations. We treat custom field definitions as part of the migration schema, creating equivalent monday.com columns (text, number, date, person, dropdown, checkbox, etc.) for each source custom field before value mapping. The customer provides the custom field export during discovery. Any OpenProject custom field type without a direct monday.com column equivalent (e.g., user-type fields) is mapped to the closest available column type and noted in the mapping document.

OpenProject Boards store Kanban-style column configurations as work package query metadata. We preserve board structure and map OpenProject status columns to monday.com status column values. If the OpenProject board uses a Type-based column split, we recreate it in monday.com as a grouped board with one group per Type and status column per workflow state.

OpenProject Time Entries are logged against Work Packages with hours, cost type, and hourly rate. Time entry display is restricted to hours only (days-only is not natively supported in OpenProject). We map hours correctly to monday.com's Time Tracking column per item. Day-based time tracking from the source requires post-migration conversion advisory from FlitStack AI since neither platform natively supports day granularity for time entries.

OpenProject Cost Entries track unit costs and rates against work packages with configurable cost types. We preserve cost entry amounts in a monday.com number column formatted as currency. Cost type definitions require explicit mapping; if the customer has more than 5 distinct cost types, we recommend a separate cost type lookup board linked via item connections.

Attachments on OpenProject Work Packages, Wiki pages, and Documents are stored either in the database (small files) or on disk (large files). We migrate attachment metadata and map small file references to monday.com file columns. Large binary files may require out-of-band transfer with remapped disk paths and URL column references post-migration. We do not migrate the attachment binaries themselves without explicit bandwidth and security confirmation during discovery.

OpenProject Users carry email, name, login, admin status, and global roles. We map user accounts 1:1 by email to monday.com team members, reassigning work package ownership and time entries to the corresponding migrated account. monday.com person columns reference the team member records directly.

OpenProject Members are user-project assignments carrying a Role that defines a permission set. monday.com uses Workspace-level permissions (member, viewer, guest) and board-level sharing. We map OpenProject Role-based permissions to the nearest monday.com permission tier, noting that OpenProject's granular per-module permission model has no direct monday.com equivalent. The customer configures final board-level sharing post-migration.

OpenProject Forums and their thread-structured Messages carry author and post timestamps but have no monday.com equivalent object. We migrate forum metadata (forum name, message count, last post date) as structured text entries in an item updates column or as a linked doc board, and deliver a written inventory of all forum content for the customer's admin to re-post manually or via board update API.

OpenProject Wiki pages store formatted content with embedded work package lists. We migrate wiki content as structured text blocks and preserve embedded work package references as cross-document links in the migration mapping document. monday.com Docs provides a similar rich-text workspace document capability, but wiki-to-docs conversion requires manual reformating that we document rather than automate.