Migrate from Twproject to Microsoft Project

Twproject Projects map to Microsoft Project .mpp files (desktop) or Project Online project records (cloud). The project-level fields (name, description, start date, finish date, status) transfer via the XML export path. We validate that the destination Project Plan uses the correct Fiscal Year start and Calendar settings before import so that date calculations propagate correctly from Twproject's working-day model to Microsoft Project's base calendar.

Twproject Tasks with parent-child hierarchies (WBS) map to Microsoft Project Tasks with outline indent levels. The XML export preserves the hierarchical structure. Task fields migrating include Name, Duration, Start Date, Finish Date, % Complete, Priority, and Notes. Milestones in Twproject (zero-duration tasks) map to Microsoft Project Milestone tasks (Duration = 0). Subtask rollup behavior differs: Twproject calculates parent completion from children; Microsoft Project requires explicit setting of 'Rollup' on the Summary Task.

This is the highest-risk mapping in the pair. Twproject's MS Project XML export deliberately omits cost rates, max units, resource type (Material vs Work), and department metadata — the export includes only name and surname. We pull the full resource record from the Twproject API and reconstruct Microsoft Project Resource Sheet entries with the missing fields restored: Max Units, Std Rate, Cost/Use, Accrue At, Resource Type, and Material Label. This requires a separate API extraction phase that the standard XML export path does not perform.

Twproject task assignments (resource-to-task allocations with percentage or hours) map to Microsoft Project Assignments. The assignment fields migrating include Assigned Resources, Units (%), and Work. Duration-driven scheduling in Microsoft Project recalculates Work unless the project is set to Fixed Work; we flag this scheduling-mode difference during scoping so the customer's PM team can decide whether to preserve Twproject's estimated effort or accept Microsoft Project's automatic calculation.

Twproject Worklogs (hours logged per task per resource per date) are not included in the XML export. We extract worklogs via the Twproject API keyed by task ID and map them to Microsoft Project Assignment timephased data if the destination is Project Online (supports Bulk Update via REST API), or export as a companion CSV timesheet file for the desktop MPP if the destination is Project desktop. We flag that Microsoft Project does not have a native time-tracking UI for worklogs — they require either manual entry or a Power Automate-based timesheet solution.

Twproject's Costs & Revenues section (budget-vs-actual tracking) is excluded from the XML project export. We pull cost records via the Twproject API and map them to Microsoft Project Cost Resources (assigned to tasks as fixed costs or per-unit costs) or to project-level Budget fields. The mapping depends on how Twproject categorized costs (labor vs material vs fixed expense). We document the cost type breakdown during discovery so the customer can confirm which Microsoft Project cost model applies.

Twproject custom fields on tasks migrate as Microsoft Project custom fields. The import dialog during .mpp import allows up to 10 custom fields to be mapped per project. We enumerate all Twproject custom field definitions (name, data type) during discovery and map each to the nearest Microsoft Project custom field type: Text, Flag, Number, Cost, Date, or Outline Code. Fields exceeding the 10-field import limit require the customer to select the priority set and document the remainder for post-migration manual entry.

Twproject project-level custom fields map to Microsoft Project Summary Task custom fields. These display in the Project Information dialog and can be included in reports. We apply the same type-mapping logic (Text, Flag, Number, Cost, Date) and flag any fields that would require custom fields outside the supported import dialog.

Twproject task dependencies transfer through the XML export as Microsoft Project Predecessor/Successor links. We preserve dependency type (FS, SS, FF, SF) and Lead/Lag time. Post-import validation checks for dependency chains that produce negative slack (indicating an impossible schedule) and for circular dependencies (which Microsoft Project flags as an error). Constraint behavior differs: Twproject and Microsoft Project both support Must Start On, Must Finish On, As Late As Possible, but the scheduling engine response to constraints can produce different results when the project uses resource leveling.

Twproject working-time configurations (default working days, holidays, exception days) map to Microsoft Project Base Calendars. We export calendar definitions from Twproject and apply them as the project's base calendar in Microsoft Project. Resource-specific calendars (if a resource has different working hours than the project default) map to Microsoft Project Resource Calendars with the same exception-day logic. We flag any resource calendars with non-standard shifts that may not survive the import intact.

Twproject tags on tasks migrate to a Microsoft Project Text custom field. If tags represent categories that would benefit from hierarchical grouping (e.g., Work Package type, Phase), we map them to an Outline Code custom field. We normalize tag values that contain characters not supported in Microsoft Project field names (special characters, spaces over 50 characters) during the transformation phase.

Twproject ToDos are a lightweight checklist feature within tasks and are explicitly excluded from the XML project export. We flag ToDos during scoping and recommend the customer treat them as non-migratable: active ToDos become a manual checklist entry in the task Notes field, and completed ToDos are archived as part of the migration inventory document delivered alongside the imported .mpp file.