CRM migration
Field-level mapping, validation, and rollback between FRONTU and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
FRONTU
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
10 of 12
objects map 1:1 between FRONTU and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Frontu organizes field service operations around Tasks, Work Orders, Employees, Locations, and Assets. Dynamics 365 Sales (built on Microsoft Dataverse) organizes customer relationships around Accounts, Contacts, Leads, and Opportunities. These data models share very little structural overlap, which makes this migration a careful translation problem rather than a simple export-import. FlitStack AI maps Frontu companies to Dynamics 365 Accounts, employees to Contacts with user-role resolution, and completed or in-progress work orders to Opportunities with original stage names preserved. Assets migrate as Products or as a custom entity depending on the Dynamics edition in use. Task history, notes, and completed activities surface as Dynamics 365 Notes and Activities with original timestamps and owner links. We do not migrate Frontu's scheduling engine, dispatch rules, or route-optimization logic — those are destination-side configurations that must be rebuilt in Dynamics 365 Field Service or Power Automate. Frontu's real-time dispatch model has no native equivalent in Dynamics 365 Sales without the Field Service add-on. We use Frontu's REST API for data extraction, transform records to match Dynamics 365 field types and entity relationships, then upsert via the Dynamics 365 Web API (Dataverse). Owner resolution happens by email match against Dynamics 365 users before records are written, so no Opportunity lands without a valid OwnerId. A delta-pickup window (24–48 hours) captures any work orders modified in Frontu during the cutover window.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
FRONTU platform overview
Scorecard, SWOT, gotchas, and pricing for FRONTU.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a FRONTU object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
FRONTU
Company
Microsoft Dynamics 365 Sales
Account
1:1Frontu company records map directly to Dynamics 365 Accounts. Account name, address, phone, and website fields translate field-for-field. Multi-location Frontu companies with branch addresses may require multiple Account records with a ParentId link in Dynamics. Each Account can represent a top-level organization or a branch office, depending on the address hierarchy from Frontu. This ensures that contacts and service history remain tied to the correct legal entity.
FRONTU
Employee
Microsoft Dynamics 365 Sales
Contact + SystemUser
1:1Frontu employee records split into two targets: the personal contact data (name, email, phone, role) becomes a Dynamics 365 Contact on the relevant Account, while the employee email is resolved against Dynamics 365 SystemUser records for OwnerId assignment on migrated Opportunities and Tasks.
FRONTU
Location
Microsoft Dynamics 365 Sales
Account (Shipping Address) / Contact (Address)
many:1Frontu service locations attached to a Company merge into the Account's address fields. When multiple service locations exist per Company, each location becomes a separate Account record linked via ParentId, preserving the location-specific address hierarchy that Frontu modeled. This approach ensures that field service visits are routed to the correct site and that each location maintains its own contact history and service records in Dynamics.
FRONTU
Work Order
Microsoft Dynamics 365 Sales
Opportunity
1:1Frontu work orders map to Dynamics 365 Opportunities with the original work order name as Opportunity Name, original status translated to an Opportunity Stage value, and estimated or actual service value mapped to Amount. CloseDate reflects the work order completion or target date.
FRONTU
Work Order Status
Microsoft Dynamics 365 Sales
Opportunity StageName
1:1Frontu status values (e.g., Pending, In Progress, Completed, Cancelled) map to Dynamics 365 Opportunity Stage values. Active statuses map to open pipeline stages; Completed maps to Closed Won; Cancelled maps to Closed Lost. Stage probabilities are applied per the Dynamics default or your configured Sales Process.
FRONTU
Asset
Microsoft Dynamics 365 Sales
Product
1:1Frontu assets with serial numbers, equipment type, and service history map to Dynamics 365 Products. Product Name reflects the asset description, Product ID reflects the serial number, and the original asset status is preserved as a custom field on the Product record for service-contract tracking.
FRONTU
Task / Activity
Microsoft Dynamics 365 Sales
Task / Activity (Email, Phone Call, Appointment)
1:1Frontu service task history, completed checklists, and notes migrate as Dynamics 365 Activities. Completed task descriptions become Note records with the original timestamp and the assigned Employee resolved to a Contact owner. Phone-call or email activities map to the corresponding Dynamics activity type.
FRONTU
Custom Field (Work Order)
Microsoft Dynamics 365 Sales
Custom Field on Opportunity
1:1Frontu custom fields on Work Orders (e.g., service-type codes, priority flags, parts used) require custom fields on the Dynamics 365 Opportunity entity. We create new_* prefixed custom fields in Dynamics and migrate the values directly. Field data type is preserved — text stays text, pick-list stays option set.
FRONTU
Custom Field (Asset)
Microsoft Dynamics 365 Sales
Custom Field on Product
1:1Frontu asset-level custom properties (e.g., warranty expiration, installation date, maintenance interval) migrate as custom fields on the Dynamics 365 Product record. These support service-contract and warranty tracking scenarios in Dynamics 365 Sales after migration. By preserving these details, service teams can quickly reference warranty status, schedule preventive maintenance, and generate renewal reports directly within the CRM.
FRONTU
Scheduling / Dispatch Rule
Microsoft Dynamics 365 Sales
Power Automate Flow / Dynamics 365 Field Service Bookable Resource
1:1Frontu's scheduling engine, route-optimization rules, and dispatch configurations do not migrate. These must be rebuilt in Dynamics 365 Field Service (Bookable Resources, Work Orders, and Resource Scheduling Optimization) or in Power Automate. We export the Frontu scheduling configuration as a reference document for your Dynamics admin.
FRONTU
Attachment / File (Work Order)
Microsoft Dynamics 365 Sales
Note (with file attachment)
1:1Files attached to Frontu work orders (e.g., photos, PDFs, inspection reports) migrate as Dynamics 365 Notes with file attachments. File size limits of 5 MB per attachment in Dataverse apply — files exceeding this limit are flagged for manual handling or chunked upload.
FRONTU
Customer (linked to Company)
Microsoft Dynamics 365 Sales
Contact (primary on Account)
many:1Frontu customer records attached to a Company are merged into the primary Contact record on the mapped Account. Additional customer contacts attached to the same Company become secondary Account Contact Relationships in Dynamics 365, preserving the multi-contact view per account.
| FRONTU | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Company | Account1:1 | Fully supported | |
| Employee | Contact + SystemUser1:1 | Fully supported | |
| Location | Account (Shipping Address) / Contact (Address)many:1 | Fully supported | |
| Work Order | Opportunity1:1 | Fully supported | |
| Work Order Status | Opportunity StageName1:1 | Fully supported | |
| Asset | Product1:1 | Fully supported | |
| Task / Activity | Task / Activity (Email, Phone Call, Appointment)1:1 | Fully supported | |
| Custom Field (Work Order) | Custom Field on Opportunity1:1 | Fully supported | |
| Custom Field (Asset) | Custom Field on Product1:1 | Fully supported | |
| Scheduling / Dispatch Rule | Power Automate Flow / Dynamics 365 Field Service Bookable Resource1:1 | Fully supported | |
| Attachment / File (Work Order) | Note (with file attachment)1:1 | Fully supported | |
| Customer (linked to Company) | Contact (primary on Account)many:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
FRONTU gotchas
No publicly documented public API for bulk data export
Custom fields are per-organization with no standard schema
Tasker legacy data from pre-2021 may use different object names
Billing and invoicing data may exist outside Frontu
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Extract Frontu data via REST API
FlitStack AI connects to Frontu's API using scoped read access to extract all Companies, Employees, Locations, Work Orders, Assets, Tasks, and custom field definitions. We pull the full schema including custom field names, pick-list values, and relationship links between work orders and assets. API rate limits are respected with exponential back-off. The extraction runs in parallel with the Dynamics 365 schema review so both sides are ready for mapping simultaneously.
Design the Dynamics 365 schema and value-mapping table
Before any data moves, we deliver a schema setup plan: which custom fields need to be created on Opportunity and Product, which Frontu status values map to which StageName options, whether the asset model fits under Product or requires a custom entity, and whether the record count and custom field count are within the Sales Professional license cap. Your Dynamics admin creates the custom fields and confirms the value-mapping table; we validate the schema before migration begins.
Resolve owners and provision Dynamics 365 Users
We match every Frontu employee email against existing Dynamics 365 SystemUser records. Matched employees get their records assigned to their Dynamics User as OwnerId. Unmatched employees are flagged in a pre-migration report with instructions: either invite them to Dynamics 365 before migration or designate a fallback owner. No Opportunity is written without a valid OwnerId — this prevents the orphaned-record problem that plagues manual CRM migrations.
Run sample migration with field-level diff
A representative slice — typically 100–300 records covering Companies, Employees, Work Orders, Assets, and a mix of task types — migrates first to a staging Dynamics 365 environment. We generate a field-level diff report showing every source value mapped to its destination field, including custom field values and resolved OwnerIds. You review the diff, confirm the stage-mapping table, and approve the full run. This step prevents bulk data from landing in the wrong stage or with missing owners.
Execute full migration with delta-pickup and audit log
The full extraction-and-load run moves all Frontu records into Dynamics 365. A delta-pickup window of 24–48 hours after the main run captures any Frontu records modified during cutover. FlitStack AI maintains a full audit log of every record created, updated, or skipped with reason codes. If reconciliation reveals missing records or incorrect stage mapping, one-click rollback reverts the Dynamics environment to its pre-migration state while your team continues working in Frontu.
Deliver scheduling reference doc and rebuild guide
Frontu's dispatch rules, route-optimization configurations, and service-type definitions are exported as a structured reference document. This doc helps your Dynamics admin or implementation partner rebuild the scheduling layer in Dynamics 365 Field Service or Power Automate. We do not migrate workflows or automations, but we give your team a clear blueprint for recreating Frontu's scheduling logic in the destination platform's native tools.
Platform deep dives
FRONTU
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across FRONTU and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
FRONTU: Not publicly documented.
Data volume sensitivity
FRONTU doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during FRONTU to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your FRONTU to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave FRONTU
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.