Migrate from Copper to Freshsales

Copper People records map directly to Freshsales Contact. Standard fields (name, email, phone, address) transfer 1:1. The email address serves as the dedupe key during import. We inspect any Copper custom fields on People and map them to Freshsales custom Contact fields, creating the equivalent custom field definition in Freshsales if it does not already exist. Copper Tags applied to People migrate as Freshsales Contact tags.

Copper Companies map to Freshsales Account. The company domain from Copper becomes the Account Website field. We preserve People-to-Company linkage during migration by resolving AccountId on each Contact record at migration time using the company reference stored in the Copper People record. This ensures every Contact in Freshsales is attached to its parent Account immediately after import.

Copper Opportunities map to Freshsales Deal. The Copper Pipeline Stage maps to the Freshsales Deal Stage, with stage names and order preserved from Copper's pipeline configuration. Deal monetary value (amount) transfers to Freshsales Deal Amount. We preserve the Opportunity's related Company (Account) and People (Contact) lookups so that the Deal is attached to the correct Account and has primary/secondary Contact assignments on day one.

Copper's separate Leads object maps to Freshsales Lead. Lead status from Copper becomes a custom field or maps to Freshsales Lead Status if the values align. We preserve any lead score or qualification data stored in Copper custom fields as Freshsales custom Lead fields. Freshsales uses email as the unique identifier during lead conversion, and duplicate records with matching email addresses merge during conversion, so we run a dedupe check on the Copper Leads export before import.

Copper's pipeline stages map to Freshsales Deal stages within a single Deal pipeline by default. If the Copper account uses multiple pipelines (available on higher tiers), we create separate Freshsales Deal Record Types for each pipeline and configure the relevant stage set per Record Type so that stage values stay scoped per line of business.

Copper Tasks migrate to Freshsales Task with Status, Priority, due date, and assignee preserved. Task association to People (Contact), Companies (Account), or Opportunities (Deal) transfers as the Freshsales Task's related_to lookup. Copper's task completion status maps to Freshsales task status using the standard status values.

Copper Activity records (emails, calls, meetings, notes) migrate as Freshsales Tasks with TaskSubtype set to Call for phone activities, Event records for meetings, and Task records with notes body for note activities. We preserve the activity date and link each record to the migrated Contact (for People) or Account (for Companies) using the parent record lookup. Email body content migrates as the Task notes field. The original Copper timestamp preserves activity timeline ordering.

Copper Projects do not have a direct Freshsales equivalent. We map Projects to a structured set of Freshsales Tasks under a parent-child relationship, using the Project name as the grouping identifier. If the customer's workflow depends on project-level tracking, we recommend a separate project management tool or a Freshsales custom module on higher tiers; the mapping notes document the choice made during scoping.

Copper custom fields on People, Companies, Opportunities, Leads, Projects, and Tasks are enumerated from the Copper Custom Field Definitions API. Each custom field is mapped to an equivalent Freshsales custom field created before migration. Field type compatibility is checked: Copper text maps to Freshsales text, Copper number to Freshsales number, Copper date to Freshsales date, and Copper dropdown to Freshsales picklist. Any field types without a direct Freshsales equivalent are documented and mapped to the closest available type with a note to the customer.

Copper Tags are flat labels applied to People, Companies, and Opportunities. We migrate tags as-is to Freshsales tags on the equivalent objects (Contact, Account, Deal). Tag names and object associations transfer directly. Freshsales uses a unified tag model across objects, matching Copper's approach.

Copper stores attachment files in the user's associated Google Drive account. We do not migrate the actual file bytes as part of the CRM record migration. Instead, we extract attachment metadata (file name, Drive URL, associated Copper record) during scoping and re-link the files in Freshsales by storing the original Drive URL as a custom field or external link field on the migrated record. The customer's admin must ensure the Google Drive files remain accessible and shared with the appropriate Freshsales users. Actual file migration out of Google Drive is a separate coordination item.