Migrate from ProjeQtOr to monday Work Management

ProjeQtOr Projects (top-level containers with start date, end date, status, and portfolio assignment) map to monday.com Boards. We extract project.id, project.name, project.startDate, project.endDate, project.status, and project.idTeam as a Board with a Project Overview group. Each project generates one Board; multi-project portfolios generate multiple Boards inside a Workspace. The ProjeQtOr project description migrates as a Board description text.

ProjeQtOr Tasks map to monday.com Items. Parent-child task hierarchies (WBS numbering) are preserved by nesting Items in Subitems. Planned work hours and actual hours logged migrate as separate number columns. Task priority, estimated duration, and work unit come in as Status and Number columns. We resolve parent task references by creating the parent Item first, then linking child Items as Subitems in a second pass.

ProjeQtOr Milestones (standalone date items linked to a project) map to monday.com Items with a Timeline column set to a zero-duration range (same start and end date) to signal milestone semantics. Milestone name and status migrate directly. If the customer uses the milestone as a phase gate, we configure it as a separate Group inside the Board instead, with a label column distinguishing it from regular task groups.

ProjeQtOr Resources (team members with calendar availability, skill profiles, and cost rates) map to monday.com Person column values. We extract resource.name, resource.email, resource.cost, and resource.isResource flag and create People column assignments on each Item. Resource capacity settings have no direct monday.com equivalent; we flag these for the customer to implement manually using monday.com's Workload view on Standard+ tiers or a third-party integration.

ProjeQtOr Allocations bind a Resource to a Task with a start date, end date, and daily assignment percentage. These map to monday.com Date columns (start and end) plus a Number column for allocation percentage. We reconstruct the allocation by joining the allocation table to the task table during extraction. Over-allocated resources are flagged in a reconciliation report so the customer can adjust before or after migration.

ProjeQtOr Expenses (project costs outside resource billing: travel, licenses, contractors) map to monday.com Items with Number columns for expense amount, Currency columns for VAT or tax, and Text columns for expense category and description. The expense.projectId reference maps to the parent Board. We preserve the original expense date, category, and payment status as separate text or date fields.

ProjeQtOr Risks (probability, impact, mitigation plan, owner) map to monday.com Items. We create a dedicated Risk Board per project or a Risk Group inside each project Board. Probability and impact map to two Number columns (0-100 scale). Mitigation plan migrates as a Long Text column. Risk status (identified, mitigating, resolved, accepted) maps to a Status column with color-coded values matching the original ProjeQtOr status workflow.

ProjeQtOr Issues and Incidents (bugs, change requests, incidents) map to monday.com Items in a separate Issue Tracking Board. Issue type (bug, incident, change request) maps to a Status column with labeled values or a separate Label column. Priority, status, and description migrate directly. Linked test cases or requirement associations are preserved in a text column referencing the related Item IDs.

ProjeQtOr Documents are filesystem references (file paths on the application server) stored with metadata in the database. We identify every document record, locate the corresponding files in the ProjeQtOr file storage directory, and run a parallel file transfer to monday.com's attachment storage. We then create Items in a Document Board with the File column pointing to the uploaded file, preserving the original filename, upload date, and document category from ProjeQtOr.

ProjeQtOr Budgets track planned versus actual spending per project with budget line items. We map budget amounts to Number columns inside Items representing budget categories. Planned and actual figures migrate as separate Number columns; the variance is calculated by monday.com's formula column feature on Pro plans. If the budget tracks multiple cost categories, we create one Item per budget line inside a Budget group.

ProjeQtOr Versions (product releases linked to a project with version number, status, and target date) map to monday.com Items with a Timeline or Date column for the release date and a Status column for version status (planned, in development, released, deprecated). Version number migrates as a Text column.

ProjeQtOr extends standard objects with custom fields stored in a separate EAV table (attribute-value rows with object-type and ID references). A simple column export omits these. We write migration queries that explicitly join the custom field tables per object type, flatten each attribute-value pair into a named column, and create the corresponding column in monday.com. Any custom field with no natural monday.com column type is flagged in the scoping report for the customer to decide whether to create a custom column, merge into a text field, or drop.