Migrate from Rocketlane to Microsoft Project

Rocketlane Projects map directly to Microsoft Project projects (MPP files or Project for the Web projects). Project name, start date, target end date, status, description, and priority migrate as project-level metadata. Phase grouping within the Rocketlane project is preserved by converting each Phase to a summary task row in the destination project, maintaining the phase sequence order as it appears in the Rocketlane timeline.

Each Rocketlane Phase converts to a Microsoft Project summary task row. Phase name, start date, and end date set the summary task Start and Finish fields. We preserve phase-level status (To do, In progress, Completed, Blocked) as a custom flag column in the MPP file. Phase dependencies (if defined across phases) convert to summary-to-summary task dependencies in the destination Gantt. Note: phase-level assignees do not translate to a single resource assignment on the summary task; we assign team members to the underlying tasks instead.

Rocketlane Tasks map to Microsoft Project detail tasks. Name, Start, Finish, Duration (computed from Start and Due Date), Percent Complete, Priority, and Description migrate directly. Task-level assignees map to the Resource Names field in Microsoft Project (resource names must match a pre-loaded resource list). Checklist items within a Rocketlane Task migrate as separate sub-tasks or as a notes field, depending on checklist complexity. Dependencies between tasks convert to Finish-to-Start (FS) task dependencies in the Gantt.

Rocketlane project-level and task-level custom fields (TEXT, MULTI_LINE_TEXT, YES_OR_NO, DATE, SINGLE_CHOICE, MULTIPLE_CHOICE, SINGLE_USER, MULTIPLE_USER, NUMBER) require pre-configuration in the destination Microsoft Project file. We enumerate the full custom field schema during scoping, map each field type to the nearest Microsoft Project column type (Flag, Number, Cost, Date, Text), and create custom columns in the MPP file before data import. Rating fields (project-level only in Rocketlane) map to a 1-5 Number column.

Rocketlane workspace members and project assignees map to Microsoft Project Resources. We extract all distinct user IDs referenced on tasks and phases, map them by email to a resource table in the destination MPP file, and flag any resource without a matching email as 'unresolved — admin to provision.' For Project for the Web destinations, we map to Planner Plan 3 assignments instead. Inactive or guest accounts in Rocketlane are excluded from the resource table by default unless the customer requests otherwise.

Rocketlane Clients (external stakeholders with portal access) have no Microsoft Project equivalent. We flag all Client records during scoping and advise the customer to configure a SharePoint site or Microsoft Teams external guest access policy before cutover. Client contact information migrates as a text field or note on the project, not as a native collaboration object. The customer must decide whether external stakeholders receive a direct MPP link or access via SharePoint document libraries.

Rocketlane Spaces (client-facing project workspaces containing a shared timeline, document library, and activity feed) do not have a native Microsoft Project equivalent. We extract the Space association for each project and deliver a written recommendation to configure a corresponding SharePoint document library linked to the project, using the same folder structure as the Rocketlane Space. Document content migrates separately (see Documents mapping); collaboration history does not.

Rocketlane Documents export to PDF only with no structured data format. We extract document body text and attempt to rebuild structural elements (panels, tables, sections) as markdown files. These markdown files are uploaded to the destination SharePoint document library or OneDrive folder for the corresponding project. Approval history, freeze/unfreeze states, comments, and approval workflows do not transfer. The customer rebuilds document-level approval logic in Power Automate post-migration if required.

File attachments on Rocketlane Tasks and Documents are downloaded via the API and uploaded to the corresponding SharePoint document library or OneDrive folder for the destination project. We preserve the filename, file type, and the task association via a custom Task Notes field containing the SharePoint/OneDrive link. Attachments exceeding SharePoint's file size limits (250 GB per file) require separate handling.

Rocketlane Time Entries (Premium and Enterprise tier) map to task-level assignment hours in Microsoft Project. We compute total hours per task from the Rocketlane time tracking data and set the Assignment Work field in the destination. Time entry metadata (date, user, billable/non-billable flag) migrates to a custom Number or Flag column. Note: Microsoft Project does not have a native timesheet or time approval workflow; billable tracking requires a separate PSA or timesheet tool or a Power Apps canvas.

Rocketlane project and document templates are not natively importable into Microsoft Project. We extract template structure (phase sequence, task names, default durations, default assignees) and deliver a written specification for rebuilding the template as an MPP file with custom fields pre-populated. Template-level default assignees and phase pre-population require manual reconfiguration at the destination.

Rocketlane Automations are plan-gated and cannot migrate as code. We inventory every active automation — including its trigger, conditions, and actions — during discovery and deliver a written automation map with recommended Power Automate equivalents for each. This is a documented handoff for the customer's admin team; we do not build Power Automate flows within the migration scope.