Migrate from AceProject to Microsoft Project

AceProject Projects map to Microsoft Project files or Project Online projects. We export project metadata (name, description, start date, end date, status) from AceProject's admin Export Data tool and create corresponding Microsoft Project files. For Project Online destinations, we create a Project Site and sync the project name, description, and classification fields. Project-level custom fields map to Microsoft Project enterprise custom fields if the destination uses Project Online with an enterprise pool.

AceProject Tasks map directly to Microsoft Project Tasks. Task name, start date, finish date, duration, and percent complete transfer. We convert AceProject estimates (estimated hours) to Microsoft Project duration units using the project's default calendar. Task-level custom fields (Boolean, Date, List, Numeric, Text, User) map to Microsoft Project custom fields with equivalent types.

AceProject Subtasks nested under Tasks flatten into a Microsoft Project WBS hierarchy where the parent Task becomes a Summary Task and Subtasks become subordinate tasks. We preserve the hierarchy by setting the Outline Number and Outline Level in the destination. The parent-child relationship is reconstructed using Microsoft Project's outline structure rather than a separate Subtask object.

AceProject Users map to Microsoft Project Resources. We extract User records (name, email, role) from AceProject and create corresponding Resource Sheet entries in Microsoft Project. For Project Online destinations, resources are created in the enterprise resource pool. AceProject user-level custom fields map to Resource custom fields. Note that Microsoft Project Resources are not automatically assigned to tasks — we perform resource assignment mapping as a separate step after resource creation.

AceProject Task Assignees map to Microsoft Project Assignments. Each unique Assignee on an AceProject Task becomes an Assignment row in Microsoft Project with the Resource, Units, and Work computed from the AceProject estimate. We run resource assignment mapping after the Resource Sheet is complete to ensure all Resources are resolvable before task assignments are written.

AceProject Task Dependencies with type (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map to Microsoft Project Predecessor fields on the dependent Task. We reconstruct the dependency graph by exporting dependency records with the predecessor and successor Task IDs, then writing the Predecessor value in the format 'TaskID[Type][Lag]' during migration. Circular dependencies are flagged and escalated before the import.

Microsoft Project does not have a native time-tracking module equivalent to AceProject's Time Entries. We store time entry data (hours, date, task association) as custom Number fields on Tasks if the destination is Microsoft Project Desktop. For Project Online destinations, we map Time Entries to a SharePoint-based timesheet structure that the customer's admin links to the project via Power Automate. The billing rate from AceProject Time Entries is stored as a custom field on the Assignment.

AceProject Expense records have no direct Microsoft Project equivalent. We export expense metadata (amount, category, date, description, project association) and deliver it as a structured CSV inventory for the customer's admin to re-enter in a connected expense system (SharePoint list, Dynamics 365 Project Operations, or external tool). Expense reporting is out of scope for the standard migration but can be addressed as a separate configuration engagement.

AceProject Documents are associated with Projects. We export document metadata (name, upload date, author, file size) and file URLs. For Project Online destinations, we copy documents to the associated Project Site's SharePoint document library. For Microsoft Project Desktop destinations, we deliver the document metadata inventory and advise uploading files to a shared SharePoint or OneDrive location with the document inventory as a reference.

AceProject Task custom fields (Boolean, Date, List, Numeric, Text, User types) map to Microsoft Project custom fields with the corresponding type. We detect the interface version during scoping and export from the new AceProject interface to ensure all custom field values are visible. Custom fields with an Administrator-only visibility flag are exported under the admin account. For Project Online, custom fields are added to the enterprise project detail pages before migration.

AceProject document and task comments do not have a native Microsoft Project equivalent. We export comment text, author, and timestamp as a structured note inventory and deliver it alongside the migration. For Project Online destinations, comments can be stored in a SharePoint list linked to the project. The comment threading structure is simplified to flat text during export.