Migrate your Z-Stream data

Projects are the top-level container in Z-Stream and map 1:1 to most destination PM tools. We preserve the project name, description, start/end dates, status, and owner. If the destination uses a workspace/team model, we map Z-Stream projects to that structure.

Tasks inherit parent Project ownership and carry standard fields: title, description, assignee, due date, priority, status, and estimated hours. We preserve the full task hierarchy including any subtask nesting depth.

Subtasks attach to their parent Task by ID. We carry across the same field set as Tasks and preserve the parent-child relationship at the destination by creating subtasks after parent tasks are seeded.

Milestones are standalone objects in Z-Stream tied to Projects. Not all destination PM tools have a native milestone concept. Where absent, we represent milestones as a custom milestone_flag property on the corresponding target task.

User records map by email address and name. Role/permission levels are carried as a custom property. We flag any inactive or archived users during scoping — these can be imported as inactive records or excluded by agreement.

Time entries in Z-Stream are tied to Tasks and Users with hours, date, and optional notes. Some destination tools track time natively while others require a custom time-tracking integration. We map to a time entry object where available or to a text field on the task.

Attachments are stored as file references with a filename, URL or blob, and parent object association. We download and re-upload all files. Large binaries are chunked by project to avoid timeout during the download step.

Z-Stream supports custom fields on Projects and Tasks. We discover the full field schema during scoping and generate a mapping table against the destination custom field names. Dropdown options and multi-select values are remapped individually.

Gantt layout is derived from task start dates, end dates, dependencies, and milestones. We extract this as structured data and rebuild the Gantt view at the destination by sequencing tasks with their dependency edges.

Kanban columns in Z-Stream correspond to custom status values on Tasks. We preserve the column order and any column-specific colour labels as a custom property at the destination.

Budget amounts and risk entries are stored as structured fields within Projects or as separate list objects. Where the destination has a native risk register, we map entries into it; otherwise we flatten them to custom text fields on the project.

Comments attach to Tasks and carry an author, timestamp, and body. We import them as threaded notes. Some destination tools do not have a comment object on tasks — in those cases we attach comments to the task description as a dated block.