Migrate from Z-Stream to monday Work Management

Z-Stream Projects map 1:1 to monday.com Boards. We carry Project name, description, start/end dates, status, and owner as Board name, description, a Date column, a Status column, and the Board owner. If Z-Stream uses multiple workspaces, each workspace becomes a monday.com Workspace or Team. The first migration step seeds all Boards so that child Tasks have a parent Board to attach to.

Z-Stream Tasks map to monday.com Items within the target Board. We carry title, description, assignee, due date, priority, and status as Item name, description (via a Text column), People column, Date column, a numeric Priority column, and a Status column. Task owner from Z-Stream becomes the Item assignee. Parent-child task relationships (tasks linked under a parent task in Z-Stream) are resolved by creating Items and setting a dependency column if the Board uses subitems.

Z-Stream Subtasks attach to their parent Task by ID. We map Subtasks to monday.com Subitems when the destination Board has Subitems enabled. The Subitem inherits the same column set as the parent Item (title, assignee, due date, status) and the parent-child relationship is preserved by linking Subitems to the parent Item record. We create parent Items before Subitems to satisfy the parent reference at migration time.

Z-Stream Milestones are standalone objects tied to Projects. monday.com has no native milestone object, so we represent milestones as a custom Toggle or Date column on the relevant Items (typically the parent Task that gates the milestone). We add a milestone_flag column with a boolean or label to flag milestone-controlling tasks. If the customer uses a separate milestone tracking sheet, we create a dedicated Board for milestone Items and link them via a Connect Boards column.

Z-Stream Users map to monday.com Users by email address match. We carry name, email, and role/permission level as a custom Text column on the User record or as a board-level permission note. Inactive or archived Z-Stream users are imported as inactive monday.com Users at the customer's request. The customer's monday.com admin provisions the User records before migration so that assignee resolution succeeds during Item import.

Z-Stream Time Entries tie to Tasks and Users with hours, date, and optional notes. monday.com offers a native Time Tracking column on Pro and Enterprise tiers, and a numeric Hours column on all tiers. We map to the native Time Tracking column when the destination plan supports it; otherwise we use a numeric column with a Date sub-column to carry the entry date and a Notes Text column for the description. The time entry owner is resolved to a monday.com User at migration time.

Z-Stream attachments are file references with a filename, blob or URL, and parent object association. We download all files from Z-Stream, chunk them by Project/Board to avoid timeout during re-upload, and attach them to the corresponding monday.com Items using the monday.com file upload API. Large binaries (over 20 MB) are chunked to individual Items. The original folder structure is reconstructed as a naming convention on the files.

Z-Stream custom fields on Projects map to monday.com Board-level columns. We discover the full custom field schema during scoping, type-match each Z-Stream field to the nearest monday.com column type (Text, Number, Date, People, Dropdown, Checkbox, Link, Rating), and pre-create the columns before any Item data loads. Multi-select dropdown options in Z-Stream map to monday.com Dropdown columns with the same option labels.

Z-Stream custom fields on Tasks map to monday.com Item-level columns. We apply the same type-matching logic as Project-level custom fields and pre-create columns on the destination Board before Item import. If a Z-Stream custom field uses a data type not supported by monday.com (e.g., a nested object), we represent it as a Text column with the serialized value and flag it for the customer's admin to reformat post-migration.

Gantt layout in Z-Stream is derived from task start dates, end dates, dependencies, and milestones. We extract structured task data (start, end, duration, predecessor IDs) and rebuild the Timeline view in monday.com by creating a Timeline column with the date range per Item. Dependencies migrate as a Dependency column referencing the predecessor Item IDs. The customer enables the Timeline view on the Board after migration completes.

Z-Stream Kanban columns correspond to custom status values on Tasks. We preserve column names and any column-specific colour labels as a Status column on the monday.com Board. The column order is carried as the order of Status options. If Z-Stream uses horizontal groups within a Kanban board, we represent those as monday.com Groups. The customer may choose to flatten to a single Board or create separate Boards per Kanban board during scoping.

Z-Stream budget amounts stored within Projects map to a set of Numeric columns (Budget Allocated, Budget Spent, Budget Remaining) on the Board or on a dedicated Budget Items board with a Connect Boards column linking to the Project Board. We extract the budget line items from the Z-Stream export and create separate Item records or column values per budget row depending on the structure.

Z-Stream risk entries stored as structured list objects within Projects map to a dedicated Risk Board or to custom columns on the Project Board (Risk Level, Risk Owner, Mitigation Status, Probability). We use a custom Board with Items representing each risk when the register has more than ten entries; otherwise we flatten to columns on the parent Project Board. The risk owner resolves to a monday.com User by email match.

Z-Stream Comments attach to Tasks with an author, timestamp, and body. We import comments as monday.com Updates on the relevant Item, carrying the author name, timestamp, and body text. Updates are imported in chronological order to preserve the discussion thread. If Z-Stream comments use @mentions, we resolve the mentioned user to a monday.com User and include the mention in the Update body.