Migrate from CINC to Nutshell

CINC Leads map 1:1 to Nutshell Leads. All standard lead fields (name, email, phone, source, status) transfer directly. Owner resolution runs against Nutshell user emails before migration commits. Unresolved owners attach to a fallback Nutshell user or are flagged for manual assignment before the full run.

CINC Contacts map to Nutshell People — the primary person record object. Primary company association transfers as a lookup to the corresponding Nutshell Company record. Multi-company contacts in CINC collapse to one primary company link in Nutshell with additional company relationships surfaced as secondary links if the Nutshell configuration supports it.

CINC Companies map directly to Nutshell Companies. Parent-child company hierarchies in CINC map to Nutshell's parent-company field. Company type, industry, and address fields transfer as-is where field names align. Nutshell Company does not support custom fields in all tiers — this is surfaced in the pre-migration schema plan.

CINC Deals map to Nutshell Deals (the opportunity-equivalent). CINC pipeline stages map to Nutshell Deal stages by value. CINC deal amounts, close dates, and owners transfer directly. Note that Nutshell Deals do not support custom fields — any CINC deal-level custom properties must be moved to custom fields on the linked Person or Company record, which is documented in the migration plan before data lands.

CINC engagement records map to Nutshell's activity objects: calls and emails become Tasks, meetings become Events, and free-text notes become Nutshell Notes. Original timestamps, owner email matches, and parent-record links (Person, Company, or Deal) are preserved across all activity types.

CINC custom property definitions are exported as a structured field catalog. Each custom field is reviewed against Nutshell's supported types (text, number, date, picklist, checkbox, currency, URL). Nutshell custom fields on People, Companies, and Leads are created in the destination account before migration. Deal-level custom fields in CINC require re-parenting to Person or Company records — this is explicitly flagged and requires a decision from the customer's admin.

CINC tracks lead source (MLS, website, referral, etc.) as a standard or custom field depending on the CINC configuration. This maps to a Nutshell custom pick-list field (Lead_Source__c) on both Lead and Person records for attribution continuity. Original source attribution timestamps also transfer as a date field if present in CINC.

CINC document attachments (images, PDFs, uploaded files) on Contacts, Companies, and Deals are downloaded and re-uploaded to the corresponding Nutshell record. File size limits and inline image handling follow Nutshell's storage conventions. All original file names and upload timestamps are preserved in Nutshell's file metadata.

CINC owner IDs are resolved by email match against Nutshell user accounts. Nutshell's API supports impersonation for write operations when the API key permits it, allowing FlitStack to attribute records to the correct Nutshell user. Owners without a matching Nutshell account are flagged pre-migration so the team can create accounts or assign a fallback owner before the run.

CINC's Speed-to-Lead auto-tracking, behavioral messaging sequences, and custom workflow rules have no equivalent in Nutshell's object model. FlitStack exports a configuration reference document detailing each CINC workflow's trigger conditions and action sequence so the customer's Nutshell admin can rebuild equivalent automations using Nutshell's Sales Email sequences and task triggers.