Migrate your Merlin Project data

The top-level container in Merlin Project. Each project file stores all nested objects. We migrate projects by exporting the project file or by extracting Activities, Assignments, and Resources from each project's view exports. Multi-project portfolios require per-project exports.

Tasks in Merlin Project with fields for name, duration, start/end dates, notes, and custom properties. Exported via CSV from the Gantt, WBS, or List views. We preserve the full field set including any custom columns added to the view before export.

Zero-duration markers on the timeline. Exported as Activity rows with a milestone flag in CSV. We preserve milestone status and any associated date constraints during migration.

Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish dependency types are stored per Activity. In CSV export, dependencies appear as predecessor/successor references. We parse these and reconstruct the dependency graph in the destination system, mapping non-standard constraint names where the destination uses different terminology.

Resources represent people, equipment, or materials assignable to Activities. Exported via the Resource view as CSV. We preserve resource names, types, rates, and any custom resource-level fields included in the export.

The linking table between Activities and Resources including allocation percentage and work units. Exported from the Assignment view or as part of a Resource or Activity export. We reconstruct the full assignment matrix in the destination, mapping work vs. material resource assignments appropriately.

Files attached to Activities, Resources, or the Project. Exported via the Attachments view to CSV listing file names and paths. Actual file binaries are stored separately. We extract the CSV list and copy the referenced files to a parallel file-store structure, then re-link them in the destination where supported.

Custom properties defined at the Activity or Resource level within a project. These appear as additional columns in the relevant view exports if the column is visible at export time. We instruct customers to make all custom columns visible before export so we capture the full field set. Custom field schemas must be reviewed per project.

Merlin Project's mind map view captures brainstorming structure but cannot be exported to CSV or any standard file format. We document this as a manual re-creation step. Teams should screenshot the mind map for reference before migration.

The Kanban board view is visual-only in Merlin Project and does not export to CSV. We recommend exporting the equivalent Activity list view with status column visible as a workaround to capture task-stage data before migration.

The network planning view cannot be exported. This is a visualization layer over the dependency and scheduling data already captured in the Activities and Dependencies exports. We treat it as non-exportable and instruct customers to use the dependency CSV as the source of truth.

Merlin Project's built-in reporting generates charts and summaries in-app but has no export format. We advise customers to run any needed reports and take screenshots before migration. The underlying data is captured via Activity and Assignment exports.

Notes attached to Activities, Resources, or the project level. These appear as rich text fields in the export if the Notes column is visible. We include Notes in the column set during scoping and verify it is present in the exported CSV before processing.

Merlin Project flags scheduling conflicts arising from date constraints and dependency order violations. We capture any constraint fields (As Late As Possible, As Soon As Possible, Fixed Dates) present in the export and map them to the equivalent constraint semantics in the destination PM tool.