Migrate from Efficy CRM to Nutshell

Efficy Company records map directly to Nutshell Companies. Company name, address, phone, website, and industry fields are standard on both platforms. We use Company name as the dedupe key during import. Efficy's custom fields on Companies (e.g., VAT number, sector classification) are extracted during scoping and mapped to Nutshell custom fields, which are created in the account settings panel before the import batch runs.

Efficy Contact records map to Nutshell People. First name, last name, email, phone, and address fields map directly. The Contact-to-Company linkage in Efficy (foreign key to Company) is preserved by resolving the Company lookup in Nutshell during import so that the Person record attaches to the correct Company. Multi-address contacts in Efficy require flattening to a single primary address in Nutshell unless the customer's workflow splits addresses manually after migration.

Efficy Opportunities map to Nutshell Deals. Deal name, value (amount), stage, expected close date, and owner assignment transfer directly. Efficy's dealstage values are mapped to Nutshell's default pipeline stages (Qualified Lead, Proposal Sent, Decision Maker Bought In, Contract Sent, Closed Won, Closed Lost) and the customer configures any non-standard Efficy stages as custom pipeline stages in Nutshell before migration.

Efficy Activity records (calls, emails, meetings, tasks) log against Contacts and Opportunities. We preserve the parent linkage by mapping the activity type to Nutshell's Activity model. Call logs, meeting notes, and tasks migrate as Nutshell Activities with the original timestamp and assigned owner. Efficy conversation threads attached to Tickets may need to be flattened into Note records if they reference a specific context that Nutshell's activity model does not capture natively.

Efficy's Project module includes Kanban views, milestones, and resource management that have no direct Nutshell equivalent. We do not migrate Projects as a native object. We extract the project list, key milestone dates, and linked Contacts during scoping and deliver them as a written project inventory. The customer's Nutshell admin maps project milestones to Deal milestones, tasks to Nutshell Activities, or a project management tool outside Nutshell depending on the team's workflow.

Efficy's Ticket module stores customer service records with status, priority, and agent assignment. Nutshell does not have a native ticket queue. We extract the ticket list, status history, and linked Contacts during scoping. Customer service history is delivered as a written ticket inventory with recommended mapping to Nutshell Activities (for single-threaded support notes) or to a dedicated helpdesk integration post-migration. Custom ticket fields are mapped to Nutshell custom fields on the linked Contact or Company record.

Efficy allows custom fields on all major objects via the Designer. During scoping we extract the complete field schema per object (field name, type, picklist values). Custom field types (text, numeric, date, picklist, checkbox) are mapped to equivalent Nutshell custom field types. Picklist values from Efficy are recreated as options in Nutshell. We recommend creating all destination custom fields before the import batch runs to prevent field-mapping rework.

Efficy object-level tags map to Nutshell Tags on the equivalent object. Tags on Companies map to Nutshell Company tags; tags on Contacts map to Nutshell Person tags; tags on Opportunities map to Nutshell Deal tags. Tags used for segmentation in Efficy are flattened to label lists in Nutshell because Nutshell does not have a native segment or list membership object.

Documents attached to Companies, Contacts, or Opportunities in Efficy are exported as file references. We flag documents with a download URL and include them in the migration package. Documents without a stable URL are listed in a separate attachments report for the customer's admin to upload manually after migration. Large binary attachments may exceed typical API payload limits and are handled separately.