Migrate from Copper Project to monday Work Management

Copper Projects map to monday.com Boards as the top-level container. Project name, description, status, start and due dates, and custom field values map to Board name, description, and column values. Each Board is created with a matching workspace or team if the customer uses monday.com's team structure. Note that monday.com Boards are workspaces-level entities while Copper Projects are workspace-level; we preserve the containment hierarchy by creating Boards in the equivalent organizational unit.

Copper Tasks map to monday.com Items within the corresponding Board. Task name becomes Item name, assignees map to the Person column, due date maps to the Date column, and status maps to a Status column. Subtasks in Copper map to Subitems in monday.com, preserving the parent-child relationship through the subitem hierarchy. We resolve the parent task reference during import to ensure the subitem is nested under the correct Item.

Copper Task Timers (duration logged per task and user) map to monday.com's native Time Tracking column on Items. The timer duration, user, and timestamp map to the time tracking entry's duration, assignee, and date. Note that monday.com time tracking is available on the Pro plan ($19/seat); if the customer is on Standard ($12/seat), we map timer data to a Number column formatted as hours instead, noting the limitation. We flag this during scoping if the destination plan lacks native time tracking.

Copper timesheet records (logged hours per user, per date, with project and task association) map to monday.com time tracking entries or Number columns depending on plan tier. Copper timesheets are a distinct object from task timers, representing aggregate logged hours. We extract these records during Copper Support coordination (required for export) and reconstruct them as time tracking entries on the corresponding Board Items. If the customer does not have time tracking enabled in monday.com, we store hours in a Number column and document the upgrade path to Pro.

Copper files attached at Project or Task level are retrieved via Copper's S3 signed-URL process: we fetch the signed URL from the Copper API, download the binary from S3 to a local staging area, then upload to monday.com as a File Upload column value on the corresponding Item. File metadata (name, type, size, upload date, uploader) is preserved in the monday.com file attachment record. We stage files locally to handle the multi-step process and batch uploads to monday.com's file storage.

Copper Invoice records (line items, amounts, status) have no direct monday.com equivalent. monday.com does not include native invoicing. We map invoice data to a set of custom columns: Status (status column), Amount (currency or number column), Line Items (text or long text column with formatted line item data), and Invoice Date (date column). The customer should evaluate a third-party integration (QuickBooks, Stripe, or Xero) if ongoing invoicing is required; we document the recommended setup during the rebuild handoff.

Copper Users (name, email, role) map to monday.com Team Members. We resolve by email match. Active Copper users are invited to the monday.com workspace with the matching email; inactive users are exported as a separate list for the customer's admin to review. Role information from Copper (admin, member) maps to monday.com permission groups if the customer uses granular access control on Pro or Enterprise.

Copper Project custom fields discovered via the Custom Field Definitions endpoint map to monday.com custom columns on the Board. Field type mapping: Copper text maps to monday.com Text column, Copper number maps to Number column, Copper date maps to Date column, Copper dropdown maps to Status column, and Copper person maps to Person column. Custom field values per project record migrate as column values. Each Board has its own column schema in monday.com, so we replicate the custom field definitions per Board.

Copper Task custom fields map to monday.com custom columns at the Item level. We follow the same type-mapping logic as Project-level custom fields. Note that monday.com column types include formula columns (Pro tier), dependency columns, and link-to-item columns that can represent more complex data relationships than Copper's custom field model.

Copper's Related Items feature (explicit relational links between entities) maps to monday.com's Relations column. Each Related Items link type in Copper becomes a Relations column in monday.com. We export the related-item pairs during data extraction and create corresponding Relations column values pointing to the migrated Items in the destination Boards.

If Copper Projects contain nested project groups or folder structures, we map these to monday.com Workspaces, Board Folders, or nested Board structures depending on the customer's organizational model. monday.com supports workspaces at the top level, board folders within workspaces, and individual Boards. We preserve the hierarchy by documenting the original project structure and creating a matching folder-board arrangement in monday.com during migration.

Copper Field Layouts control which fields are visible per entity type in the Copper UI. These are workspace-level display preferences and carry no data content. monday.com column visibility is controlled per Board via the column configuration. We do not migrate Field Layouts; the customer's admin configures column visibility in monday.com Boards after migration. We flag this as a post-migration admin task during the rebuild handoff.