Migrate from Affinity Fieldreach to HighLevel

Affinity Fieldreach contact records migrate as HighLevel contacts with a direct field-level map for all standard properties. Email serves as the primary unique identifier for deduplication during migration. Owner resolution uses email matching against HighLevel users. Fieldreach contacts without an email receive a generated placeholder address flagged for manual review post-migration.

Affinity Fieldreach company records migrate as HighLevel companies. Company name, domain, industry, employee count, and annual revenue map directly. Fieldreach company-to-contact associations (one contact can be linked to multiple companies) map to HighLevel's primary-company association; secondary associations are preserved as custom fields for reference post-migration.

Affinity Fieldreach work orders do not have a native HighLevel equivalent and must be modeled as Opportunities. The work order name becomes the Opportunity name, the total amount maps to the Opportunity value, and the service address maps to a custom address field. Work order status is preserved as a custom pick-list field on the Opportunity, with value mapping to align Fieldreach status labels with HighLevel pipeline stage names.

Fieldreach work orders contain line items for parts and labor that do not exist as separate objects in HighLevel's standard Opportunity model. FlitStack AI creates a custom object in HighLevel called Work Order Line Items with fields for item description, quantity, unit price, and total. The custom object is linked to the parent Opportunity via a lookup relationship so the full service cost breakdown is accessible from the Opportunity record.

Affinity Fieldreach assets (equipment, meters, infrastructure components with location and condition data) migrate as a HighLevel custom object named Assets. Asset name, type, location, and condition status map to custom fields on the object. Maintenance history from Fieldreach is preserved as a text area field on the Asset custom object since HighLevel has no native maintenance log structure.

Fieldreach service history records are embedded within the work order and include all status transitions, technician notes, and timestamps. Because HighLevel has no native service history object, FlitStack AI appends a service history summary as a custom text area field on the Opportunity record and attaches individual history entries as HighLevel Notes linked to the Opportunity, preserving the full chronological service record.

Affinity Fieldreach user and owner records are resolved by email matching against HighLevel users. A pre-flight check runs before migration to identify unmatched owners. Teams either invite those users to HighLevel first or assign their records to a designated fallback owner. No record lands in HighLevel without a valid owner resolved via email match.

Affinity Fieldreach notes attached to work orders or contacts migrate as HighLevel notes linked to the corresponding Opportunity or Contact. Original create timestamps are preserved as a custom datetime field on each note since HighLevel's native createdAt timestamp reflects the import date, not the original note creation date.

Fieldreach file attachments on work orders and contacts are downloaded and re-uploaded to HighLevel's file storage. Large file attachments (exceeding HighLevel's file size limits) are flagged during the pre-flight audit and documented for manual re-upload post-migration. All file names and original upload timestamps are preserved as metadata in HighLevel.

Affinity Fieldreach custom fields on any object are created as custom fields in HighLevel on the corresponding object before migration begins. Fieldreach field types (pick-list, text, number, date) map to their HighLevel equivalents. Pick-list fields require explicit value mapping when the source and destination pick-list values differ. This step ensures the schema is ready before any record data is written.

Affinity Fieldreach workflows and automations tied to work-order status changes, assignment rules, or scheduling logic do not have a direct HighLevel equivalent. FlitStack AI does not migrate automation logic. We export a structured definition of each Fieldreach workflow (trigger events, conditions, and actions) as a JSON reference document that your HighLevel admin can use to rebuild equivalent automations in HighLevel's Workflows builder.

Affinity Fieldreach tags and labels applied to contacts, companies, or work orders migrate as HighLevel tags. Tags are preserved exactly as they appear in Fieldreach so segmentation, filtering, and automation triggers in HighLevel can reference the same tag vocabulary post-migration.

Affinity Fieldreach integrations with ERP systems, payment processors, or third-party field tools do not migrate. Each integration must be evaluated individually: HighLevel's native integrations cover Stripe, QuickBooks, Google Calendar, and Zapier, among others. We document every active Fieldreach integration and provide a rebuild plan referencing HighLevel's available connectors and API endpoints.