Migrate from Effort to Nutshell

Effort Person records map directly to Nutshell People. The primary company association migrates as the Nutshell People record's Company field. If a Person has no company in Effort, it lands as a standalone Nutshell People record without a company link.

Effort Company records map 1:1 to Nutshell Company records. Company name, domain, address, and industry fields map to the equivalent Nutshell fields. Parent-company hierarchies in Effort become parent-company links in Nutshell if both parent and child exist in the migration scope.

Effort Deal records map to Nutshell Deals. Deal name, amount, stage, and close date translate directly. Effort deal owner resolves to a Nutshell user by email match. Nutshell Deal records are created before assigning pipeline stages, since pipeline assignment is a required field on the Deal object.

Effort pipelines become Nutshell Pipelines. Each Effort pipeline stage maps to a corresponding Nutshell Pipeline stage with value-by-value mapping. If Effort uses custom stage names, those names are preserved as Nutshell stage names, and a probability value is assigned per stage in the migration plan.

Effort tasks (including daily reports and attendance entries) migrate as Nutshell Tasks. The original created date is preserved as a custom datetime field if the Nutshell CreatedDate cannot be set directly. Task owner resolves by email match to Nutshell users. Completed task status maps to Nutshell's completed task status.

Effort notes on People, Companies, or Deals migrate as Nutshell Notes attached to the corresponding record. Note content and original creation timestamp are preserved. Notes are linked by record type and ID in the migration mapping table, and we set the note visibility to the same owner as the source Effort note to maintain access control after import.

Effort custom fields on Person records become Nutshell custom fields on the People object. Text, number, date, and pick-list field types map to Nutshell equivalent types. Pick-list fields require value-by-value mapping if Effort uses custom pick-list options not available in Nutshell's default set.

Effort company-level custom fields migrate as Nutshell Company custom fields. Field type translation follows the same rules as Person custom fields. If a company custom field in Effort references a pick-list, we map each value explicitly to ensure no data loss on import.

Effort Deal custom fields become Nutshell Deal custom fields. Nutshell supports per-deal custom fields scoped to the deal record. These are created before deal migration runs so the import can populate them on first pass. We also translate field type definitions (text, number, date, pick-list) and set the field visibility to the same Nutshell user role that owned the field in Effort, ensuring consistent reporting after migration.

Effort call logs and email references attached to a Person or Deal migrate as Nutshell Tasks with Type set to 'Call' or 'Email'. The original timestamp and owner are preserved. Content notes from the activity are stored in the Task description field.

Effort workflows and automation rules have no direct equivalent in Nutshell's workflow model. Nutshell supports email sequences triggered by pipeline stage changes but does not replicate field-operation automation logic. We export your Effort workflow definitions as a structured document for your Nutshell admin to rebuild using Nutshell's automation tools.

Effort attendance records (check-in times, distance logged, daily reports) do not have a native Nutshell equivalent. These are migrated as Nutshell Tasks linked to the relevant Person record, with the original date, distance, and notes preserved in the Task description. Your team can then decide whether to keep these for historical reference or archive them separately.