Skip to content
Get a quote

Copper to HubSpot migration

Moving from Copper CRM to HubSpot CRM opens access to HubSpot's full marketing-sales-service platform, unlimited contact storage on paid tiers, and the ecosystem of 875+ integrations. FlitStack AI maps every Copper Person, Company, Opportunity, and Project into HubSpot's Contacts, Companies, Deals, and custom objects — preserving original create dates, owner assignments, and association links so your HubSpot instance reflects the complete relationship graph from day one.

Short answer

FlitStack AI migrates contacts, companies, deals, custom object or deals and tasks from Copper to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records.

By

Source Copper
DestinationHubSpot
ContactCompanyDealCustom Object or DealTask
Mapped field by field · sample run · one-click rollback

What moves from Copper to HubSpot?

Copper CRM and HubSpot CRM take fundamentally different approaches to data organization.

Read the full summary

Copper uses a flat object model where People, Companies, and Opportunities link through direct association IDs. HubSpot uses a property-based model where Contacts, Companies, and Deals each have a unified set of standard and custom properties, with lifecycle stage as the primary contact classification mechanism rather than separate Lead and Contact objects. We map Copper People to HubSpot Contacts, Copper Companies to HubSpot Companies, and Copper Opportunities to HubSpot Deals. Lead records in Copper route to HubSpot Contacts tagged with a migrated lifecycle stage value. Projects in Copper become either HubSpot Deals or HubSpot Custom Objects depending on whether they map to the deal lifecycle or represent a distinct entity type. Activity history (calls, emails, meetings, notes) migrates as HubSpot Engagements with original timestamps and owner attribution preserved. Custom fields in Copper translate to HubSpot custom properties with equivalent data types — text, number, date, picklist, or currency. The migration uses Copper's REST API with its 180 requests-per-minute rate limit, extracting all objects in dependency order (Companies first, then People, then Opportunities with their association links) and loading into HubSpot via the Contacts API, Companies API, Deals API, and Associations API. Automations, workflows, and project templates in Copper do not migrate — those require a separate rebuild effort in HubSpot's workflow builder, and we provide an export of Copper's automation definitions to accelerate that work.

direct

Person → Contact

Copper Persons map directly to HubSpot Contacts.

How it maps

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.

direct

Company → Company

Copper Companies map to HubSpot Companies.

How it maps

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.

direct

Opportunity → Deal

Copper Opportunities become HubSpot Deals.

How it maps

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.

transformed

Lead → Contact

Copper Leads map to HubSpot Contacts.

How it maps

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.

custom_field_required

Project → Custom Object or Deal

Copper Projects require assessment: Projects tracking sales milestones map to HubSpot Deals with a Project_Type__c custom property set to 'Project'.

How it maps

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.

direct

Task → Task

Copper Tasks map to HubSpot Tasks.

How it maps

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.

What moves18 objects
CopperHubSpot
  • PersonContact1:1
  • CompanyCompany1:1
  • OpportunityDeal1:1
  • LeadContacttransformed
  • ProjectCustom Object or Dealtransformed
  • TaskTask1:1

+ 12 more in the mapping below

How Copper and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionCopperHubSpot
Contact Storage LimitsCopper Starter caps at 1,000 contacts, Basic at 2,500, Professional at 15,000. Business tier offers unlimited contacts.HubSpot Starter includes 1,000,000 contacts included. Paid tiers remove all per-contact limits entirely.
Workflow AutomationCopper Professional and Business tiers include workflow automation with triggers, actions, and time delays.HubSpot includes workflow automation starting at Starter tier, with advanced features in Professional and Enterprise.
Email IntegrationCopper automatically logs Gmail emails to contact records via Google Workspace Chrome extension with bidirectional sync.HubSpot Sales Chrome extension logs emails and tracks engagement, with Gmail and Outlook integrations, plus optional email connection settings.
Pipeline ModelCopper supports multiple pipelines with customizable stages per pipeline. Each opportunity belongs to one pipeline.HubSpot supports multiple deal pipelines with customizable stages, probability weights, and forecast categories per pipeline.
Pricing StructureCopper charges per seat with contact limits: Starter $9/seat, Basic $23/seat, Professional $59/seat, Business $99/seat (annual pricing).HubSpot CRM is free for unlimited users with paid tiers starting at $50/month for the CRM Bundle. Marketing and service hubs priced separately.
Custom ObjectsCopper supports custom fields on People, Companies, Opportunities, Projects, and Tasks. No standalone custom object type.HubSpot Custom Objects (Enterprise only) allow creating standalone object types with custom properties and associations to Contacts, Companies, and Deals.
Association ModelCopper uses direct association IDs linking People to Companies and Opportunities. Each person can have multiple company associations.HubSpot uses association labels between Contacts and Companies. N:N relationships supported via multiple associations or association properties.

