Migrate from Daylite to Nutshell

Daylite People map to Nutshell Person records. The Daylite CSV includes first name, last name, email, phone, address, and custom field values with foreign key references to the Company table. We load Nutshell Persons first in the migration sequence, then update each Person record with the resolved Account (Company) reference using a lookup-by-name strategy against the Nutshell Account table after it has been populated. Any Person without a matching Company in Daylite's export is loaded as a standalone Nutshell Person with no Account association and flagged for customer review.

Daylite Companies map to Nutshell Accounts. The export includes company name, industry, website, address, and custom properties. Account is loaded before Person to satisfy the lookup dependency. We use company name as the dedupe key; if a duplicate Account name exists in Nutshell, we append a suffix and flag the record for the customer to merge post-migration. Industry and website fields map directly to Nutshell's standard Account fields.

Daylite Opportunities map to Nutshell Leads for open or early-stage records and Nutshell Deals for qualified, pipeline-active records. We apply a split rule during scoping: Opportunities with a Stage value indicating qualification (as defined by the customer's stage normalization mapping) land as Nutshell Deals linked to the resolved Account and Person. Opportunities in early or unspecified stages land as Leads. The original Daylite stage string is preserved in a custom field on both Nutshell record types for audit and reconciliation.

Daylite Opportunity stages are freeform text strings stored per record, not a managed taxonomy. We deduplicate all unique stage values across the export, deduplicate and normalize them into a customer-reviewed stage mapping table, then configure Nutshell Lead Status values (for migrated Leads) and Deal Stage values (for migrated Deals) before import. Typos and variant names in historical records are preserved verbatim in the raw stage field; the normalized value becomes the target Nutshell stage.

Daylite Projects have no direct Nutshell equivalent because Nutshell is CRM-only without native project management. We discuss the customer's preference during scoping: Projects can migrate as Nutshell Notes attached to the related Account or Deal (preserving project name, status, dates, and description as note body text), or as a custom Projects object that Nutshell creates during the migration if the customer has a Nutshell Enterprise plan. Budget and cost threshold fields from the iOSXpert Time&Budget plugin migrate as custom number fields on the Project mapping target if that plugin table is present in the export.

Daylite Tasks (standalone and sub-tasks) map to Nutshell Tasks. The export includes task title, status, due date, priority, assignee (owner email), and parent project reference. We resolve assignees by email match against Nutshell Users, hold any unresolved owners in a reconciliation queue, and write tasks with status mapping (Open to Open, Completed to Completed, Cancelled to Cancelled). Sub-tasks carry a parent Task foreign key; we preserve the hierarchy by writing the child task with a link back to the parent Nutshell Task ID after the parent insert.

Daylite Appointments map to Nutshell Activities. The CSV includes start time, end time, timezone, all-day flag, location, category, and linked Person and Project IDs. We reconstruct the calendar chronology in Nutshell Activities, setting the activity type to Meeting and preserving the original UTC timestamp as a custom field for ordering. Location and category transfer to standard Nutshell Activity fields where supported; any unmapped category values are written to a custom field for the customer's admin to remap post-migration.

Daylite Notes are freeform text records attached to any object. The export includes the target object type (Person, Company, Opportunity, Project) and ID. We write them to Nutshell as Note records linked via ContentDocumentLink to the corresponding Nutshell record (Person or Account). Notes with no resolvable target (referenced object was deleted in Daylite) are held in a notes-without-parent queue for the customer to review.

Daylite Groups are static groupings of People or Companies used for segmentation. The export is a membership mapping table (group name, member type, member ID). We recreate group membership in Nutshell as Tags on Person and Account records. The customer chooses during scoping whether to create Tags as Nutshell native tags or as custom picklist values on a custom segmentation field.

Daylite custom fields on People, Companies, Opportunities, Projects, Tasks, and Appointments are defined in a separate metadata table within the export and referenced by field ID in the record tables. We extract both the definition table and the value columns, present a custom field mapping worksheet during scoping, and pre-create equivalent custom fields in Nutshell before import. Field type mapping: Daylite text and number map to Nutshell text and number; date maps to date; multi-select maps to a comma-separated text field in Nutshell unless Nutshell's multi-select custom field type is available on the customer's plan.