Migrate from Fieldproxy to Microsoft Dynamics 365 Sales

Fieldproxy customers who are businesses or organizations map directly to Dynamics 365 Accounts. Company name maps to Account Name. Primary address maps to the Account's address fields. We flag multi-site customers so each service location can become either a separate Account or a Child Account via Parent Account relationship.

Individual customers in Fieldproxy without a company association map to Dynamics 365 Contacts. We preserve the email, phone, and any site-specific notes. If the individual is tied to an Account (the organization is also a customer), we link the Contact to the Account via the AccountId lookup in Dynamics.

Fieldproxy jobs become Dynamics 365 Opportunities. The job name maps to Opportunity Name. Job amount or quoted price maps to Estimated Revenue. Job status (Scheduled, In Progress, Completed) maps to a custom Opportunity Status field since Dynamics 365 stages differ from job lifecycle states. Technician assignments and job type become custom fields on the Opportunity.

For organizations needing full job history preservation, we create a custom JobHistory Dataverse table linked to the Account or Contact. Each migrated job becomes a record in this table with fields for job date, technician, location, service type, and outcome. This captures Fieldproxy's operational history without overloading the native Opportunity object.

Fieldproxy locations associated with a customer become additional address records on the corresponding Dynamics 365 Account. Multi-location customers with separate billing and service addresses get separate address type records (Bill To, Ship To, Service Location). We preserve the location name as an address label.

Fieldproxy technicians who also interact with customers (as sales contacts or account managers) map to Dynamics 365 Contacts. Technicians who only perform field service and do not need CRM access become Contacts with a custom Technician_Flag__c field. If the technician also needs Dynamics 365 login, they are provisioned as a System User; we map their email for owner lookup during migration.

Fieldproxy equipment records map to a custom EquipmentAsset Dataverse table linked to the Account. The equipment name, model, serial number, and installation date become fields on this custom entity. Maintenance history from Fieldproxy becomes a related Activity log or a custom Audit__c field on the equipment record.

Fieldproxy quotes with status 'Sent' or 'Accepted' map to Dynamics 365 Quotes. Accepted quotes map to Sales Orders. Line items map to Opportunity Products. We preserve the quote total, currency, and validity date. Quotes in Draft status are optionally migrated or provided as a data export for manual re-creation in Dynamics.

Fieldproxy activity records (visit notes, status updates, customer communications) map to Dynamics 365 Tasks. Phone call records migrate as Phone Call activities. On-site visit completions migrate as Appointments with the original start/end timestamps preserved. Each activity links to the parent Account, Contact, or Opportunity via the regarding lookup.

Fieldproxy custom objects and their fields map to corresponding custom Dataverse tables and columns. We create the custom table in Dynamics 365, map each custom field by data type (text, number, date, pick-list), and preserve any relationships between custom objects and standard objects (Customer, Job) via Dataverse lookups.

Fieldproxy file attachments on jobs, customers, or equipment are downloaded and re-hosted. We attach them to the corresponding Dynamics 365 record as Notes with file attachments, or push them to the Account's SharePoint document library if the organization has SharePoint integration enabled. Original filenames and upload dates are preserved.

Fieldproxy workflows and AI-dispatch configurations do not have a direct equivalent in Dynamics 365 Sales. We export all workflow definitions (trigger conditions, actions, branching logic) as a structured JSON document that your admin can use as a reference when rebuilding equivalent automations in Power Automate or Dynamics 365 business rules.