Migrate from FieldPro to Microsoft Dynamics 365 Sales

FieldPro users map to Dynamics 365 SystemUser records. We match on email address — if a FieldPro user email matches an existing D365 user, the record inherits that OwnerId. Unmatched FieldPro users are flagged before migration; your admin either invites them to D365 first or assigns them to a fallback user who inherits their records.

FieldPro outlets (retail locations, distributor endpoints) map directly to Dynamics 365 Account records. We map the outlet name to Account.Name, the registered address fields to Address1 components, and store the original FieldPro outlet ID in a custom Source_Outlet_ID__c field for traceability. GPS coordinates from FieldPro (latitude/longitude) become custom decimal fields on the Account.

FieldPro contact records on outlets map to Dynamics 365 Contact. Email, phone, mobile phone, job title, and address fields migrate directly. We resolve the primary account link by matching the outlet name — if the outlet already landed as an Account, the contact gets that AccountId lookup populated. Contacts without an email receive a generated placeholder email and are flagged for review.

If FieldPro tracks outlet pre-qualification or prospect visits before a location is confirmed, those records map to Dynamics 365 Lead. Lead fields (firstname, lastname, email, company, phone) migrate directly. We preserve the original FieldPro createdate as Original_Create_Date__c since D365's CreatedOn is set at migration time.

FieldPro visit records have no native D365 equivalent — the structured visit data (checklist responses, visit outcome, products observed, visit duration) maps to a new_ FieldProVisit custom table in Dataverse. The visit summary (date, outlet, agent, outcome) also creates a Task record on the related Account for timeline visibility. The custom table stores the full visit payload as JSON in a custom Long Text field for audit reference.

FieldPro route definitions and individual route legs (ordered stops with arrival times) map to a new_ FieldProRoute custom table. Each route leg links to the related Outlet (Account) via a lookup field. Route optimization scores from FieldPro AI migrate as custom Number fields. Planned vs. actual arrival times are preserved as separate datetime fields for route-efficiency reporting in Power BI.

FieldPro Direct orders placed by retailers map to Dynamics 365 SalesOrder and OrderProduct records. Order number, order date, total amount, and status migrate directly. Line items map to OrderProduct with product name, quantity, and unit price. If FieldPro products use a different SKU schema than D365, we apply a value-map lookup or create placeholder products flagged for D365 admin reconciliation.

FieldPro product catalog entries (name, SKU, description, unit price, category) map to Dynamics 365 Product records. Product type (stocked vs. non-stocked) is preserved as a custom field. If FieldPro organizes products into hierarchies that don't match D365's unit-group model, we map the top-level category to Product.Products [Default Business Unit] and surface sub-category as a custom field.

Any FieldPro custom objects — common in distribution and agri-sourcing deployments where teams define bespoke data capture forms — map to new_ prefixed Dataverse tables. We create the custom table schema in D365, define the lookup relationships to Account or Contact, and migrate the records. N:N associations between custom objects map via Dataverse many-to-many relationship entities.

FieldPro blob attachments (visit photos, signed forms, compliance documents) are downloaded from FieldPro storage and re-uploaded to SharePoint Online linked to the relevant Account or Contact record. We create Document Location records in D365 pointing to the SharePoint folder so the files appear in the CRM timeline. If your D365 environment uses Notes attachments instead of SharePoint, we fall back to Note with file attachment (25MB limit enforced per file).

FieldPro workflows — route-triggered notifications, visit-completion alerts, auto-assignment rules — have no direct equivalent in Dynamics 365 and do not migrate automatically. We export FieldPro workflow definitions as a reference JSON document your D365 admin can use to rebuild equivalent Power Automate flows. The export covers trigger conditions, action steps, and field references.

FieldPro's pre-built ERP connectors (Business Central, NetSuite, Sage CRM, SYSPRO) are platform-specific and cannot transfer to Dynamics 365. We document the current integration endpoints, field mappings, and sync frequency so your integration team can rebuild using the D365 Dataverse connector or Azure Logic Apps. If you use FieldPro Direct for B2B ordering, we provide a data model guide for mapping that flow to D365 Sales Order processing.