Migrate from QuickStart Admin to Microsoft Project

QuickStart Admin Projects map to Microsoft Project files (.mpp) or Project for the Web Project records. The top-level project name, description, start date, and finish date transfer as base project properties. We probe the source instance during discovery to confirm whether QuickStart Admin stores a single project container or multiple workspaces, since multi-project organizations require us to create one .mpp file or Project for the Web entry per source project.

QuickStart Admin Task records map to Microsoft Project Task rows. Task name, start date, finish date, duration, and percent complete transfer directly. We resolve the source task hierarchy (parent-child relationships or subtask flattening) against Microsoft Project's WBS structure. Summary tasks in Project become the parent level; leaf tasks become the detail rows. Milestone tasks from QuickStart Admin map to Microsoft Project milestones (duration = 0).

QuickStart Admin subtasks with a parent-child structure map to Microsoft Project summary tasks (indented rows with a summary bar). If QuickStart Admin stores subtasks as flat records with a parent_id reference, we reconstruct the hierarchy during the transform step before loading into Project. If QuickStart Admin flattens subtasks to the same level as tasks, we apply the customer's preferred indentation convention during migration.

QuickStart Admin Assignee records map to Microsoft Project named Resources. We extract user names and email addresses from the assignee list, deduplicate by email, and create Resource records in the Project resource sheet. Resource type is set to Work. Assignment hours transfer as assignment units on the task row. If QuickStart Admin assigns teams rather than individuals, we create a Resource Group in Microsoft Project and assign tasks to the group.

QuickStart Admin custom fields have no documented schema, so we probe the customer's live instance during discovery to identify custom field names, data types, and picklist values. Each custom field is then mapped to a typed Microsoft Project custom field: single-value picklists map to Choice fields (2-20 options), text fields map to Text, numbers to Number, dates to Date, and flags to Flag. If QuickStart Admin stores more than 20 picklist options for a custom field, we split across multiple Choice fields or use a Text field as a fallback.

QuickStart Admin task-level comments migrate as Microsoft Project Task Notes. Author and timestamp are appended to the note body in plain text format. Formatting (bold, bullet points, hyperlinks) may simplify to plain text during transfer depending on the source export format. We flag any rich-media content that cannot be preserved in the Project Notes field and recommend a SharePoint-based comments archive if fidelity matters.

QuickStart Admin user accounts required for assignee resolution migrate as Microsoft Project Resources. We map user email addresses as the Resource Name and create a custom Resource field for email to preserve the lookup key. Active and inactive user status does not block migration; inactive users become inactive Resources in Project so historical assignments are preserved even if the person has left the organization.

File attachments on QuickStart Admin tasks or projects cannot be migrated. Microsoft Project stores attachments as embedded OLE objects in .mpp files, which is not compatible with file-based exports from other platforms. We do not guarantee attachment migration for this pair. We recommend exporting attachments separately as a file-based archive and linking them via a UNC path in a custom Project Notes field or a SharePoint document library.

QuickStart Admin workflows (automated task triggers, notifications, status-change rules) do not migrate. Microsoft Project Desktop has no native workflow engine; Project for the Web supports Power Automate triggers but requires manual rebuild. We deliver a written inventory of every QuickStart Admin workflow configuration (trigger, conditions, actions) for the customer's admin to rebuild as Power Automate flows post-migration.

QuickStart Admin reports and dashboards do not migrate. Microsoft Project reporting lives in Project for the Web (Roadmap, built-in views) and Project Desktop (visual reports to Excel, Visio). We deliver a written report inventory from QuickStart Admin with the report name, filters, and chart type so the customer's admin can rebuild in Power BI or Excel.