Migrate from Comet Suite to Nutshell

Comet Suite employees map directly to Nutshell People. Name, email, phone, and address fields carry over directly with no transformation required. Employee status (active/inactive) maps to a custom pick-list field on the Nutshell Person record. FlitStack reads the full employee schema from Comet Suite to capture all standard fields and preserve them in the corresponding Nutshell Person object.

Comet Suite employees who are not yet customers in Nutshell land as Leads rather than People. The employee's contact details — name, email, phone, and address — map directly to Nutshell's Lead fields. The Lead stage defaults to 'New' unless a custom status field is present on the source Comet Suite employee record that maps to an existing Nutshell Lead stage value.

Comet Suite locations (client sites, depots, service areas) map to Nutshell Companies. Location name becomes the Company name, and address fields map directly across all standard address components. Multi-level location hierarchies in Comet Suite — such as regions containing multiple sites — map via Nutshell's parent-company field to maintain organizational structure.

Comet Suite job tickets have no direct Nutshell equivalent. Each ticket becomes a Nutshell Deal — the ticket's subject and description map to the Deal name and notes fields. Ticket priority and status values map to a custom Deal field since Nutshell Deals lack a native status pick-list. Your team configures which Comet Suite statuses map to which Nutshell pipeline stages during migration planning.

Individual line items or checklist steps within a Comet Suite job ticket translate to Nutshell Tasks. Each task is linked to the parent Deal that represents the ticket, preserving the original due date and assigned employee. This maintains the work-breakdown structure from the original ticket while fitting into Nutshell's activity model.

Comet Suite time punches do not map to a native Nutshell object. They are stored as Tasks on the related Deal with Type='Time Entry', a custom duration field, and a reference back to the original Comet Suite time entry ID for traceability. The original entry ID allows reconciliation if audit or billing questions arise post-migration.

GPS tracking data and route history from Comet Suite have no Nutshell equivalent and cannot be stored as structured fields. Route logs are exported as a CSV file and attached to the relevant Company record for historical reference. This preserves the data as a downloadable file without requiring custom field engineering beyond the standard migration scope.

Any custom fields on Comet Suite job tickets — such as service type, priority tier, skill requirements, or region — are created as Nutshell Deal custom fields before migration begins. FlitStack maps the field name, data type, and pick-list values value-by-value, ensuring the destination fields mirror the source schema as closely as the target platform allows.

Files attached to Comet Suite job tickets re-upload to Nutshell as Deal attachments. Large files are chunked and rehosted in Nutshell's file storage to respect size limits. Inline images embedded in Comet Suite notes are downloaded, processed, and re-attached as separate files to maintain the original visual context.

Comet Suite users are matched to Nutshell users by email address. Unmatched users are flagged before migration begins — your team either creates the Nutshell user account first or reassigns the records to a fallback owner designated during planning. This prevents orphaned records with no assigned owner in the destination system.