Migrate from Link app to Nutshell

Link app person records (name, email, phone, job title, address) map directly to Nutshell Person fields. Original create date preserved as a custom field since Nutshell's createdAt is set at migration time. Link app's client ID stored as a source reference field for delta-run deduplication.

Link app company records map to Nutshell Company. Fields include name, website, industry, address, and number of employees. Parent-child company relationships in Link app map to Nutshell's parent company field if the destination schema is pre-created. FlitStack validates each company name against Nutshell's duplicate-detection rules during ingestion to prevent duplicate company records from forming.

Link app messaging threads are not direct CRM activities — they represent a conversation log. FlitStack AI breaks each thread into individual Nutshell Activity records with Type (email or note), Subject (client name + thread topic), Body (message text), Owner (mapped via email match), and the original sent timestamp. Attachments on a thread become Nutshell file attachments on the corresponding Person or Company.

Link app file attachments (uploaded documents, signed forms, case files) re-upload to Nutshell as file attachments linked to the Person or Company record. File size limits from Nutshell's storage configuration apply. Inline images in messages are extracted and re-hosted as attachments.

Link app firm users are matched to Nutshell users by email address. Nutshell's JSON-RPC API supports impersonation mode — if the API key has impersonation enabled, FlitStack can log activity under the correct user rather than under a generic migration account. Unmatched users are flagged before migration so the team can create Nutshell accounts first.

Link app matters or cases (named thread groups) have no direct Nutshell equivalent because Nutshell Deals carry financial fields (Amount, Stage, Close Date) that Link app doesn't track. FlitStack creates a Nutshell Deal for each Link app matter using the matter name as Deal name, the most recent thread date as a custom close-date proxy, and zero or estimated amount — the team fills in actual deal value post-migration. A custom field Matter_ID__c stores the original Link app matter ID.

Link app uses tags and labels to segment clients (e.g., 'active matter', 'prospective client', 'archived'). These migrate as a custom multi-select or single-select field (Client_Segment__c) on Nutshell Person. Tag values are preserved verbatim; the Nutshell admin confirms field type during schema setup.

Link app workflow definitions (message routing rules, automated notifications, template triggers) are platform-specific and have no equivalent in Nutshell's automation model. FlitStack AI exports a written summary of every Link app workflow definition so the Nutshell admin can rebuild equivalent rules in Nutshell's sequence and automation tools after migration.

Link app integrations (calendar sync, e-signature, document management) are connection-level configurations that cannot be exported due to OAuth tokens and platform-specific authentication. Each integration must be re-connected manually in Nutshell — FlitStack provides a checklist of active Link app integrations to rebuild, including the integration type, connected service name, and the admin permissions needed to reauthorize in Nutshell.

Nutshell Activities record the createdAt timestamp as the import time, not the original message timestamp. FlitStack preserves the original sent date as a custom datetime field (Original_Activity_Date__c) on each Activity so reporting reflects the true interaction timeline from Link app.