Migrate your Efficy CRM data

Companies are the top-level account entity in Efficy and support custom fields. We migrate them first in the sequence because Contacts and Opportunities link to them. The API exposes them as a searchable object with standard field mapping to destination Company/Account objects.

Contacts in Efficy carry standard properties (name, email, phone, address) plus custom fields. We map them to the destination Contact object preserving the Company linkage via foreign key. Multi-address records are flattened to a primary address during migration.

Opportunities represent the deal pipeline and map cleanly to Deals or Opportunities in most destination CRMs. Stage, value, expected close date, and owner assignment are all migratable. We validate stage names to flag any custom stage configurations.

Activities (calls, emails, meetings, tasks) are logged against Contacts and Opportunities. We preserve the parent linkage but some activity types may require mapping to the destination's activity schema, particularly for calendar-synced events versus manual logs.

Efficy's project management module includes Kanban views, resource management, and milestones. The structure maps to Projects in destination systems but nested tasks and dependencies may need field-level remapping depending on the destination's data model.

The ticketing module stores customer service records with status, priority, and agent assignment. Custom ticket fields require explicit mapping. We preserve conversation history as notes or threaded comments where the destination supports it.

Efficy allows custom fields on all major objects. During migration scoping we extract the full field schema per object to build a mapping table. Custom field types (picklist, date, numeric, text) are translated to the closest equivalent in the destination CRM.

Documents attached to Companies, Contacts, or Opportunities are migrated as file references with URLs or as binary blobs depending on the destination. We flag documents without a download URL and advise on re-upload steps post-migration.

Users in Efficy carry roles and assignments that map to Owner or Assignee fields in destination systems. Inactive users are excluded from the user count mapping but their historical assignments are preserved on records.

Efficy's automation rules and workflow sequences are not exported via the API or Easy Import Wizard. They must be manually rebuilt in the destination. We document every automation trigger, condition, and action during discovery so the customer has a rebuild specification.

Tags in Efficy are object-level labels that map to Tags or Labels in destination CRMs. Segments and list memberships require explicit mapping because not all CRMs support the same list logic. We flatten segment membership into tag equivalents.