Copper to HubSpot field mapping

The 30 most-used fields of 46 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
CopperHubSpot
  1. namePerson firstnameContact
  2. last_namePerson lastnameContact
  3. emailPerson emailContact
  4. phone_numberPerson phoneContact
  5. mobile_phonePerson mobilephoneContact
Copper fieldHubSpot fieldMappingNote
Person.nameContact.firstnamedirect
Person.last_nameContact.lastnamedirect
Person.emailContact.emaildirect
Person.phone_numberContact.phonedirect
Person.mobile_phoneContact.mobilephonedirect
Person.titleContact.jobtitledirect
Person.linkedin_urlContact.linkedin_facepiledirect
Person.addressContact.addressdirect
Person.cityContact.citydirect
Person.stateContact.statedirect
Person.postal_codeContact.zipdirect
Person.countryContact.countrydirect
Person.websiteContact.websitedirect
Person.birthdayContact.date_of_birthcustom_field_requiredBirthday is a custom property in HubSpot; created as date type property.
Person.owner_idContact.hubspot_owner_idtransformedCopper owner email matched to HubSpot user; unresolved owners flagged before migration.
Person.created_atContact.original_create_datecustom_field_requiredHubSpot CreatedDate reflects migration time; original Copper create date preserved as custom datetime.
Person.copper_idContact.copper_person_idcustom_field_requiredStores Copper's internal ID for traceability and delta-run de-duplication.
Company.nameCompany.namedirect
Company.domainCompany.domaindirect
Company.phone_numberCompany.phonedirect
Company.addressCompany.addressdirect
Company.cityCompany.citydirect
Company.stateCompany.statedirect
Company.postal_codeCompany.zipdirect
Company.countryCompany.countrydirect
Company.industryCompany.industryvalue_mappingIndustry picklist values mapped value-by-value; unknown values set to HubSpot default.
Company.employee_countCompany.numberofemployeesdirect
Company.annual_revenueCompany.annualrevenuedirect
Company.owner_idCompany.hubspot_owner_idtransformedCopper owner email matched to HubSpot user; unresolved owners flagged.
Company.copper_idCompany.copper_company_idcustom_field_requiredStores Copper's internal ID for traceability and delta-run de-duplication.

What to watch for in a Copper to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Copper's N:N person-company associations require primary-company resolution

Copper allows a single Person record to associate with multiple Company records, with one marked as primary.

How we handle it

HubSpot's Contact-Company association model also supports multiple associations, but HubSpot reports and workflows often treat the 'primary' company association differently than secondary ones. We migrate the primary association first and surface all secondary associations for your team to review. If Copper had a person linked to three companies without a designated primary, the most-recently-modified company becomes the HubSpot primary by default — you can override this rule before migration commits.

high

Copper Projects may require HubSpot Custom Objects (Enterprise only)

Copper's Project object tracks non-opportunity work items like implementation milestones or customer onboarding tasks.

How we handle it

HubSpot's standard Deals object handles sales opportunities well but is not designed for project management. If your Copper Projects contain milestones, dependencies, or task breakdowns that need to migrate as structured data, they require HubSpot Custom Objects — which are gated behind HubSpot Enterprise pricing. We assess each Project's data structure and recommend whether it maps cleanly to Deals or requires Custom Object setup in your HubSpot account.

medium

Email body content depends on Copper's storage model

Copper's email logging via Gmail integration may store only metadata (sender, recipient, timestamp, subject) rather than the full email body, depending on your Copper plan and Gmail sync configuration.

How we handle it

If the full body is present, we migrate it as a HubSpot Email engagement. If only metadata is available, the engagement appears in HubSpot with subject and timestamp but blank body. We audit your Copper email data before migration and report exactly what will transfer so you can decide whether to adjust Copper's email logging settings before extraction.

medium

Copper's 180 requests-per-minute API rate limit extends extraction time

Copper's REST API enforces a rate limit of 180 requests per minute per API key.

How we handle it

Large Copper accounts with 200,000+ records may require several hours of extraction time just to pull the data, before any transformation or loading into HubSpot. We use batch endpoints where available, pre-fetch association IDs to minimize follow-up requests, and run extraction in off-peak hours to maximize throughput within the rate limit window. The extraction phase is the longest single step in most Copper-to-HubSpot migrations.

