Migrate your Twproject data

Projects exportable as JSON including structure, details, and user assignments. The export lives in a dedicated button on the project list page and imports into any other Twproject instance. We use this for bulk project scaffolding but supplement with API calls for full fidelity.

Tasks are the primary work unit in Twproject. They support parent-child hierarchies (subtasks), custom fields, assignees, dates, and status. We retrieve all task fields via the get/object/task API call and preserve the full hierarchy in the destination.

Resources in Twproject correspond to user accounts. Each resource carries allocation, cost rates, and department metadata. We map resources to the destination's user object and preserve cost rates as custom properties where the destination supports them.

Worklogs record hours against tasks and are not included in the JSON export. We pull them via API using the task ID association and map them to the destination's time entry object. Date-range scoping is required to avoid pulling excessive historical data.

Twproject tracks project-level costs, additional expenses, and budget-vs-actual forecasts. These live in the Costs & Revenues section and are not exported via the project JSON export. We fetch them via API and map to the destination's cost or budget object, preserving parent-child rollup logic.

Custom fields are supported on tasks and projects. Twproject's documentation describes them as a wizard-driven customization. We enumerate all custom field definitions during discovery and map each to the destination's equivalent custom field, handling type differences (text, date, select, etc.).

Attached documents are not included in the JSON project export. The Twproject support documentation confirms this omission explicitly. We cannot migrate attachments via the standard export path. Customers must handle document migration separately, typically via direct file transfer.

ToDos are a lightweight checklist feature within Twproject and are explicitly excluded from the JSON project export. We flag this to customers during scoping and recommend they either treat ToDos as non-critical or migrate them manually as part of a separate task.

Twproject's Gantt view is built on a Work Breakdown Structure where each project node can have phases, sub-phases, and tasks. The JSON export captures this hierarchy. We preserve parent-child relationships and phase assignments during migration.

Kanban is a daily planning view in Twproject rather than a top-level object. We migrate task assignments and statuses which drive the Kanban display. The board configuration itself (columns, swimlanes) may not be fully portable depending on the destination platform.

Tasks and projects can carry tags. We retrieve tag assignments via API and map them to the destination's tagging system. Some destinations use flat tag lists while others use a taxonomy — we normalize during the mapping phase.

Twproject's resource workload view shows assignment distribution across time. We pull assignment data per resource and reconstruct a workload view in the destination. Note that Twproject stores allocation at the assignment level; we aggregate by resource and period for the migration.

Twproject supports importing and exporting MS Project files. This is useful for cross-platform handoffs. We can use this path for projects that originated in MS Project, preserving task hierarchy and dates. Customers originating in Twproject who need MS Project export as an interim format can use this feature.