Migrate from Efficy CRM to Salesforce Sales Cloud

Efficy Company records map directly to Salesforce Account. The Company KCode or ID field becomes the external ID on Account for dedupe during import. We extract Companies first in all migration sequences because Contacts and Opportunities link to them via foreign key. Efficy custom fields on Company map to custom Account fields, and we handle multi-address Companies by creating a primary AccountAddress and any secondary addresses as separate Address records linked via AccountId.

Efficy Contacts with no linked Opportunity map to Salesforce Lead. Efficy Contacts attached to an active Opportunity or already marked as a customer map to Salesforce Contact under an Account. We make this split using Efficy's contact status property and the presence of a linked Opportunity at migration time. The original Efficy contact record ID is preserved in a custom field efficy_contact_id__c for audit and reconciliation.

Efficy Opportunity records map to Salesforce Opportunity with stage, value, expected close date, and owner assignment preserved. Efficy's dealstage and pipeline properties map to Salesforce StageName and a Salesforce Record Type that we configure before migration. Closed-won and closed-lost reasons from Efficy custom fields become Salesforce Loss Reason and Win Reason fields.

Efficy Activities logged against Contacts and Opportunities migrate to Salesforce Task (calls, tasks), Event (meetings), and EmailMessage (emails). We use the Bulk API 2.0 with batch chunking because a mid-market Efficy account may have 200,000+ activity records. The WhatId on each record points to the migrated Opportunity or Account; WhoId points to the migrated Lead or Contact. ActivityDate preserves the original Efficy timestamp for timeline fidelity.

Efficy ticketing module records migrate to Salesforce Case if the destination org includes Service Cloud. Ticket status maps to Case Status, priority maps to Case Priority, and the assigned agent maps to Case Owner. Conversation history from Efficy tickets migrates as EmailMessage records linked to the Case, preserving the full service thread.

Efficy Project module records migrate to a Salesforce custom object named Project__c. Milestones map to child Project Milestone__c records with a lookup back to Project__c. Kanban stage information from Efficy migrates as a picklist field on Project__c. Nested tasks and resource assignments require explicit mapping because Efficy's project structure supports more nesting depth than standard Salesforce custom objects without additional configuration.

Efficy Users map to Salesforce User records by email match. We extract every Owner referenced on Company, Contact, Opportunity, and Activity and match against the Salesforce org's User table. Any Efficy User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Efficy users are excluded from user count but their historical assignments are preserved on the migrated records.

Efficy custom fields on Companies, Contacts, Opportunities, and Activities are extracted during discovery with full schema metadata (field name, type, picklist values, required/optional). Each custom field maps to a typed Salesforce custom field. Picklist fields map to Salesforce Picklist or Multi-Select Picklist with values preserved. Date, numeric, and text field types translate directly. We create all custom fields in the destination org before any data loads to avoid schema mismatch rejections.

Efficy tags are object-level labels that we map to Salesforce Tags (native) or to a multi-select picklist custom field on the relevant object. The customer's admin chooses the preferred strategy during scoping. Tags used for segmentation are flattened into a single text field or mapped to a multi-select picklist depending on downstream reporting needs.

Documents attached to Companies, Contacts, or Opportunities in Efficy migrate as Salesforce ContentDocument records with ContentVersion file bodies. We migrate documents with download URLs accessible via Efficy's API. Documents without a download URL are flagged in the reconciliation report and the customer's admin handles them via manual upload post-migration.

Efficy segments and list memberships are evaluated for migration strategy. Salesforce Campaigns serve as the closest equivalent for audience segmentation. We map Efficy list membership to Campaign Members with a custom field indicating the original Efficy segment name. Complex dynamic segments that depend on Efficy's built-in logic are documented as a configuration note for the customer to rebuild in Salesforce Reports or a complementary segmentation tool.

Efficy's industry-specific configurations (law firms, consultancies, construction, financial services) include vertical-specific fields and workflow templates. We extract the full field schema per industry and map it to Salesforce Record Types with matching Page Layouts and custom fields. Workflow templates do not migrate and are documented for rebuild in Salesforce Flow as part of the automation inventory delivery.