Migrate from Copper to HubSpot

Copper Persons map directly to HubSpot Contacts. The person's name, email, phone, address, job title, and social profiles become standard HubSpot Contact properties. Original Copper create date and last-modified date are preserved in HubSpot custom properties for reporting continuity. Copper's person ID is stored as a custom property to support delta-run de-duplication on subsequent migrations.

Copper Companies map to HubSpot Companies. Company name, domain, industry, employee count, annual revenue, phone, and address fields translate to their HubSpot Company equivalents. Industry picklist values are mapped on a value-by-value basis with unknown values assigned to HubSpot's default. Parent-company hierarchies in Copper map to the HubSpot Parent Company association.

Copper Opportunities become HubSpot Deals. Deal name, value, expected close date, stage, probability, and owner transfer directly. HubSpot Deal pipelines and stages are created to match Copper's pipeline configuration, including stage order, stage names, probability percentages, and forecast categories. Each Copper pipeline results in a corresponding HubSpot deal pipeline.

Copper Leads map to HubSpot Contacts. The Lead status field (New, Working, Nurturing, Unqualified) is translated to a HubSpot custom property (Copper_Lead_Status__c) since HubSpot uses lifecycle stage instead of separate lead status. Leads with no associated Company create a HubSpot Company automatically.

Copper Projects require assessment: Projects tracking sales milestones map to HubSpot Deals with a Project_Type__c custom property set to 'Project'. Projects representing non-deal entities (e.g., implementation work, customer onboarding) map to a HubSpot Custom Object named 'Project' with custom properties mirroring Copper's project fields and milestones.

Copper Tasks map to HubSpot Tasks. Task subject, body, due date, priority, status (complete/incomplete), and owner transfer to HubSpot. Completed status maps to HubSpot's completed checkbox. Open tasks retain their due dates and priority levels. Copper's task association to People or Companies is preserved through HubSpot task associations.

Copper call logs become HubSpot Call Engagements. Call direction (inbound/outbound), duration, outcome, recording link, and timestamp transfer to HubSpot. The engagement is associated to the correct Contact and Company using Copper's association IDs resolved during migration. Call recordings are downloaded and re-uploaded to HubSpot Files, then linked to the Call Engagement.

Copper email logs become HubSpot Email Engagements. Email subject, body (plain text or HTML), timestamp, and status (sent/replied/bounced) transfer to HubSpot. The email engagement is associated to the correct Contact. Note: email body content depends on whether Copper stored the full email or only metadata.

Copper meeting records become HubSpot Meeting Engagements. Meeting title, start time, end time, location, body, and attendees transfer to HubSpot. Attendee email addresses are resolved to HubSpot Contact records where matches exist; unresolved attendees are recorded as text on the engagement.

Copper notes become HubSpot engagements of type 'note'. Notes attached to specific records are associated to the correct Contact, Company, or Deal. The note body, create date, and owner transfer. Rich-text formatting in Copper notes is preserved where the format is compatible with HubSpot's note editor.

Copper custom fields on People (e.g., Birthday, Preferred Language, Referred By) become HubSpot Contact custom properties. Field types are mapped: text fields to single-line text, picklists to single-option or multi-option contact properties, date fields to date properties, number fields to number properties. HubSpot property names use underscores (e.g., referred_by) to match HubSpot naming conventions.

Copper custom fields on Companies (e.g., Tax ID, Billing Cycle, Contract Status) become HubSpot Company custom properties with equivalent data types. Text, number, date, and picklist fields map directly. Multi-select picklists in Copper map to HubSpot multi-checkbox properties.

Copper custom fields on Opportunities (e.g., Contract_Type, Upsell_Potential, Implementation_Owner) become HubSpot Deal custom properties. Stage-dependent fields in Copper require mapping to HubSpot deal properties that can be populated regardless of pipeline stage. All custom properties are created in HubSpot before data loading begins.

Copper's N:N person-to-company associations map to HubSpot Contact-Company associations. If a Copper Person has multiple associated Companies, the primary Company (most recently modified or by your specified rule) becomes the HubSpot primary association, and secondary companies are added as additional associations. Copper's association labels (e.g., Primary Contact, Billing Contact) become HubSpot association labels. Your team can review and adjust the primary designation post-migration.

Copper's Opportunity-to-Person associations (the people involved in a deal) map to HubSpot Deal-Contact associations. HubSpot Deal-Contact associations support an 'impact' field (Primary Decision Maker, Evaluator, End User) to capture deal role information. Copper association labels are translated to HubSpot deal contact roles.

Copper's Opportunity-to-Company association maps directly to HubSpot Deal-Company association. Each HubSpot Deal is associated to one Company. If a Copper Opportunity links to multiple Companies, the primary Company becomes the HubSpot deal association.

Copper Users (owners of records) are matched to HubSpot Users by email address. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback HubSpot owner. No record lands in HubSpot without a valid owner assignment. The fallback owner is designated by your team during planning.

Files attached to Copper records (People, Companies, Opportunities, Projects) are downloaded and re-uploaded to HubSpot Files. Files are associated to the corresponding HubSpot record (Contact, Company, or Deal). File size limits apply: HubSpot's file upload limit is 256MB per file. Files exceeding this limit are flagged for manual handling.