Migrate from Blueprint to Microsoft Project

Blueprint Projects map to Microsoft Project plan files or Project Online project sites. We preserve the Project name, description, start date, target date, and status. Blueprint's project-level metadata becomes project summary fields or custom fields in the destination. The Project becomes the top-level container in Microsoft Project with its Scopes and Tasks nested beneath.

Blueprint Scopes (AI-generated work breakdowns) represent logical groupings of related Tasks. In Microsoft Project, each Scope becomes a Summary Task that contains the related child Tasks. We flatten the Scope-to-Task hierarchy into a standard WBS structure. If a Blueprint Scope contains nested Scopes, the nesting is preserved as a nested Summary Task hierarchy. The original Scope name is preserved as the Task Name of the Summary Task.

Blueprint Tasks map directly to Microsoft Project Tasks. We migrate Task name, description, start date, end date, duration, status (Not Started, In Progress, Completed), and priority. If Blueprint stores effort or hours, we map to the Task Work field in Microsoft Project. Microsoft Project Task fields (Cost, Fixed Cost, Notes, Hyperlink) are populated where Blueprint data exists.

If Blueprint Scopes or Tasks have explicit dependencies (finish-to-start, start-to-start, etc.), we map these to Microsoft Project predecessor links using FS, SS, SF, FF dependency types. Not all project management tools store explicit task-to-task dependencies; if Blueprint uses scope-level sequencing rather than task-level, we document the dependency model during discovery and advise whether predecessor links should be built post-migration.

Blueprint stores user-to-Task assignments as user IDs linked to Task records. Microsoft Project uses a Resource Sheet (with named resources) and Assignment rows per Task. We extract unique users from Blueprint assignments, map them to Microsoft Project resources (by display name or email), and create Resource Assignments linking each Task to its assigned Resource. Resource type (Work, Material) defaults to Work for user assignments. Generic placeholders are created for unresolvable users.

Blueprint's role-based access model uses Roles (e.g., Developer, Project Manager, QA) that define permissions across Projects and Scopes. Microsoft Project's Resource Sheet supports role-type resources used for capacity planning without assigning to a specific named person. We map Blueprint Roles to Microsoft Project Resources of type Work with the Role name as the Resource name and a note that this is a role placeholder rather than an individual user.

Blueprint supports custom fields on Projects. We discover these during the extraction-phase audit, map them to Microsoft Project enterprise custom fields (Text, Number, Date, Flag, or Dropdown based on type), and populate them during import. Custom field formulas and conditional formatting from Blueprint do not carry over.

Blueprint supports custom fields on Tasks. These map to Microsoft Project Task-level custom fields. We discover the full field inventory during scoping, map each field's type to the nearest Microsoft Project equivalent, and populate values during task import. The customer should confirm which custom fields are actively used vs. historical before migrating all of them.

Blueprint Automation Rules are stored as structured configuration, not as migratable data records. We do not migrate automation rules as functional code. We document every active Automation Rule during discovery, capture its trigger conditions and actions, and deliver a written specification recommending either a Microsoft Project native equivalent (if one exists) or a Power Automate flow design. The customer's admin rebuilds the automations post-migration.

Blueprint stores attachment references (URLs or stored object IDs) associated with Projects or Tasks. Microsoft Project supports Hyperlink fields on Tasks and file attachments on tasks in the desktop client. We preserve the original URL or file reference as a Hyperlink on the relevant Task. The customer's admin confirms whether linked files need to be migrated to SharePoint or another document store for long-term access.

We preserve Blueprint task creation timestamps, last-modified timestamps, and completion timestamps as Microsoft Project Start, Finish, Actual Start, and Actual Finish fields where available. If Blueprint tracks percent complete, we map it to Microsoft Project's % Complete and Actual Work fields. Historical timestamps are preserved as-is to maintain project audit trails.