low

Workflow automations and sequence logic do not transfer

Copper's workflow automation engine (available on Professional and Business tiers) builds automated actions triggered by record changes, field updates, or time delays.

How we handle it

HubSpot has its own workflow engine with a different trigger-action model. There is no automatic conversion between Copper workflows and HubSpot workflows — the logic must be rebuilt manually in HubSpot's workflow builder. We export a machine-readable summary of your Copper workflow definitions (triggers, conditions, actions) that your HubSpot admin can use as a rebuild reference. The same applies to Copper's bulk email sequences.

How the migration runs

  1. Audit Copper data structure and associations

    FlitStack AI connects to your Copper account via API using read-only credentials.

    What this step covers

    We extract a full inventory of all object types, record counts, custom field definitions, and association links. We specifically audit person-company associations (N:N resolution), project record structures (deal-like vs. custom-object-like), email logging depth, and workflow definitions for rebuild reference. The audit produces a migration plan document that identifies which objects map directly, which require custom property creation, and which need a rebuild-only approach (automations, templates).

  2. Create HubSpot properties and pipelines

    Before data loading begins, FlitStack AI creates all required HubSpot custom properties (Contact, Company, Deal) to match Copper's custom field definitions.

    What this step covers

    Data types are mapped: Copper text fields become HubSpot single-line text, picklists become single-option or multi-option properties, date fields become date properties. We also create HubSpot deal pipelines and stages to match Copper's pipeline configuration, including stage probability weights. This step runs in parallel with Copper data extraction to save time.

  3. Extract and sequence data by dependency order

    Copper data is extracted in dependency order: Companies first (they have no dependencies), then People and Leads, then Opportunities, then Tasks, then Activities (calls, emails, meetings, notes).

    What this step covers

    Association IDs are collected during extraction and resolved to HubSpot record IDs after each batch loads. Extraction respects Copper's 180 requests-per-minute API rate limit. For accounts with more than 100,000 records, extraction may run over multiple hours or overnight to stay within rate limits without impacting your team's Copper performance.

  4. Run sample migration with field-level verification

    A representative sample (typically 200–500 records spanning all object types) migrates first.

    What this step covers

    We generate a field-level diff comparing source values in Copper against destination values in HubSpot. You review the sample to verify: person-to-contact mapping, company-to-account mapping, opportunity-to-deal stage mapping, association preservation (person-company, opportunity-contact), owner resolution, and date preservation. We correct any mapping errors before committing the full migration run.

  5. Execute full migration with delta-pickup window

    The full data migration runs against your HubSpot account.

    What this step covers

    Records are loaded in dependency order with foreign-key resolution as each batch completes. A delta-pickup window (24–48 hours after initial load) captures any records created or modified in Copper during the migration window. The delta run applies only new records and changed field values, avoiding duplicates. All operations are logged to an audit trail. One-click rollback reverts the HubSpot account to its pre-migration state if reconciliation uncovers data integrity issues.

Copper HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 25,000 recordsTypical, smaller accounts
5–10 days for over 200,000 records or complex custom object setupsLarge or heavily customised accounts

Copper to HubSpot migrations typically land in the mid-range because Copper's data model is relatively close to HubSpot's Contacts-Companies-Deals structure, reducing transformation complexity. Costs scale with record volume (especially Opportunities with many association links), the number of custom fields requiring property creation in HubSpot, and whether Projects map to standard Deals or require Custom Object setup. Migrations with more than five custom fields per object, multiple pipelines, or significant activity history (email logs, call records) extend into the upper range. The delta-pickup window and association preservation steps add processing time but are included in the base scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Copper to HubSpot →

Why teams move from Copper to HubSpot

  • Copper's contact storage limits on lower tiers force teams to upgrade to Professional or Business as they grow — HubSpot's free tier includes unlimited contacts, making HubSpot more cost-effective at the same scale. G2 reviewers consistently cite Copper's per-seat pricing plus contact caps as a budget surprise once teams exceed 2,500 contacts.
  • Copper's workflow automation is gated behind the Professional tier at $59/seat/month. HubSpot includes workflow automation starting at Starter, and the broader HubSpot platform (Marketing Hub, Service Hub) integrates natively with Sales Hub workflows — Copper has no equivalent marketing or service management modules.
  • HubSpot's 875+ integrations and open API offer more connection options than Copper's focused Google Workspace integration. Teams migrating from Copper often cite the need for integrations that only HubSpot's ecosystem supports natively, including advanced marketing automation, referral tracking, and custom reporting tools.
  • Copper's reporting capabilities are limited to the built-in dashboards. HubSpot offers deeper analytics, custom report builder, and integration with BI tools. Reviewers who need revenue forecasting, cohort analysis, or pipeline velocity reports find Copper's reporting a constraint as teams scale.
  • Teams already using HubSpot for marketing or considering HubSpot's full platform can consolidate onto a single CRM with unified contact records, shared properties, and cross-hub automation. Copper does not offer a marketing hub, service hub, or CMS — those require separate tools that don't share data as cleanly.

