Migrate from Affinity Fieldreach to Nutshell

Affinity Person maps 1:1 to Nutshell Contact (internally called 'People' in the UI, 'Contact' in the API). FlitStack preserves the Person's original create date as a custom datetime field since Nutshell's createdate is set at migration time. All standard Person fields (name, email, phone, title, address) map directly.

Affinity Organization maps 1:1 to Nutshell Account (called 'Company' in the Nutshell UI, 'Account' in the API). Organization name, domain/website, industry, and employee count fields map directly. Nutshell's Account API field name is 'name' for company name — FlitStack resolves this during the field mapping phase. Parent-child organization hierarchies in Affinity map to Nutshell's parent Account field if configured.

Affinity Opportunity maps to Nutshell Lead, not to a deal or opportunity object — Nutshell does not have a separate Opportunity object at the CRM level. Deal amount, expected close date, and deal name migrate as Lead custom fields in Nutshell. Affinity's opportunity stage values are mapped to Nutshell's Milestone (stage) values; if multiple Affinity pipelines exist, FlitStack maps them to a single Nutshell pipeline with stage filtering handled via a Pipeline custom field on the Lead record.

Affinity global custom fields at the Person level migrate to Nutshell Contact custom fields. FlitStack creates the Nutshell custom field using the same field type (text, number, date, picklist) inferred from the Affinity field definition. Multi-select picklist fields in Affinity become Nutshell multi-value custom fields where supported, or comma-separated text as a fallback.

Affinity Organization custom fields map to Nutshell Account custom fields. The same type-inference logic applies: text to text, number to number, date to date, picklist to picklist. Nutshell's custom field creation API requires the field key name — FlitStack generates a URL-safe key from the Affinity field label (e.g., 'Customer Tier' becomes 'customer_tier').

Affinity Opportunity custom fields map to Nutshell Lead custom fields. Because Nutshell Lead is the target for all opportunity data, opportunity-level custom fields are appended to the Lead record alongside the transformed deal amount and close date fields. FlitStack surfaces the full list of Affinity opportunity custom fields in the pre-migration mapping plan.

Affinity Interactions (calls, emails, meetings logged against a Person or Organization) map to Nutshell Activities. Each Interaction type (call, email, meeting) maps to the corresponding Nutshell Activity type. Original timestamps and owner assignment are preserved. Affinity Interaction notes content migrates as the Activity description field in Nutshell.

Affinity Notes attached to Persons, Organizations, or Opportunities map to Nutshell Notes. The note body, create date, and owning user are preserved. Nutshell Notes are linked to a parent entity (Contact, Account, or Lead) via the standard Nutshell note association model.

Affinity List entries (static lists of Persons or Organizations) map to Nutshell Tags. Each List name becomes a Tag name in Nutshell. If an Affinity List is dynamic (auto-populated by filter rules), FlitStack exports the list definition as a JSON specification so your Nutshell admin can recreate equivalent filtered views or static tag groups in Nutshell.

Affinity relationship_strength scores are unique to Affinity's deal-sourcing model and have no Nutshell equivalent. FlitStack migrates the relationship_strength numeric value as a read-only custom field (Relationship_Strength__c) on the Nutshell Contact record for historical reference. This field is not actively used in Nutshell workflows but preserves the data for audit purposes.

Affinity Entity Files attached to Persons, Organizations, or Opportunities are re-uploaded to Nutshell as file attachments on the corresponding Contact, Account, or Lead record. Nutshell stores attachments inline with the record. File size limits in Nutshell apply — files exceeding 25MB are flagged in the migration report for manual handling.

Affinity Fieldreach automations and webhooks do not have a direct Nutshell equivalent. FlitStack exports the automation definition as a structured JSON file including trigger conditions, action steps, and field references. Your Nutshell admin uses this export as a rebuild specification for Nutshell's built-in automation tools (sequences and workflow rules). The data migration does not include automation logic by design.