Migrate from Agilean to Microsoft Project

Agilean Project records map directly to Microsoft Project project files (MPP) or Project Online/Project for the Web projects. We extract the project name, description, start date, finish date, and status from Agilean and create the corresponding Project in the destination environment. Active versus archived status in Agilean maps to Active/Completed/Archived states in Microsoft Project.

Agilean Task records map to Microsoft Project Task rows within the project schedule. We map task name, planned start, planned finish, duration, and percent complete from Agilean's fields to the corresponding Microsoft Project columns. Constraint dates and task calendars transfer where Agilean exposes them; we flag any Agilean-specific scheduling metadata that has no Microsoft Project equivalent for the customer's PMO to evaluate.

Agilean predecessor-successor relationships map to Microsoft Project task dependencies (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish). We extract the dependency type and lag time from Agilean and configure the corresponding predecessor link in Microsoft Project. Complex cross-project dependencies may require manual validation or a temporary dependency workaround during migration.

Agilean resource records map to Microsoft Project Resources. We extract resource name, email (if available), role, and capacity data. If Agilean stores resource allocation percentages or assignment hours, we map these to Microsoft Project assignment fields (Units, Work). Resource calendars in Agilean transfer as the default calendar assignment in Microsoft Project.

Agilean task assignments (which resource is assigned to which task) map to Microsoft Project Assignments. We resolve the resource reference from Agilean to the mapped Microsoft Project Resource and create the assignment record with Work and Units fields populated from the Agilean allocation data. If Agilean stores task-level effort estimates, we map these to the Assignment Work field.

Agilean custom fields require direct customer collaboration to enumerate, since Agilean's exact custom field data types are not publicly documented. We map Agilean custom field names and values to Microsoft Project Enterprise Custom Fields using the supported type set (Text, Number, Cost, Flag, Date, Outline Code, Duration, Yes/No). We verify field type compatibility during discovery and flag any Agilean field types that exceed Microsoft Project's 30+ supported custom field types for customer decision.

Agilean file attachments map to documents stored in the SharePoint document library associated with the Microsoft Project site or to the local project file's hyperlinks. We extract the file reference and URL from Agilean and either migrate the file content directly (if the file is accessible via Agilean's export mechanism) or create a hyperlink record pointing to the original location for the customer's admin to relocate post-migration. File size and attachment count affect migration timeline estimates.

Agilean milestone records map to Microsoft Project tasks with zero duration and the Milestone flag enabled. We extract the milestone name, date, and any associated custom fields and preserve these as milestones in the destination project. Milestone dependencies (predecessors) map using the same dependency logic as standard task dependencies.

Agilean non-standard object types (flagged during discovery) map to either Microsoft Project Enterprise Custom Fields or Enterprise Lookup Tables depending on the data structure. If the non-standard object represents a picklist-style enumeration, we use an Outline Code or Text custom field. If it represents a related record with multiple attributes, we evaluate whether a custom field group or a SharePoint list integration is the appropriate representation in the Microsoft environment.

Agilean workflow configurations and rule-based automation do not migrate as code to Microsoft Project. We deliver a written inventory of every Agilean workflow rule with its trigger conditions, actions, and scope (project-level versus task-level). The customer's PMO or a Microsoft partner rebuilds these in Microsoft Project using built-in features (AutoSave, Desktop Inspector, or Power Automate) post-migration. This is a manual handoff, not a data migration deliverable.