Bella FSM to Dynamics 365 migration
Moving from Bella FSM to Dynamics 365 Sales consolidates your field service and sales data under the Microsoft ecosystem. FlitStack AI maps customer records, work order history, equipment assets, and custom fields into Dynamics 365 Sales tables — preserving original timestamps, technician assignments, and service-category tags so your Dynamics 365 reporting reflects the full service lifecycle from day one.
FlitStack AI migrates accounts, contacts, work_order__cs, work_order_line__cs and asset or asset__cs from Bella FSM to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records.

What moves from Bella FSM to Dynamics 365?
Bella FSM is a field service management platform built around work orders, job scheduling, technician dispatch, equipment tracking, and invoicing.
Read the full summary
Its data model organizes records around Customers, Jobs, Work Orders, Equipment, Inventory, and Vendors with time-tracking and signature-capture features per job. Microsoft Dynamics 365 Sales is a traditional CRM built around Leads, Opportunities, Accounts, and Contacts stored in Dataverse with customizable tables and business rules. The two platforms share a customer-centric model — both store account and contact records with address and phone data — but Bella FSM's scheduling, dispatch, and equipment objects have no native equivalents in Dynamics 365 Sales. FlitStack AI migrates everything that has a direct or custom equivalent: customers and contacts become Accounts and Contacts; work order headers become a custom Work_Order__c table; equipment records become Assets; invoice line items become Opportunity Product records. Scheduling logic, dispatch rules, and technician route data require manual rebuild using Dynamics 365 Sales or Power Platform tools. The migration uses Dynamics 365's Dataverse API for structured record creation with field-level validation. A 24–48 hour delta-pickup window captures any jobs created or updated during cutover so Dynamics 365 reflects Bella FSM's final state at go-live.
Customer → Account
Bella FSM customer records map directly to Dynamics 365 Sales Accounts.
How it maps
The customer name, billing address, shipping address, and primary contact fields align one-to-one. Multi-location customers in Bella FSM become parent-child Account hierarchies in Dynamics 365 using the ParentAccountId lookup.
Customer Contact → Contact
Every Bella FSM customer contact maps to a Dynamics 365 Contact linked to the corresponding Account via AccountId.
How it maps
Email, phone, mobile phone, job title, and address fields carry over directly. Secondary contacts on the same customer become additional Contact records sharing the same Account.
Job / Work Order → Work_Order__c (Custom Table)
Bella FSM Jobs have no native equivalent in Dynamics 365 Sales.
How it maps
FlitStack creates a custom Work_Order__c table in Dataverse to store job header data: job number, status, scheduled date, assigned technician, service category, customer reference, and original create date. This table links to the Account via a lookup field.
Work Order Line Item → Work_Order_Line__c (Custom Table)
Bella FSM work order line items (parts, labor, fees) map to a custom Work_Order_Line__c table linked to Work_Order__c.
How it maps
Line type (part, labor, fee), quantity, unit price, and total map to corresponding fields. This preserves the itemized structure that drives invoicing in Bella FSM.
Equipment → Asset (Dynamics 365 Field Service) or Asset__c (Custom)
Bella FSM equipment records track assets installed at customer sites — serial number, make, model, install date, and service history.
How it maps
Dynamics 365 Field Service includes an Asset table natively; without Field Service licensed, FlitStack creates a custom Asset__c table in Dataverse to store equipment data linked to the customer Account.
Inventory / Parts → Product
Bella FSM inventory parts (part number, description, cost, list price, quantity on hand) map to Dynamics 365 Product records.
How it maps
The parts warehouse location from Bella FSM is stored as a custom field on Product since Dynamics 365 Inventory is part of Supply Chain Management, not Sales.
- CustomerAccount1:1
- Customer ContactContact1:1
- JobWork_Order__ctransformed
- Work Order Line ItemWork_Order_Line__ctransformed
- EquipmentAsset or Asset__ctransformed
- InventoryProducttransformed
+ 6 more in the mapping below
How Bella FSM and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Bella FSM | Dynamics 365 |
|---|---|---|
| Core data model focus | Bella FSM is work-order-centric — Jobs and Work Orders drive scheduling, dispatch, and billing. Customers and equipment exist as supporting records attached to jobs. | Dynamics 365 Sales is opportunity-centric — Leads and Opportunities drive the sales pipeline. Accounts and Contacts are the primary customer records. |
| Scheduling and dispatch | Bella FSM includes drag-and-drop calendar, real-time dispatch board, and technician route optimization as native features. | Dynamics 365 Sales has no native dispatch board. Scheduling requires Dynamics 365 Field Service or Power Apps custom development. |
| Equipment and asset tracking | Bella FSM tracks equipment per customer with service history, maintenance schedules, and parts used — stored as Equipment records. | Dynamics 365 Sales stores Assets in the AssetManagement module (requires Field Service or custom) or as custom Asset__c records in Dataverse. |
| Work order structure | Bella FSM Work Orders include status, line items, parts, labor, time tracking, checklists, and customer signatures — all in one record. | Dynamics 365 Sales has no Work Order object. Jobs map to a custom Work_Order__c table; line items become Opportunity Products or custom Invoice_Line__c records. |
| Invoicing model | Bella FSM generates invoices directly from work orders with line items, tax, and payment status tracking built in. | Dynamics 365 Sales creates Quotes and Orders but relies on Dynamics 365 Business Central or an integrated ERP for full AR/AP invoicing. |
| Pricing tier | Bella FSM starts at $35/month base plus $10/user/month for additional seats, with add-on modules like eSignature and Advanced Inventory. | Dynamics 365 Sales Professional starts at $65/user/month; Enterprise at $105/user/month. Additional modules (Field Service, Business Central) add separate licensing costs. |
Bella FSM to Dynamics 365 field mapping
The 30 most-used fields of 46 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
customernameCustomerNameAccount -
customeremailCustomerEmailContact -
customerphoneCustomerTelephone1Account -
billingaddress1CustomerAddress1_Line1Account -
billingaddress2CustomerAddress1_Line2Account
| Bella FSM field | Dynamics 365 field | Mapping | Note |
|---|---|---|---|
Customer.customername | Account.Name | direct | |
Customer.customeremail | Contact.Email | direct | |
Customer.customerphone | Account.Telephone1 | direct | |
Customer.billingaddress1 | Account.Address1_Line1 | direct | |
Customer.billingaddress2 | Account.Address1_Line2 | direct | |
Customer.billingcity | Account.Address1_City | direct | |
Customer.billingstate | Account.Address1_StateOrProvince | direct | |
Customer.billingzip | Account.Address1_PostalCode | direct | |
Customer.customernotes | Account.Description | direct | |
Customer.createddate | Account.Original_Create_Date__c | custom_field_required | Dynamics 365 sets CreatedDate at migration time; original Bella FSM create date preserved as a custom datetime field for reporting continuity. |
Contact.contactfirstname | Contact.FirstName | direct | |
Contact.contactlastname | Contact.LastName | direct | |
Contact.contactemail | Contact.Email | direct | |
Contact.contactphone | Contact.Telephone1 | direct | |
Contact.contactmobile | Contact.MobilePhone | direct | |
Contact.contactjobtitle | Contact.JobTitle | direct | |
Work Order.workordernumber | Work_Order__c.Name | direct | |
Work Order.workorderstatus | Work_Order__c.Status__c | value_mapping | Bella FSM status values (Scheduled, In Progress, Completed, Cancelled) map to corresponding values in the custom Status__c pick-list on Work_Order__c. |
Work Order.scheduleddate | Work_Order__c.Scheduled_Date__c | direct | |
Work Order.completeddate | Work_Order__c.Completed_Date__c | direct | |
Work Order.servicecategory | Work_Order__c.Service_Category__c | direct | |
Work Order.technicianassigned | Work_Order__c.Assigned_Technician__c | transformed | Technician name resolved to a Contact record with Role='Field Technician' by email match; the Contact ID stored as the lookup value. |
Work Order.customerid | Work_Order__c.AccountId | direct | |
Work Order.workordernotes | Work_Order__c.Description | direct | |
Work Order Line Item.itemtype | Work_Order_Line__c.Line_Type__c | value_mapping | Line types (Part, Labor, Fee) map to Option Set values in the custom Line_Type__c field on Work_Order_Line__c. |
Work Order Line Item.itemdescription | Work_Order_Line__c.Description | direct | |
Work Order Line Item.quantity | Work_Order_Line__c.Quantity__c | direct | |
Work Order Line Item.unitprice | Work_Order_Line__c.Unit_Price__c | direct | |
Work Order Line Item.linetotal | Work_Order_Line__c.Line_Total__c | direct | |
Equipment.equipmentname | Asset__c.Name | direct |
What to watch for in a Bella FSM to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Work orders require a custom Dataverse table with no native Dynamics 365 Sales equivalent
Bella FSM's work order is the central record for scheduling, dispatch, parts, labor, and billing.
How we handle it
Dynamics 365 Sales has no native Work Order entity — the Opportunities table manages deals, not field service tasks. FlitStack creates a custom Work_Order__c table in Dataverse to store job data, but this requires pre-migration schema setup in your Dynamics 365 environment. Dynamics 365 Sales Professional limits custom tables to 15; Enterprise removes this ceiling. If you are on Professional and need Work_Order__c, Asset__c, and Work_Order_Line__c, you may exceed the table limit and need to consolidate or upgrade to Enterprise before migration.
Bella FSM scheduling and dispatch logic has no equivalent in Dynamics 365 Sales
Bella FSM's drag-and-drop calendar, real-time dispatch board, and technician route assignments are FSM-specific features that do not translate to any Dynamics 365 Sales native object.
How we handle it
Dynamics 365 Field Service includes a Resource Schedule Optimization engine, but it requires a separate Field Service license and operates within its own entity model. FlitStack preserves work order records with scheduled dates and technician assignments, but the dispatch board and routing rules must be rebuilt in Dynamics 365 Field Service or as Power Apps components. We export Bella FSM scheduling rules as a configuration reference for your rebuild.
Equipment tracking requires custom table or Field Service licensing decision
Bella FSM equipment records store make, model, serial number, install date, warranty info, and service history per customer site.
How we handle it
Dynamics 365 Sales has no native Asset table — it lives in the Dynamics 365 Field Service module (AssetManagement). Migrating equipment without Field Service means FlitStack creates a custom Asset__c table in Dataverse, which preserves the data but lacks the maintenance scheduling and IoT integration that Field Service Assets provide. Your team must decide pre-migration whether to license Field Service or accept the custom table approach.
Bella FSM invoice-to-payment workflow diverges from Dynamics 365 quote-to-cash model
Bella FSM generates invoices directly from work orders and tracks payment status (Draft, Sent, Paid, Overdue).
How we handle it
Dynamics 365 Sales manages Quotes, Orders, and Invoices — but the Invoice entity is designed for creating PDF invoices rather than full AR tracking. AR automation (payment receipts, credit notes, aging) lives in Dynamics 365 Business Central. FlitStack migrates paid Bella FSM invoices as Fulfilled Orders; outstanding invoices become Open Orders. Your accounting team should reconcile any outstanding balances against Business Central or your preferred AR tool post-migration.
Custom data fields in Bella FSM require manual field creation in Dataverse before migration
Bella FSM allows text, checkbox, and dropdown custom fields on Customer and Job pages.
How we handle it
Dynamics 365 Sales stores custom fields as Dataverse columns that must be created before data loads — there is no auto-migration of custom field definitions. FlitStack audits your Bella FSM custom field inventory during the discovery phase and delivers a Dataverse field creation checklist so your admin can pre-provision the schema. Custom dropdown values must be recreated as Option Sets with identical labels to preserve reporting continuity in Dynamics 365.
How the migration runs
Audit Bella FSM data and design Dataverse schema
FlitStack extracts a full export of your Bella FSM data — customers, contacts, work orders, line items, equipment, inventory, vendors, and time entries.
What this step covers
We audit record counts, custom field inventory, and data quality (duplicate detection, missing required fields). Based on the audit, we deliver a Dataverse schema plan: which custom tables to create (Work_Order__c, Asset__c, Work_Order_Line__c), which fields to add to Account and Contact, and which Option Set values to pre-populate. Your Dynamics 365 admin creates the schema before the migration run so field IDs are ready for mapping.
Map and transform records by foreign-key dependency order
Dynamics 365 requires parent records to exist before children can reference them.
What this step covers
FlitStack sequences the migration in dependency order: Vendors (as Accounts) → Customers (as Accounts) → Contacts → Products (from Inventory) → Work Orders → Work Order Lines → Equipment (as Assets) → Time Entries → Invoices (as Orders) → Invoice Lines. Each batch resolves foreign keys — Work_Order__c.AccountId links to the migrated Account; Work_Order_Line__c.Work_Order__c links to its parent Work Order. Unresolved references are flagged and routed to a fallthrough table for admin resolution.
Resolve technician and user identities by email
Bella FSM users and technicians are matched to Dynamics 365 Users by email address.
What this step covers
Technicians who are not Dynamics 365 licensed users migrate as Contacts with a custom Role__c field set to 'Field Technician'. Owner fields on Work_Order__c records point to the resolved Contact or User. Unmatched emails are flagged in a pre-flight report — your team either creates the corresponding Dynamics 365 User or assigns a fallback owner before the full migration runs.
Run a sample migration with field-level diff
A representative slice migrates first — typically 200–500 records spanning 10–20 work orders, 50 customers, 5 equipment records, and 3 invoices.
What this step covers
FlitStack generates a field-level comparison report showing source values versus destination field values for every mapped column. You verify that work order status mapping, equipment account linking, and invoice totals are correct before the full run commits. Any mapping adjustments are applied to the migration configuration before the production run.
Execute full migration with delta-pickup window
The full migration runs against your Dynamics 365 environment using the Dataverse API with batched requests to stay within request allocation limits.
What this step covers
A 24–48 hour delta-pickup window opens simultaneously — any Bella FSM records created or modified during the migration window are captured and applied after the initial batch completes. FlitStack generates an audit log of every record created, updated, or skipped. If reconciliation identifies mismatches, one-click rollback reverts the target environment to its pre-migration state.
Bella FSM - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record count, the number of custom tables required in Dataverse, and whether equipment and work-order history need custom mapping. Bella FSM setups with dense work-order histories — multiple line items, time entries, and equipment attachments per job — fall toward the upper range because each related record requires its own foreign-key resolution in Dynamics 365. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Bella FSM to Dynamics 365 →Why teams move from Bella FSM to Dynamics 365
- Field service operations have grown beyond scheduling-only scope — leadership needs consolidated sales pipeline visibility alongside service data in one Microsoft environment. Teams report that exporting Bella FSM reports into spreadsheets for sales forecasting adds days to close-loops and creates version-control chaos.
- Microsoft-first strategy requires Dynamics 365 as the system of record for CRM while keeping field operations data accessible via Power BI dashboards and Dataverse connections. Reviewers on G2 highlight Dynamics 365's integration with Microsoft 365 tools as a key differentiator over standalone FSM platforms.
- Bella FSM's accounting module is frequently described as limited by reviewers and power users. Businesses with complex billing requirements—such as progress invoicing, subcontractor cost tracking, multi-phase change orders, and retainage—find that Bella FSM lacks the depth needed for full AR automation. Migrating to Dynamics 365's quote-to-cash model combined with Business Central integration provides the invoicing sophistication, payment tracking, and financial reporting these organizations require.
- When an organization acquires another company that already runs Dynamics 365 Sales, consolidating both operations onto a single Microsoft CRM platform eliminates the overhead of maintaining multiple systems and duplicate licensing costs. This consolidation enables cross-company reporting, unified customer views, and streamlined service operations across the merged entity. It also allows leadership to leverage existing Dynamics 365 investments without requiring the acquired company to migrate away from their established CRM infrastructure.
Questions, answered
Bella FSM to Dynamics 365 migration questions
How long does a Bella FSM to Dynamics 365 Sales migration take?
Most Bella FSM to Dynamics 365 Sales migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 100,000+ work orders, dense equipment histories, or multiple custom Dataverse tables extend to 5–10 days. The longest planning step is pre-migration schema setup — creating custom Work_Order__c and Asset__c tables in Dataverse — which your admin performs in parallel with our discovery phase. Data extraction from Bella FSM itself is typically the fastest step; validation and delta-pickup take the most time.
Will my Bella FSM scheduling rules and dispatch workflows migrate to Dynamics 365?
No. FlitStack AI migrates data and schema only — scheduling rules, dispatch board configurations, and automation workflows do not transfer between platforms. Bella FSM's dispatch logic lives in the application's scheduling engine with no export mechanism. We provide a Configuration Export document that lists every scheduling rule, route, and technician assignment from Bella FSM so your Dynamics 365 admin or Power Apps developer can rebuild the dispatch logic in Dynamics 365 Field Service or a custom Power Apps scheduling board. This is manual work that must be accounted for in your migration project plan.
What do Bella FSM work orders become in Dynamics 365 Sales?
Bella FSM work orders have no native equivalent in Dynamics 365 Sales, so FlitStack creates a custom Work_Order__c table in Dataverse. Work order number, status, scheduled date, completed date, service category, and assigned technician migrate as fields on this custom table. Line items (parts, labor, fees) become records in a linked Work_Order_Line__c table. Work orders link to the customer Account via a lookup. If you have Dynamics 365 Field Service licensed, these records can be upgraded to the native Work Order entity — FlitStack's schema plan supports both paths.
Can I migrate Bella FSM equipment records to Dynamics 365?
Yes. Bella FSM equipment records migrate as custom Asset__c records in Dataverse — storing serial number, make, model, install date, warranty info, and service history linked to the customer Account. If you license Dynamics 365 Field Service, these can be upgraded to the native AssetManagement entity which adds maintenance scheduling and IoT integration. Equipment without Field Service licensed uses the custom table approach, preserving all data but without the advanced asset lifecycle features. FlitStack surfaces this decision during the discovery phase so you can choose the approach that fits your licensing.
Does the migration affect my Bella FSM account during cutover?
No. FlitStack AI uses scoped read access on Bella FSM — your team continues working in Bella FSM throughout the migration. A 24–48 hour delta-pickup window captures any work orders, invoices, or customer records created or updated during the cutover. FlitStack does not modify your Bella FSM data in any way. At go-live, Dynamics 365 reflects Bella FSM's final state including all delta changes. Your team can choose a cutover weekend to minimize the delta window if operational continuity is a concern.
What happens to Bella FSM invoices and payment history in Dynamics 365?
Bella FSM invoices migrate to Dynamics 365 Sales as Order records. Paid invoices become Fulfilled Orders with the original invoice total preserved in the TotalAmount field. Outstanding invoices become Open Orders awaiting closure. Invoice line items map to Order Product records. Payment receipts, credit notes, and AR aging require Dynamics 365 Business Central or a separate accounting tool — Dynamics 365 Sales Order management covers the transactional record but not full accounts receivable automation. FlitStack's pre-migration report identifies all outstanding invoice balances so your finance team can plan the AR reconciliation.
How are Bella FSM custom data fields handled during migration?
Bella FSM custom fields on Customer and Job pages (text inputs, checkboxes, dropdown menus) require manual pre-creation in Dataverse before migration runs. FlitStack delivers a Custom Field Audit during the discovery phase listing every custom field by object, type, and option values. Your Dynamics 365 admin creates matching custom fields on the Account, Contact, and Work_Order__c tables. Text fields become Text columns, checkboxes become Two Option fields, and dropdowns become Option Sets with identical labels. FlitStack then maps these fields in the migration configuration so data loads correctly once the schema is in place.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Sugarcrm to Dynamics 365Mapping · history · rollbackmonday CRM to Dynamics 365Mapping · history · rollbackConvertkit to Dynamics 365Mapping · history · rollbackJonas Enterprise Service & Construction Software to Dynamics 365Mapping · history · rollbackDrivecentric to Dynamics 365Mapping · history · rollbackCustomer.io to Dynamics 365Mapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Bella FSM to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote