Migrate from Mobile Service App to Nutshell

Direct 1:1 map. The Nutshell People object receives all standard person fields from the source platform, including name, email, phone, title, and address. Email serves as the primary key for de‑duplication across the migration run, and any duplicate email contacts are flagged for review. Owner assignments are resolved by email lookup; unmatched owners are noted before records are written to Nutshell.

Direct 1:1 map. Nutshell Companies hold business‑level records and receive source company name, phone, website, industry, employee count, and revenue fields. Address information maps to Nutshell’s address dictionary on the Company record. If the source platform supports parent‑company hierarchies, those relationships are preserved as a custom field in Nutshell, ensuring organizational structure continuity after migration.

Direct 1:1 map for leads that exist in the source system. The Nutshell Lead object accepts name, email, phone, status, source, and any custom fields. All status values are mapped value‑by‑value against Nutshell’s pick‑list options — New, Assigned, Working, Unqualified, Converted — so no manual status conversion is required after migration. Custom field data is transferred in the same way as standard fields, preserving all lead attributes.

Source work orders or tasks become Nutshell Deals. The task description maps to the Deal name, the source status or priority becomes a custom pick-list field on the Deal, and any assigned technician resolves by email to a Nutshell user (Owner). Original create and close dates are preserved as custom datetime fields.

Source custom fields that have no direct Nutshell equivalent are created as Nutshell custom fields on the relevant entity. We create the custom field in Nutshell first (Settings > Data > Custom Fields), then write values during the migration run. Field types (text, number, pick-list, date) are preserved from the source API metadata.

Notes and activity entries from the source system attach to the corresponding Nutshell People record. Original timestamps and activity type (call, email, note) are preserved. Nutshell Activity type field is set to match the source activity kind where a direct match exists.

Source file attachments are re‑uploaded to Nutshell and linked to the corresponding People or Deal record. Nutshell enforces a 25 MB per‑file limit; any files that exceed this threshold are flagged during the migration audit and excluded from the standard import. A separate file‑transfer plan — which may involve direct storage access or a chunked upload workflow — is documented before the migration run to ensure no data is lost.

Source users or owners are resolved by email address against Nutshell's user list. FlitStack AI flags any owner with no matching Nutshell user before migration commits — your team either invites the user to Nutshell first or assigns those records to a fallback owner during the run.

Source tags or labels that apply to contacts or companies are consolidated into a Nutshell custom text field. If tags are used as categorical data (e.g., service category), a custom pick-list field is created in Nutshell and tag values are mapped value-by-value.

Time entries or labor logs linked to source work orders are migrated as Nutshell Activities attached to the corresponding Deal. The activity subject field contains the duration or a short description of the time entry, while the original timestamp and owner are retained for reporting continuity. This preserves technician labor history in Nutshell, enabling managers to review service effort and cost metrics directly within the platform without needing external time‑tracking tools.