Migrate from ELMA365 to Nutshell

ELMA365 Contact records map to Nutshell Person objects. The ELMA365 contact name, email address, phone number, and organizational assignment (if the contact is linked to an ELMA365 Company) migrate directly. If the ELMA365 instance uses custom fields on Contact, we create equivalent custom fields in Nutshell (available for Companies, People, and Leads per Nutshell's field management documentation) before import. Email addresses serve as the primary dedupe key during Nutshell import.

ELMA365 Company records map to Nutshell Company objects. Company name, website, address, and any custom fields migrate. If the ELMA365 Company has associated Contacts, we create the Nutshell Company first and then associate the related Person records via the Company link during import. ELMA365's organizational hierarchy (parent-subsidiary relationships within the HUB) maps as a flat list of Nutshell Companies; hierarchical company structures require admin review post-migration.

ELMA365 Task records map to Nutshell Activity records of type Task. Task title, description, due date, assignee (mapped to Nutshell User by email resolution), and status (open/closed) transfer directly. We preserve the original ELMA365 creation timestamp as an activity note for audit. Completed ELMA365 tasks become completed Nutshell Activities; open tasks become open Activities.

ELMA365 Project records do not have a direct Nutshell equivalent. We map each ELMA365 Project to a Nutshell Deal that serves as the project-level container, and map the project's constituent Tasks to Nutshell Activities linked to that Deal. This preserves the project structure while fitting it into Nutshell's data model. Project-level custom fields become Deal custom fields in Nutshell.

ELMA365 Process Instances (running or historical BPM process records) carry state data, step names, and field values. We map each Process Instance to a Nutshell Deal with the process step name stored in a custom Deal field and the process state preserved as a note entry. Active process instances may require customer input on whether to migrate as open Deals or as historical records.

ELMA365 email engagements map to Nutshell Activity records or Notes attached to the relevant Person or Company. The email body, timestamp, and sender/recipient addresses transfer. If ELMA365 stores emails as separate objects with thread associations, we reconstruct the thread by grouping on subject and timestamp and attach as a linked Note to the primary Person record.

ELMA365 call engagements (call logs with duration and disposition) map to Nutshell Activity records. Call duration, direction (inbound/outbound), and disposition transfer to custom Activity fields if configured in Nutshell. The original ELMA365 timestamp preserves the activity timeline ordering. Recording URLs stored in ELMA365 are documented separately for manual re-association by the customer's team.

ELMA365 meeting records (meeting title, date, attendees, location, notes) map to Nutshell Activities or Notes attached to the relevant Person records. Attendees resolve to Nutshell Person records by email match. We preserve the meeting date as the Activity date and the meeting body as the Activity description.

Documents attached to ELMA365 Tasks, Projects, or Process Instances are downloaded from ELMA365's file store and re-uploaded as file attachments to the corresponding Nutshell records (Person, Company, or Deal). Folder hierarchy is flattened during import and documented separately for the customer's admin to reorganize if needed.

ELMA365 Users and employee directory records map to Nutshell Users. Resolution is by email address. Any ELMA365 User without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import continues. Role and department assignments from ELMA365 are stored as notes on the Nutshell User record since Nutshell's permission model differs from ELMA365's role framework.

Custom Applications built in ELMA365's low-code designer store data in custom-defined tables with schemas extracted from ELMA365's configuration export. We reverse-engineer each custom Application schema and map it to Nutshell's equivalent custom fields on the nearest standard object (Person, Company, or Deal). If a Custom Application has no clear CRM analog, we document the schema and recommend a rebuild approach in Nutshell. Custom Application lookup relationships to standard objects resolve during migration as cross-object references in Nutshell.

ELMA365 BPMN workflow definitions store as JSON configuration within ELMA365 and have no direct equivalent in Nutshell. We do not migrate workflow definitions as code. We export every process definition, step name, transition logic, and assignee rule and deliver them as a written inventory document with recommended Nutshell equivalents (email templates, automated sequences, or manual process notes). The customer's admin rebuilds workflow logic post-migration.