Migrate from Copper Project to Trello

Copper Project records map to Trello Boards. We use the Copper Project name as the Board title and project status (Active, On Hold, Completed) as a Board background color or label scheme in Trello. If the Copper workspace uses multiple projects per client, we coordinate with the customer to decide whether to create one Board per project or to use a Workspace containing multiple Boards per client. Archived Copper projects map to Archived Boards in Trello.

Copper Tasks map to Trello Cards within the appropriate Board and List. We use the Copper task name as the Card title, the task description as the Card description, and the task status (New, In Progress, Complete) to determine the initial List placement. Subtasks in Copper become Checklist items on the corresponding Trello Card. Parent-child task relationships are preserved by placing child Cards under the parent Card or by linking them via Card cross-references in the Card description.

Copper task timers record duration against a specific task. Trello has no native time-tracking field. We append a formatted time summary (e.g., 'Time logged: 3h 45m') to the Card description and create a Checklist item with the time entry for visibility. If the customer requires formal time tracking, we document this as requiring a Trello Power-Up (such as a time-tracking integration) that the admin installs post-migration.

Copper file attachments live at the Project or Task level and are stored via a three-step S3 upload process. We retrieve files through the Copper API using the same signed-URL flow, stage them locally, then upload to Trello as Card Attachments via the Trello REST API. We preserve the original filename, file type, and upload date. Files are re-linked to the corresponding Card using the original entity relationship. Large files (over 10 MB) may require Trello API chunking.

Copper Project users (name, email, role) map to Trello Board Members. We match by email address. Any Copper user without a matching Trello account is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Copper users are exported but flagged as such for the admin to review before adding to Trello.

Copper timesheet entries are logged hours per user per day against a task. Trello has no native timesheet object. We summarize each user's timesheet entries per task as a formatted text block appended to the Card description (e.g., 'Timesheet: John Doe - 3h, Jane Smith - 1.5h on 2024-03-15'). This preserves the data in readable form even though it cannot be structured as a native Trello object. Formal timesheet reporting requires a Trello Power-Up or external time-tracking tool.

Copper Project includes a native invoicing module with line items, amounts, and payment status. Trello has no invoicing or billing module. We do not migrate invoices as records. We deliver a written inventory of all Copper invoice records (invoice number, client, line items, amounts, status, dates) as a CSV for the customer's admin to import into their chosen billing tool (FreshBooks, QuickBooks, Stripe, or similar). The invoice inventory is scoped separately during discovery.

Copper Project supports custom fields on Projects. Trello Custom Fields Power-Up (available on Standard and Premium plans) supports text, number, date, dropdown, checkbox, and rating field types. We map each Copper Project custom field to a Trello Custom Field of the matching type. If the destination Trello workspace is on the Free plan, custom field support is unavailable; we fall back to storing values as Board description tags or as a separate CSV inventory alongside the migration.

Copper Task custom fields map to Trello Custom Fields on Cards via the Custom Fields Power-Up. We enumerate all active Copper custom field definitions via the Custom Field Definitions API endpoint before mapping. Field type matching: Copper text fields map to Trello text custom fields; Copper date fields map to Trello date custom fields; Copper dropdown fields map to Trello dropdown custom fields with the same option set. If the destination plan is Free, we store custom field values in the Card description as structured text.

Copper's Related Items feature links entities (e.g., linking a Project to a related Task or a Task to a related File). Trello has no native relational links between Cards beyond Power-Ups. We export these as explicit text links in the Card description (e.g., 'Related: [Task-123]') and deliver a separate Related Items mapping table as a CSV so the admin can rebuild relationships using Trello Card Cross-References Power-Up or a Trello Plus-compatible plugin if required.

Copper Task status values (e.g., New, In Progress, Review, Complete) map to Trello Lists on the destination Board. We create Lists that correspond to the Copper task status values in use. If Copper uses multiple status values that would result in more than ten Lists (Trello's recommended maximum), we consolidate into four to six core Lists (e.g., To Do, In Progress, Review, Done) with the full status history preserved in the Card description or a custom field.

Copper Project automations and workflows are workspace-level configuration that triggers actions based on task events. Trello's Butler automation uses a different trigger-action model and does not import Copper automations as code. We deliver a written inventory of every Copper automation with its trigger conditions, actions, and a recommended Butler equivalent for the admin to rebuild. Butler rebuilds are outside standard migration scope.