Migrate from Efficy CRM to Freshsales

Efficy Company records map directly to Freshsales Account. The Efficy company name becomes the Account Name field and serves as the dedupe key during import. Accounts are imported first because Contacts and Opportunities link to them via foreign key. Efficy's multi-relation model supports nested hierarchies; we flatten single-level hierarchies into Freshsales Account parent relationships and flag deeper nesting for manual configuration post-migration.

Efficy Contacts map to Freshsales Contacts. Standard properties (name, email, phone, address) transfer directly. The Company linkage from Efficy (KCompany) resolves to the Freshsales Account lookup at migration time. Multi-address support in Efficy maps to the primary address fields in Freshsales; secondary addresses are stored in a custom field for reconciliation. Custom fields on Contact migrate as Freshsales custom fields of equivalent type (picklist, date, numeric, text).

Efficy Opportunities map to Freshsales Deal. The dealstage property maps to Freshsales Deal Stage, and the pipeline assignment maps to a Freshsales Deal pipeline that we configure before migration. Deal value, expected close date, and owner assignment transfer directly. Efficy's Closed-Lost and Closed-Won reason fields map to Freshsales custom fields on Deal if configured in the destination.

Efficy Activities (calls, emails, meetings, tasks) are logged against Contacts and Opportunities. We map Efficy call logs to Freshsales Task with type set to Call; meeting logs to Appointment; tasks to Task; and notes to Note. The parent linkage (Contact or Deal reference) resolves at migration time via foreign key lookup against the migrated record IDs. Some Efficy activity types may require mapping to Freshsales custom activity fields if the destination uses a non-standard activity schema.

Efficy Projects include Kanban views, milestones, and resource assignments. Freshsales does not have a native project management module. If the customer uses Projects primarily as a deal grouping mechanism, we map them to Freshsales Deals with a custom project identifier field. If Projects represent a distinct data model, we recommend a Freshsales Custom Module (Pro tier and above) and configure the schema before migration.

Efficy Tickets with status, priority, and agent assignment map to Freshsales Case if the destination includes Service Cloud functionality. Ticket conversations migrate as threaded comments on the Case record. Custom ticket fields transfer as Case custom fields. If Service Cloud is not active in the destination Freshsales org, tickets migrate as Notes attached to the related Account or Contact.

Efficy custom fields on all major objects (Company, Contact, Opportunity, Ticket) are extracted during scoping and mapped to Freshsales custom fields of equivalent type. Picklist values in Efficy map to Freshsales dropdown fields; multi-select picklists map to Freshsales multi-select fields; date fields require format validation against the Freshsales CRM Settings date format before import. We validate the full field schema per object during discovery.

Efficy Users carry roles and assignments that map to Freshsales User records. We resolve Efficy users by email match against the Freshsales user table. Inactive users in Efficy are excluded from the active user count but their historical assignments (owner on Contact, Opportunity, Ticket) are preserved and mapped to the corresponding Freshsales User record for audit continuity.

Tags in Efficy are object-level labels that map directly to Tags in Freshsales. We flatten multi-tag assignments per record during transformation so that each tag value appears as a separate Tag record linked to the parent Contact, Account, or Deal. Tags used for segmentation are preserved in a dedicated tags field rather than lost during import.