Migrate from Affinity Fieldreach to Zoho CRM

Affinity Persons with a valid email address and organization link become Zoho Leads first. If the person represents an active customer relationship in Affinity, they also create a Zoho Contact record linked to the corresponding Account. The decision rule applies based on whether the Affinity Person carries a customer-facing status in a List Item field — we surface this rule in the migration plan for your team to confirm before the full run.

Affinity Organizations map directly to Zoho Accounts using the Organization ID as a unique external identifier stored in a custom field (Source_System_ID__c equivalent in Zoho naming convention). Parent-child organization hierarchies in Affinity map to the Zoho Account Parent Account field. Multi-person organizations generate one Zoho Account with multiple linked Contact records.

Affinity List Items that categorize Persons or Organizations (e.g., role labels, status tags, tier classifications) map to Zoho custom pick-list fields on the Lead or Contact module. Each Affinity List Type generates one Zoho custom field; pick-list values are created to match the source values. Multi-select List Items in Affinity map to Zoho multi-select pick-list fields where supported, or stored as a comma-separated string in a text field as a fallback.

Affinity Notes that contain free-form text become Zoho Notes attached to the corresponding Lead, Contact, or Account record using the parent Person or Organization ID. Interaction logs tagged as email, call, or meeting activities map to Zoho Tasks with Type='Email', Type='Call', or Type='Meeting' respectively, preserving the original timestamp and owner attribution.

Affinity custom fields on the Person entity map to Zoho custom fields on the Lead or Contact module depending on where the Person lands. Zoho custom fields use an auto-generated API name derived from the field label. We create the Zoho custom field first, then populate it during the record migration. Data type mismatches (e.g., Affinity date stored as text) are flagged and corrected before the field is created.

Affinity custom fields on the Organization entity map to Zoho custom fields on the Account module. The same data-type reconciliation process applies — Zoho validates field values against the declared data type during import, so any Affinity values that don't conform require pre-processing before the migration run commits.

Affinity Person owners are resolved by email match against Zoho user records. Unmatched owners are flagged before migration — your team either creates a corresponding Zoho user first or assigns those records to a designated fallback owner. No record lands in Zoho without a valid owner assignment, ensuring your sales team sees their assigned accounts immediately after go-live.

Same owner-resolution logic as Person owners: email-based matching against Zoho users. If the Affinity Organization and its child Persons have different owners, the Account owner defaults to the Organization owner and the Contact owner reflects the Person owner — your admin confirms the desired hierarchy before the migration runs.

Affinity Work Orders and Jobs map to Zoho Tasks with the task subject set to the Work Order name, status mapped from the Affinity status string to a Zoho Task status value, and priority mapped via a value-mapping table. The linked Person or Organization ID is preserved as a lookup so the task attaches to the correct Zoho record.

Affinity Deals (if present in the source subscription tier) map to Zoho Deals using the Deal ID as an external identifier. Deal stage, amount, expected close date, and owner are mapped directly. Affinity Deal custom fields map to Zoho Deal custom fields using the same custom field creation and type-validation process described for Organization fields.