Migrate from FieldAware by GPS Insight to Zoho CRM

FieldAware Customers map 1:1 to Zoho Accounts. Account Name, phone, website, and industry fields migrate directly. Multi-location customers: the primary location address populates the Account's address fields; secondary locations migrate as custom address fields or a custom Locations subform on the Account module. FieldAware Customer IDs are preserved as Source_System_ID__c on each Account for delta-run deduplication.

FieldAware's Location object (address, lat/long coordinates, location name per customer) has no direct Zoho equivalent. We map the primary location address to Account address fields. Secondary locations become a custom Locations subform or individual address lines stored as custom text fields. Lat/long coordinates are stored as custom Number fields on the Account since Zoho does not have a native geolocation field type.

FieldAware Contacts map to Zoho Contacts with direct field mapping on first name, last name, email, phone, job title, and mobile. Contacts are linked to their parent Account via Account Name matching. FieldAware Contact IDs are preserved as Source_System_ID__c for traceability. Multiple contacts per customer (FieldAware allows N:1) all migrate; Zoho Contact roles are assigned based on the contact's role field in FieldAware.

FieldAware Jobs are the core field service record and map to Zoho Cases in the Cases module. Job Subject becomes Case Subject; Job description maps to Case Description; Job status (Scheduled, In Progress, Completed, Cancelled) maps via value_mapping to Zoho Case Status values (New, In Progress, Closed — you configure the pick-list). Job scheduled start/end dates map to custom Date fields on the Case since Zoho Cases have no native scheduling window field. Technician assignment resolves by email match to Zoho Users and populates Case Owner.

Active jobs with a future scheduled date that are still in progress at migration time split into two records: the Case captures the work order context and history, and a Zoho Task with the scheduled date and assigned technician captures the dispatch-level scheduling. Completed jobs migrate as Cases only with status set to Closed. Cancelled jobs migrate as Closed Cases with a custom Cancelled_Reason__c field populated from FieldAware cancellation notes.

FieldAware Assets (serial number, manufacturer, model, customer association, service history) have no native equivalent in Zoho CRM. We recommend pre-creating a custom Assets module (available on Enterprise and Ultimate plans) before migration. Asset fields map to custom fields on the Assets module: Asset_Serial_Number__c, Manufacturer__c, Model__c, Service_History__c (long text), and Customer__c (lookup to Account). Each Asset is linked to its parent Account record.

FieldAware Quotes map to Zoho Quotes with Quote Subject, Quote Date, and status mapping directly. Line items (Items, quantity, unit price) map to Zoho Quote Line Items referencing Zoho Products. Quote total and tax amounts map to Zoho Quote fields. Quotes in Draft status remain Draft; Approved quotes map to Open. We map FieldAware Quote IDs to Source_System_ID__c on the Quote for reconciliation.

FieldAware Invoices map to Zoho Invoices with Invoice Subject, Invoice Date, and status mapping directly. Invoice line items map to Zoho Invoice Line Items referencing Products. Amount, tax, and payment status migrate as-is. Paid invoices keep their Paid status in Zoho; outstanding invoices migrate with their balance amount. FieldAware Invoice IDs are preserved as Source_System_ID__c on each Invoice.

FieldAware Items (part number, name, description, unit price) map to Zoho Products. Product Name, Part Number, Unit Price, and Description migrate directly. Items flagged as products vs. services in FieldAware can be tagged with a Product Type custom field in Zoho to preserve that distinction for pricing and reporting purposes.

FieldAware Users are resolved by email match against Zoho Users. Matched users become the Owner on migrated records (Cases, Contacts, Accounts). Unmatched users — technicians who do not yet have Zoho accounts — are flagged during the pre-flight report; you either create their Zoho users before migration or assign their records to a fallback owner. Admin-level FieldAware users map to Zoho Admin roles.

FieldAware custom fields declared on Jobs, Customers, Contacts, and Assets (types: Text, Number, CheckBox, Dropdown, Date, Time) migrate as Zoho custom fields. Dropdown custom fields require value-by-value pick-list mapping in Zoho before import. CheckBox fields convert to Zoho's Checkbox data type. Date and Time fields migrate as Zoho DateTime fields. We pre-create all custom field declarations via Zoho's Settings API before the migration run.

FieldAware file attachments on Jobs and Invoices (photos, signatures, PDFs) re-upload as Zoho Attachments linked to the corresponding Case or Invoice record. Zoho's attachment limit is 25MB per file for most editions; files exceeding this are flagged for manual review or chunked upload. Inline images in FieldAware notes are downloaded and rehosted as Zoho Attachments.