Questions, answered

Copper to HubSpot migration questions

How long does a Copper to HubSpot CRM migration take?

Most Copper-to-HubSpot migrations complete within 48–72 hours of clock time for accounts under 25,000 records. The longest single phase is often Copper's data extraction, constrained by the API's 180 requests-per-minute rate limit. Accounts exceeding 200,000 records or containing complex Project-to-Custom-Object mappings extend to 5–10 days. HubSpot property and pipeline setup runs in parallel with extraction, so the effective timeline is driven by record volume and the delta-pickup window you choose.

Will my Copper workflows migrate to HubSpot workflows?

No. Copper workflow automations do not transfer to HubSpot — the trigger-action logic, conditions, time delays, and automation rules are platform-specific and cannot be converted automatically. We export a machine-readable summary of your Copper workflow definitions (which triggers, which conditions, which actions) that your HubSpot admin can use as a reference when rebuilding automations in HubSpot's workflow builder. The same applies to Copper's bulk email sequences, which require rebuilding in HubSpot's email sequences tool.

What happens to Copper's Lead records in HubSpot?

Copper Lead records become HubSpot Contacts. The Lead status field (New, Working, Nurturing, Unqualified) is preserved as a custom property on the Contact named copper_lead_status. HubSpot's native lifecycle stage is set to a default value — typically 'lead' — and your team can update lifecycle stage values during the cleanup phase or via a post-migration workflow. We flag any Leads that lack an associated Company so your team can create the Company record and re-associate the Contact.

Can I migrate Copper custom fields to HubSpot?

Yes. Copper custom fields on People, Companies, Opportunities, and Projects migrate to HubSpot custom properties with equivalent data types. Text fields, number fields, date fields, and picklists all map to HubSpot property types. Multi-select picklists in Copper become multi-checkbox properties in HubSpot. Boolean fields map to HubSpot's checkbox property type. Custom properties are created in HubSpot before data loading begins, so all values land in the correct fields on the first import.

What happens to Copper's person-company associations in HubSpot?

Copper's N:N person-to-company associations map to HubSpot's Contact-Company associations. If a Copper Person has multiple associated Companies, we migrate the primary association first and add secondary associations from HubSpot's association menu. Copper association labels (Primary Contact, Billing Contact) translate to HubSpot association labels. Your team can review and adjust the primary designation after migration if the default rule does not match your business logic.

Does the migration affect my Copper account during cutover?

No. FlitStack AI uses scoped read-only API access to Copper — your team continues working in Copper throughout the migration. A delta-pickup window (24–48 hours) captures any records created or modified in Copper during the migration window so HubSpot reflects Copper's final state at go-live. We recommend not deleting records in Copper during the delta window to avoid data loss. After the delta run completes and you verify the HubSpot data, you can decommission the Copper account.

What happens to my Copper email logs and call recordings?

Copper email logs migrate as HubSpot Email Engagements on the associated Contact timeline. Note: Copper may store only metadata (subject, timestamp, participants) rather than full email body depending on your Gmail sync settings — we audit this before migration and report exactly what will transfer. Call recordings attached to Copper call logs are downloaded and re-uploaded to HubSpot Files, then linked to the corresponding Call Engagement. YouTube or video meeting links in Copper notes are preserved as URL properties on the engagement.

How do you handle Copper's 180 requests-per-minute API rate limit during extraction?

Copper's API rate limit of 180 requests per minute is managed through request throttling and batch endpoint usage. We pre-fetch association IDs in a single pass to minimize follow-up lookups, use bulk endpoints where Copper exposes them, and run extraction during off-peak hours to maximize available quota. For accounts with fewer than 50,000 records, extraction typically completes within a few hours. Large accounts may require 8–12 hours of extraction time — this is built into the project timeline and does not incur additional cost.

Get a quote

Moving from Copper to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote