Migrate from PROAD to Microsoft Project

PROAD Projects map directly to Microsoft Project plans. We preserve project name, description, status (Active/Closed/On Hold), Start Date, Finish Date, and any custom Project-level fields. If PROAD's project has a fixed constraint or deadline, we set the corresponding constraint type in Microsoft Project. Project Plan 5 is required for project-level custom fields; Plan 3 supports task and resource custom fields only.

PROAD Subprojects nest inside Projects and carry their own task hierarchies. We transform each Subproject into a Microsoft Project summary task (Outline Level 1) with child tasks indented below it, preserving the parent-child relationship as outline hierarchy. WBS codes are generated to reflect the original subproject numbering. If a subproject has its own milestones, those become milestones under the summary task.

PROAD Tasks map to Microsoft Project Tasks with Task Name, Start, Finish, Duration, and Priority preserved. Subtask relationships from PROAD carry over as Microsoft Project outline indentation and predecessor-successor dependencies where applicable. We flag any tasks with constraint types set in PROAD and apply the equivalent Microsoft Project constraint.

PROAD Milestones map to Microsoft Project milestone tasks (zero-duration markers). We preserve the milestone name, target date, and associated project or subproject linkage. If PROAD stores milestone status (Completed/In Progress), we add a custom flag field to the milestone task.

PROAD Clients contain contact details and company information. Microsoft Project has no contact management object. We export Client records as a CSV inventory for the customer to import into Dynamics 365, a SharePoint list, or their chosen CRM. We do not force a partial import into Project because no supported object exists. The customer decides on the CRM strategy during scoping.

PROAD Contacts (email, phone, address, custom fields) have no Microsoft Project equivalent. We export contact records as a structured CSV with all original fields preserved for import into Dynamics 365, a SharePoint Contacts list, or another CRM. We flag any Contacts linked to specific Projects so the customer can manually associate them in their chosen contact management system.

PROAD time entries (hours logged, task attribution, user attribution, billable flag) map to Microsoft Project Assignment records under tasks. We aggregate time entries by task and set the Assignment Actual Work field. The billable flag has no native Microsoft Project field; we store it as a custom task flag field (Flag1 or a custom Flag field). Hourly rates from PROAD have no destination field and are noted in the billing-rate inventory delivered with the migration package.

PROAD Tickets linked to Projects migrate as Tasks in the destination Project plan with a custom Ticket ID field preserving the original PROAD ticket reference. Standalone tickets (not linked to a project) are exported as a CSV for import into Microsoft Planner, a helpdesk tool, or a SharePoint list. We advise the customer during scoping on whether their ticket volume warrants a Planner integration or a separate helpdesk migration.

PROAD Users and task Assignees map to Microsoft Project Resources. We match by email address and resolve to Resource records in the destination plan. Any inactive PROAD users are flagged for the customer to decide whether to include as resources. Material resources and cost resources require separate configuration in Microsoft Project if they exist in PROAD.

PROAD custom fields on Projects and Tasks map to Microsoft Project custom fields (Text, Flag, Number, Cost, or Date types). We inventory all custom fields during discovery, map each to the closest Microsoft Project type, and flag any that cannot be represented (for example, a multi-select text field without an equivalent). Project Plan 5 is required for project-level custom fields.

File attachments on PROAD Tasks and Projects are exported to a structured folder hierarchy and linked in Microsoft Project via Hyperlink fields pointing to the file share or SharePoint location. We document the original attachment path alongside the new link target so the customer's admin can validate access. Files exceeding typical size thresholds are flagged during audit.

PROAD Tags applied to Projects and Tasks are mapped to a custom Text or Flag field in Microsoft Project. We normalize tag names to avoid duplicates introduced by inconsistent casing or spacing in the source. Tags used for categorization (project type, department, priority) are migrated as separate custom fields; loose-label tags are concatenated into a single text field.