Migrate from Project Drive to monday Work Management

Project Drive Projects map directly to monday.com Boards. The Project name becomes the Board title, description maps to the Board description field, and project status (active, archived, on hold) maps to a Board status column we create during migration. Project Drive's project-level cost and budget fields are flagged for mapping to custom number columns on the Board (see Budget mapping). We create Boards using the monday.com REST API with the workspace and folder location specified during scoping.

Project Drive Tasks map to monday.com Items within the target Board. We preserve task name, description (as Item name and main text column), assignee (as person column), start date, due date, and status. Project Drive status values map to monday.com Status column options. Task ordering within the Gantt sequence is captured from the visual layout and reconstructed using monday.com's group ordering and optional dependency column.

Project Drive Subtasks nest under Tasks. We map each subtask as a monday.com Subitem attached to its parent Item. The parent-child relationship is maintained via monday.com's native subitem structure. Description, assignee, start date, and due date carry over to the subitem. Teams that prefer flat item lists can instead map subtasks as separate Items with a custom parent-reference column; the customer chooses the strategy during scoping.

Project Drive Milestones are date-flagged markers within the Gantt view. They export as standalone task records with a milestone boolean flag. We create each milestone as a monday.com Item with the milestone date in a Date column, a Status column marked as Milestone, and a Name column carrying the milestone title. If the destination monday.com account has the Sprint or milestone app enabled, we apply the milestone tag accordingly.

Project Drive user accounts map to monday.com Workspace Members by email address. We extract every distinct assignee from tasks and match by email against the destination monday.com account's user table. Any assignee without a matching monday.com User goes to a reconciliation queue for the customer's admin to provision before record import. We do not migrate user role or permission data beyond assignee identity.

Project Drive displays task dependencies visually in Gantt view, but exported CSV data may flatten these into ordering position rather than explicit dependency links. We parse the exported Gantt visual layout, reconstruct the dependency graph (identifying predecessor-successor pairs), and apply them as monday.com Dependency column entries on the target Items. Monday.com supports Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish dependency types; we default to Finish-to-Start unless the source data indicates otherwise. This reconstruction step is the most time-intensive part of Gantt-heavy migrations.

Project Drive stores budget and cost data as native project-level fields, but monday.com has no equivalent native field. We map each Project Drive budget field to a custom Number column on the destination Board. The customer chooses during scoping whether to use simple number columns (for manual updates) or to configure Formula columns that compute variance, remaining budget, and percentage consumed. We flag any null or zero budget values in the source export for customer confirmation before loading.

Project Drive task and project attachments export as binary file blobs with original filename and content type preserved. We download each attachment, upload to the customer's monday.com file storage or to a connected Google Drive or Dropbox folder (depending on the customer's preference), and create a monday.com File column entry or URL column entry linking back to the file. File column integration requires that the customer's monday.com account has the relevant integration (Google Drive or Dropbox) connected. We do not migrate file version history.

Project Drive task start_date and due_date fields map directly to monday.com Date columns. If the source export provides only due dates without explicit start dates, we infer start_date from the Gantt sequence ordering or from the predecessor dependency chain. Both dates display in the monday.com Timeline view once the Dependency column is configured.

Project Drive task status values (e.g., Not Started, In Progress, On Hold, Complete) map to monday.com Status column options. We extract the distinct status values from the source export and create matching Status column options in the destination Board during schema setup. Status color assignments follow monday.com conventions (grey for Not Started, blue for In Progress, green for Complete, red for blocked).

Project Drive priority values map to a monday.com Labels column or a Priority column if the destination Board template includes one. Priority labels (High, Medium, Low) become color-coded Labels. If Project Drive stores priority as a numeric score, we convert to a three-tier label system during transformation.

Project Drive project-level start and end dates map to a monday.com Timeline column on the Board. The Timeline column groups Items by their date ranges and displays them in the Timeline view. We extract the earliest task start_date as the project start and the latest task due_date as the project end, or use the project-level dates if Project Drive exposes them directly in the export.