Migrate from FieldAware by GPS Insight to Microsoft Dynamics 365 Sales

FieldAware jobs carry customer, location, technician, asset, and line-item context. These map as Cases with the AccountId lookup pointing to the migrated Customer. Original job status (Pending, In Progress, Completed, On Hold) maps to Case Status (Active, Resolved, Cancelled, On Hold) via value-mapping.

FieldAware Customer is the top-level entity holding name, billing address, and contact list. Maps 1:1 to Dynamics Account. The Customer ID is preserved as a custom field (Source_Customer_ID__c) for traceability and delta-run de-duplication and enables cross-reference reporting across source and target systems.

FieldAware Contacts (per Customer) map to Dynamics Contacts. Each contact gets its AccountId lookup populated from the migrated Customer-Account pair. Multiple contacts per customer collapse to individual Contact records linked by AccountId ensuring that service locations and billing contacts are correctly associated in the target CRM.

FieldAware Locations hold service-site address, contact name, and site-specific notes. Dynamics Accounts store a primary address composite (address1_line1, city, state, postalcode, country). Multiple locations per Customer map to additional address lines or a custom Address table — your admin chooses before migration.

FieldAware Assets (serial number, make, model, warranty end date, linked customer) have no native Dynamics 365 Sales equivalent. We create a custom Asset table (new_asset) with AccountId and ContactId lookups and preserve the full asset record including service history dates as custom fields.

When a FieldAware Job references an Asset, the Case in Dynamics holds a lookup to the custom Asset table (new_assetid). This preserves the equipment context on each service Case so technicians see the asset history before a visit and supports future service scheduling decisions.

FieldAware Quotes (line items, pricing, customer reference) sent to customers map as Dynamics Opportunities. Quote status (Draft, Sent, Accepted, Declined) maps to Opportunity Stage values via value-mapping. Accepted quotes may also generate a Dynamics Quote record for the full sales-order chain.

FieldAware Quote line items (item reference, quantity, unit price, discount) map to Dynamics Opportunity Product records. The Product lookup resolves against the migrated Items catalog. Discount handling uses the manual discount field on Opportunity Product and maintains pricing accuracy across the sales pipeline.

FieldAware Invoices (invoice number, date, total amount, status) map to Dynamics Invoice records. Line items resolve as Invoice Product records linked to the Invoice. Original invoice number preserved in the Invoice Number field for billing reference and ensures audit trail continuity during transition.

FieldAware Items and parts (name, part number, description, unit price) map to Dynamics Products. The part number maps to the Product Number field. Products are activated in the catalog before job and quote migrations run so lookups resolve correctly for downstream reporting.

FieldAware Users and assigned Technicians are resolved by email match against Dynamics SystemUser records. Technicians who are not Dynamics licensed users land as Contacts with a custom field (Technician_in_Source__c) set to true for reference and can be upgraded to full users later as needed.

FieldAware Tasks linked to jobs map as Dynamics Tasks with the regardingobjectid pointing to the Case. Original task description, due date, and owner are preserved. Completed task status maps directly and includes a flag for tasks requiring client approval before closure.

FieldAware custom fields declared per entity are migrated as Dataverse custom columns with the new_ prefix. Dropdown-type custom fields require explicit value-mapping against the Dynamics picklist options. CheckBox fields map to the TwoOption (boolean) type and each mapping is validated before final load.

FieldAware customer signature capture on completed jobs has no native Dynamics equivalent. We preserve the signature image as a Note attachment on the Case record, linked via RegardingId to the migrated Case ensuring that sign-off proof remains attached for compliance audits.