Migrate from Affinity Fieldreach to Salesforce Sales Cloud

Affinity people map to Salesforce Contacts. Affinity stores the person's name, email, and organization affiliation in a unified record. In Salesforce, Contact requires an AccountId (lookup to Account). FlitStack AI creates the Account first from Affinity organization data, then links each Contact to the resolved AccountId — unresolvable organization affiliations surface as Account Contact Relations.

Affinity organizations map to Salesforce Accounts. Affinity stores company name, domain, industry, and employee count directly on the org record. Salesforce Account holds the equivalent fields: Name, Website, Industry, NumberOfEmployees. Parent-child org hierarchies in Affinity map to the Salesforce ParentId field on Account. Multi-org affiliations from Affinity people get surfaced as Account Contact Relations.

Affinity deals translate to Salesforce Opportunities. Affinity deal properties — name, amount, expected close date, stage — map to Opportunity Name, Amount, CloseDate, and StageName respectively. The StageName mapping requires value-by-value translation between Affinity stage names and Salesforce Opportunity Stage pick-list values per sales process.

Affinity lists are entity groupings (people, organizations, or both) that serve as deal context or segmentation buckets. They have no direct Salesforce equivalent. FlitStack AI maps each list to either a custom object (for many-to-many relationship tracking) or Account Contact Relations, depending on whether the list contains people, organizations, or both. Your Salesforce admin chooses the target model before migration runs.

Affinity List_Entry is the junction between a Person and a List. In Salesforce, person-list associations map to Account Contact Relations (for Account-person links) or a custom junction object (for other list types). The junction's custom fields capture any list-specific metadata from Affinity, such as entry date or list-provided notes.

Affinity engagement records — calls, emails, and meetings — map to Salesforce Task records with Type='Call' or Type='Email', and Event records for meetings. Original timestamps, owner (resolved by email), and parent-record links (to Contact and Account) are preserved in Salesforce. Task WhoId maps to the resolved Contact ID; Task WhatId maps to the resolved Account or Opportunity ID.

Affinity notes migrate to Salesforce Notes (the newer rich-text-enabled object, not the legacy Note). Content, author attribution, and timestamps are preserved. Rich-text formatting in Affinity notes is converted to Salesforce Notes rich-text format. If the original Affinity note was attached to a specific entity, the Salesforce Note links to the corresponding Contact or Account.

Affinity custom fields on people that have no Salesforce standard equivalent — relationship scores, enrichment data, multi-select tags — require custom fields on the Salesforce Contact object (suffix __c). FlitStack AI inventories every Affinity custom field before migration, maps the field type to the closest Salesforce type (multi-select to Text, number scores to Number), and creates the Salesforce custom fields as part of the pre-migration schema setup.

Affinity organization-level custom fields — industry-specific metrics, enrichment data, financial flags — require Salesforce custom fields on the Account object. Type translation follows the same logic as person-level custom fields. Fields with value pick-lists that don't exist in Salesforce's standard Industry pick-list are created as custom pick-lists on Account.

Affinity deal-level custom fields (beyond name, amount, stage, date) map to custom fields on Salesforce Opportunity. This includes deal priority flags, internal deal IDs, or deal-specific attributes. Custom Opportunity fields follow Salesforce naming conventions with the __c suffix and are created before the migration loads deal records.

Affinity owner references on entities resolve to Salesforce User IDs via email address matching. FlitStack AI cross-references Affinity owner email addresses against the Salesforce org's active User records. Unmatched owners are flagged before migration — the team either invites the user to Salesforce first or assigns their records to a designated fallback owner. No record lands without a valid OwnerId.

Affinity file attachments on people, organizations, or deals are downloaded and re-uploaded to Salesforce Files. Files are linked to the corresponding Salesforce record (Contact, Account, or Opportunity) via ContentDocumentLink. Salesforce's 25MB per-file size limit applies — files exceeding this are flagged for manual handling or chunked upload.