Migrate from ProjeQtOr to Microsoft Project

ProjeQtOr Project records map to Microsoft Project Project files or Project Online project sites. We extract project name, description, start date, end date, status, and priority from the project table. Project-level custom fields stored in the EAV attribute-value tables are explicitly enumerated and mapped to Microsoft Project custom text, number, date, or flag fields. ProjeQtOr's multi-project portfolio structure maps to individual MPP files or a Project Online Project PWA site collection per project.

ProjeQtOr Tasks map directly to Microsoft Project tasks. We preserve the WBS numbering sequence stored in ProjeQtOr's WBS field and recreate the same WBS string in Microsoft Project's WBS field. Parent-child hierarchy is reconstructed using Microsoft Project's Outline Number and Summary Task structure. Task fields mapped include name, duration, start date, finish date, priority, status, and work (hours). Actual work logged against tasks in ProjeQtOr migrates as actual work in Microsoft Project, driving percent complete calculation.

ProjeQtOr Milestones map to Microsoft Project tasks with Duration set to zero and the Milestone flag enabled. Milestone name, due date, and project association migrate directly. Milestones that serve as phase gates in ProjeQtOr are linked as predecessors to the first task of the subsequent phase to preserve the phase-gate logic.

ProjeQtOr Resources (team members with calendar availability and cost rates) map to Microsoft Project Resources. We extract resource name, type (material vs work), max units (capacity percentage), hourly cost rate, and calendar exceptions from the ProjeQtOr resource and calendar tables. Resource calendars in Microsoft Project are reconstructed by mapping ProjeQtOr leave days and non-working time to calendar exceptions. ProjeQtOr skill profiles are not natively supported in Microsoft Project and are flagged for documentation.

ProjeQtOr Allocations (resource-task assignments with start date, end date, and daily assignment percentage) map to Microsoft Project Task Assignments. We reconstruct each assignment with the assigned resource, units (percentage), start, and finish. ProjeQtOr allocation percentages translate directly to Microsoft Project assignment units. Over-allocated resources in ProjeQtOr are flagged and surfaced in a pre-migration reconciliation report so the customer can resolve before or after cutover.

Microsoft Project has no native expense tracking module. ProjeQtOr expenses (category, amount, date, project, and VAT) are extracted and written to a structured CSV delivered alongside the migration. Each expense row references the migrated ProjeQtOr project ID. The customer imports this CSV into an expense management tool or maps it to Microsoft Project task cost fields if the expense is task-specific. We document the mapping decisions in the migration handoff.

ProjeQtOr Risks include probability, impact, mitigation plan, and owner assignment. Microsoft Project has no native risk register. We extract all risk records to a structured CSV with probability, impact, mitigation description, owner, and project reference. The customer imports this into a risk management tool (SharePoint list, Azure DevOps, or ServiceNow) or creates risk entries as summary tasks with a risk flag custom field. We document the chosen strategy during scoping.

ProjeQtOr Issues and Incidents are combined in a single object with type, priority, status, and description. Microsoft Project does not have a native issue log. We extract issue records to CSV and recommend mapping them to a SharePoint list integrated with the Project Online site or to a task with an issue flag. Issue type (bug, change request, incident) is preserved as a custom text field in the CSV for the customer to structure in their chosen destination.

ProjeQtOr documents are file-system references stored in the database with file paths pointing to the application server's document directory. We identify all document records, locate the corresponding files, and run a parallel file transfer to the destination SharePoint document library or local file share. Attachment URLs in migrated records are updated to point to the new storage location. If the destination is Microsoft Project desktop without SharePoint, files are attached directly to the MPP file and we flag the file-size constraint.

ProjeQtOr extends standard objects with a flexible attribute-value model stored in separate tables. Custom fields are not direct columns; a standard column export omits them entirely. We write migration queries that explicitly join the custom field tables per object type and flatten each attribute-value pair into a named field in the destination. Fields with no natural Microsoft Project equivalent are flagged in the migration handoff for the customer to decide whether to drop them, merge into a notes field, or create a new custom field. Microsoft Project supports custom text, number, cost, date, flag, and drop-down fields per object type.

ProjeQtOr Versions track product releases linked to a project with name, number, status, and target date. Microsoft Project has no native version or release object. We map version records to summary tasks with a release flag custom field, preserving version name, target date, and status. The customer decides whether to use this as a planning construct or to document releases externally.

ProjeQtOr Budgets track planned versus actual spending per project with line items and totals. Microsoft Project does not have a native budget tracking module beyond task cost fields. We extract budget line items to a structured CSV. For task-level costs (resource-based billing), we map planned cost and actual cost to the relevant Microsoft Project cost fields. For project-level budgets, we deliver a CSV for the customer to manage in Excel, Power BI, or a financial system.