Migrate from Copper Project to Microsoft Project

Copper Project records map directly to Microsoft Project as the top-level container. We export Project Name, status, planned start and end dates, description, and custom field values from Copper, then recreate the project in MS Project using the same name and dates. Project-level custom fields require manual recreation in MS Project's column editor since there is no bulk field creation API for the desktop client. We document every custom field present on each project so the customer can recreate them post-migration.

Copper Tasks map to MS Project Tasks with Name, Start, Finish, Duration, and % Complete preserved. If Copper stores Work (hours) rather than Duration (days), we convert using an 8-hour-per-day factor agreed upon during scoping. Subtasks in Copper map to MS Project outline hierarchy with the parent task ID resolving to the summary task row. Task-level custom fields are recreated as MS Project custom fields per project.

Copper's Related Items feature links Tasks to other Tasks, Projects, or external records. We export all Related Items where the relationship is task-to-task and map them to MS Project predecessor fields with the appropriate dependency type: finish-to-start (FS) as the default, start-to-start (SS), finish-to-finish (FF), or start-to-finish (SF) based on the related item type. We validate that predecessor application does not create circular dependencies or negative lag, and flag any constraint types that cannot be represented in MS Project's scheduling engine for admin review before import.

Copper task assignees map to MS Project resource assignments on a per-task basis. We resolve Copper users to the MS Project resource pool by matching email address, then allocate the assignment as hours or percentage units proportional to the Copper task's estimated duration. Resource leveling in MS Project is configured per the customer's standard (auto-leveling, manual, or none) and documented in the handoff report. Assignees without a matching MS Project resource are held in the reconciliation queue.

Copper custom fields on Projects and Tasks are not migratable through any native MS Project import pathway. We enumerate all active Copper custom field definitions during discovery, export the field values per record, and deliver a written custom field mapping document specifying the MS Project custom field name, type (text, number, date, flag, or cost), and the per-record values for the customer's admin to manually enter post-migration. Custom field schema is not bulk-loaded into MS Project desktop versions.

Copper task timers record elapsed time against a task by a specific user. We export timer records during the scoping phase (coordinating with Copper Support as needed for large volumes), sum the total duration per task, and map the total to the MS Project Actual Work field on the corresponding task. The hours-to-days conversion factor (default 8h/day) is agreed upon before migration. Task timer records are logged in the handoff report with the original timer start time, end time, user, and Copper task ID.

Copper active users map to MS Project resources in the resource pool. We export name, email, and role from Copper, then create MS Project resources with the user name as the resource name and the email recorded in a custom resource field. Inactive Copper users are exported and flagged for the customer to decide whether to include them in the resource pool or treat them as historical-only. MS Project resource types (material vs. work) are configured per the customer's standard during scoping.

Copper files attached at the project or task level are downloaded to a local staging directory with the Copper entity ID and relationship preserved in the file name. MS Project stores file attachments locally or references SharePoint locations; there is no native bulk attachment import from an external URL-based storage system. We deliver a file inventory report listing each file's original name, size, related Copper entity, and recommended SharePoint or local path in the destination. The customer or their admin re-attaches files post-migration.

Copper invoices include line items, amounts, status, and payment information. Microsoft Project has no invoicing or billing module. We export Copper invoices as a CSV report and deliver it alongside the migration as a reference document. The customer must adopt a separate billing system for invoice management post-migration. We document the invoice field mapping (invoice number, line item description, quantity, rate, total, status) as part of the handoff report for integration into the customer's chosen billing platform.

Copper timesheet records (distinct from task-level timers) represent logged hours by user against a date range and project. Microsoft Project does not have a native timesheet object. We coordinate with Copper Support during scoping to obtain the timesheet export, then deliver it as a dated CSV report organized by user and project. The customer integrates this into their chosen timesheet system (Microsoft Project Online's PWA, Smartsheet Timesheets, or a standalone tool) as a separate post-migration step.