Migrate from ProjeQtOr to Asana

ProjeQtOr Projects map directly to Asana Projects. We extract project id, name, description, status, start date, end date, and customer association from the Project table and load into Asana Project via the Asana REST API or CSV importer. Project color and icon do not transfer; we configure these in Asana post-migration if needed. Multi-project portfolios in ProjeQtOr map to Asana Portfolios at the Business tier or to a top-level Project grouping at lower tiers.

ProjeQtOr Tasks map to Asana Tasks with parent-child hierarchy preserved via the subtasks relationship. The WBS numbering sequence from ProjeQtOr migrates as a custom field for audit. Planned work hours and actual work logged map to Asana custom number fields since Asana natively tracks only start date, due date, and assignee. Task status (idle, in progress, completed, cancelled) maps to Asana completion state with a status custom field for granular tracking.

ProjeQtOr Milestones map to Asana Milestones linked to the parent Project. We extract milestone name, target date, status, and project association from the Milestone table. Asana Milestones are a native subtype of Task; they appear as diamonds in Timeline and Calendar views. If the destination Asana workspace uses the Basic tier (which lacks Portfolios), milestones are the primary mechanism for phase tracking across projects.

ProjeQtOr Resources represent team members with calendar availability, cost rates, and skill profiles. We map Resources to Asana Users by email match, provisioning Asana Workspace members as we go. ProjeQtOr resource skill profiles and capacity settings do not have a direct Asana equivalent; we preserve them in custom fields on the User record (skill tags as a multi-select custom field, capacity notes in a text field). ProjeQtOr's resource pool concept (a shared inventory of available people) does not exist in Asana; resource availability is managed through the Workload view at Business tier.

ProjeQtOr Resource Allocations bind a Resource to a Task with start date, end date, and daily assignment percentage. Each allocation creates an Asana Task assignment. If a task has multiple resource allocations, we create one Asana assignee per allocation and record the original allocation percentage in a custom field assignment_percent__c. Allocations without a corresponding ProjeQtOr Resource become unassigned Asana Tasks flagged for manual assignment during cutover.

ProjeQtOr Expenses (travel, software licenses, contractor costs) with category, amount, date, VAT, and project association do not have a native Asana equivalent. We aggregate expenses by project and write them to Asana as a custom monetary field expense_total__c on the Project record, with individual expense line items preserved in a linked Google Sheet or CSV attachment on the Project for financial reference. Customers needing native expense management in Asana integrate a third-party tool post-migration.

ProjeQtOr Risks include probability, impact, mitigation plan, and owner. We map these to Asana Tasks with a risk_flag__c custom field set to true, probability mapped to a custom picklist (very low, low, medium, high, very high), impact to a severity custom field, and mitigation plan as the task description. We tag the task with a Risk label. This is a configuration decision the customer makes during scoping; alternatives include storing risks in a dedicated project with sections per risk category or using a third-party risk management integration.

ProjeQtOr Issues (bugs, incidents, change requests) map to Asana Tasks with the issue type (bug, incident, change request) preserved as a custom picklist field and tagged accordingly. Priority from ProjeQtOr maps to Asana priority (high, medium, low). Issue status (open, in progress, resolved, closed) maps to task completion state with a status custom field for granular tracking.

ProjeQtOr Document records reference files stored on the application server filesystem. We identify all document records, locate the corresponding files in the ProjeQtOr file storage directory, and upload them to Asana as Project or Task attachments via the Asana Attachments API. The original folder hierarchy is preserved as a prefix in the attachment name for traceability. Files exceeding Asana's 100 MB per-attachment limit are handled via Google Drive or Dropbox link custom fields.

ProjeQtOr Budgets track planned versus actual spending per project with line items and variance. We extract budget line items and actual expense totals and map them to Asana Project custom fields: budget_planned__c, budget_actual__c, and budget_variance__c. Detailed budget line items (category breakdown) are preserved as a linked CSV attachment on the Project. Asana has no native budget object; if the customer requires granular budget tracking, they use a third-party integration or a linked spreadsheet.

ProjeQtOr stores custom fields as EAV rows in a separate attribute table, not as direct columns. We write migration queries that enumerate custom field definitions per object type, flatten the EAV rows into columnar records, and create matching global Custom Fields in the Asana workspace before data migration begins. The customer chooses whether each custom field applies project-wide or workspace-wide. Custom fields with no natural Asana equivalent are flagged for decision: drop, merge into a notes field, or create a new custom field.

ProjeQtOr custom status workflows per object type have no direct Asana equivalent. We read the workflow definition table and document every status value and transition rule per object. The customer decides whether to rebuild status-based routing as Asana Automation Rules (Advanced tier) or as named Sections within a Project. We deliver a written workflow inventory document listing each ProjeQtOr status workflow, its trigger, its stages, and the recommended Asana implementation approach.