Migrate your ProjeQtOr data

Projects are the top-level container in ProjeQtOr. Every task, milestone, resource allocation, and expense belongs to a Project. We extract project records by their ID and map the project status, start/end dates, and description fields directly to the destination equivalent.

Tasks support parent-child hierarchies and multiple assignees. We preserve the WBS numbering sequence and dependency chains during migration. Planned work hours and actual work logged are mapped as separate fields in the destination.

Milestones are standalone items that can be standalone or linked to a parent project. We extract milestone name, date, status, and project association and map them to the destination milestone or phase object.

Resources represent team members with calendar availability and cost rates. We map resource records to the destination user or resource object, preserving capacity settings, skill profiles, and cost-per-day values.

Resource allocations bind a Resource to a Task with a start date, end date, and daily assignment percentage. We extract the full allocation table and reconstruct assignments in the destination, flagging over-allocated resources.

Expenses capture project costs that fall outside resource billing—travel, software licenses, contractors. We map expense category, amount, date, and project association. VAT/tax amounts are preserved as separate fields where present.

Risks include probability, impact, mitigation plan, and owner assignment. Some destination platforms store risks as Issues with a custom type field. We create a mapping rule that pushes Risks into the destination's Issue or Risk object and preserves the probability-impact matrix values as custom fields.

ProjeQtOr uses a combined Issue object for bugs, incidents, and change requests. We extract the issue type, priority, status, and description, then map to the destination ticket or issue object, splitting by type where the destination has separate objects.

Documents are stored as file references within ProjeQtOr's document management module. We extract the file URLs or paths and map them to the destination attachment object. Binary file content requires a separate file-transfer step alongside the record migration.

Budgets track planned versus actual spending per project. We extract budget line items and actual expense totals and map them to the destination financial or budget field. Where the destination has no budget object, we store budget data as custom project fields.

Versions track product releases linked to a project. We extract version name, number, status, and target date. If the destination tracks releases as a separate object, we create a direct mapping; otherwise, versions land as tags or milestones with a version-type indicator.

ProjeQtOr supports custom status workflows per object type. We read the workflow definition table to understand which statuses are available per object and map them to equivalent statuses in the destination, flagging any custom statuses that have no direct match.

Quotations and sales orders are not part of the core ProjeQtOr PM module. These are handled by separate CRM or ERP systems in the ProjeQtOr ecosystem. We do not migrate quotation data out of ProjeQtOr as it falls outside the platform's project management scope.