Migrate your Affinity Fieldreach data

Person records migrate cleanly with name, email, and primary identifiers. Global custom fields (multi-select, choice) require value mapping to the destination system. The n8n integration node only returns id, name, and primary_email natively; we retrieve full field payloads via direct API calls.

Organization (Entity) records migrate as standard objects with name, domain, and related custom fields. We preserve all associated Person-to-Organization relationships and any custom organization-level fields.

Deals carry owner assignment, stage, value, and close date as native fields. Custom fields on Deals map to equivalent custom fields in the destination. We maintain deal-to-organization and deal-to-person linkages.

Opportunities are similar to Deals but with their own lifecycle stages. We map Opportunity stage names and custom field configurations to the destination's equivalent deal or opportunity object, flagging any unsupported field types.

Lists are dynamic or static groupings of Persons or Organizations. We recreate list memberships in the destination as tags, segments, or static groups depending on the destination's model, and note whether the destination supports dynamic list logic.

Interaction records (calls, meetings, emails) capture relationship activity. Migration requires mapping to the destination's activity or engagement object. Note-taking and meeting summary content migrates as activity descriptions.

Global fields attached to multiple object types require careful field-type mapping. Multi-select and choice fields need explicit value translation. Choice type fields cannot have their type changed after creation in Affinity.

Custom fields scoped to Persons, Organizations, Deals, or Opportunities map individually. We retrieve field metadata via the API to determine type, required flag, and choice options before writing transformation logic.

Notes are standalone entities that can reference Persons or Organizations. We migrate note content and associations. Rich text formatting is preserved as HTML where the destination supports it.

Affinity supports multiple pipeline configurations per list or org. We map source pipeline stage names to the destination's pipeline stages, creating new stages where no equivalent exists.

Owner records map to users in the destination CRM. We handle inactive owner records by assigning orphaned deals/contacts to an active owner during migration.

Attachments associated with notes, deals, or organizations are downloaded and re-uploaded to the destination's document storage. We log attachment URLs and warn if file size exceeds destination limits.