Migrate from Bella FSM to Microsoft Dynamics 365 Sales

Bella FSM customer records map directly to Dynamics 365 Sales Accounts. 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.

Every Bella FSM customer contact maps to a Dynamics 365 Contact linked to the corresponding Account via AccountId. 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.

Bella FSM Jobs have no native equivalent in Dynamics 365 Sales. 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.

Bella FSM work order line items (parts, labor, fees) map to a custom Work_Order_Line__c table linked to Work_Order__c. 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.

Bella FSM equipment records track assets installed at customer sites — serial number, make, model, install date, and service history. 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.

Bella FSM inventory parts (part number, description, cost, list price, quantity on hand) map to Dynamics 365 Product records. 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.

Bella FSM vendors map to Dynamics 365 Accounts tagged with an account type of 'Vendor'. The vendor name, address, and contact fields align directly. No separate Vendor object exists in Dynamics 365 Sales — all parties are Accounts with a type designation.

Bella FSM invoices map to Dynamics 365 Sales Quotes in 'Active' or Orders in 'Fulfilled' state. Invoice line items map to Opportunity Product or Order Product records. Paid status from Bella FSM sets the Order status to 'Fulfilled'; outstanding invoices become open Orders awaiting closure.

Bella FSM time entries tracking technician labor hours map to a custom Time_Entry__c table linked to Work_Order__c and the technician Contact. Hourly rate and total labor cost are stored as numeric fields. For simpler cases, Activities (Tasks) can represent labor entries with duration and subject fields.

Bella FSM custom data fields on Customer and Job pages (text, checkbox, dropdown) map to custom fields in Dataverse on the corresponding tables. Text fields become Text fields; checkboxes become Two Option fields; dropdowns become Option Sets with the same value labels preserved.

Bella FSM users and technicians are resolved by email against Dynamics 365 Users. Technicians who are not Dynamics 365 licensed users migrate as Contacts with a custom Role field (e.g., 'Field Technician') to preserve their identity in work order assignments.

Bella FSM file attachments on work orders, equipment records, and customer profiles migrate to Dynamics 365 as Annotations, with the file body encoded as base64 to preserve the original document structure. Signature images captured during work order completion also become Annotations linked to the corresponding Work_Order__c record, maintaining the complete audit trail. All migrated attachments retain their original filenames for compatibility when opened or downloaded.