Migrate from Bella FSM to Salesforce Sales Cloud

Bella FSM Customer maps to Salesforce Account as the primary company record, with Contact records created for each named contact on the Bella FSM customer. Primary phone and email from Bella FSM populate the Account phone/website and Contact email/phone respectively. Customers with multiple locations become parent Account with child Account records linked via ParentId.

Bella FSM Jobs have no native Salesforce equivalent — a custom Work_Order__c object is required. We create the object with custom fields for job type (picklist), status (picklist), priority (picklist), description (textarea), scheduled date, completed date, PO number, and job cost. The object links to Account via AccountId lookup and to User via Technician__c lookup.

Each line item on a Bella FSM Job becomes a Work_Order_Line_Item__c record with a Master-Detail relationship to Work_Order__c. Fields include: part number, description, quantity, unit price, and line total. This preserves itemized billing detail that would otherwise collapse into a single job cost field.

Bella FSM Technicians map to Salesforce Users by email match as the primary resolution key. Employee name maps to User Name; email becomes the Username field. Active/Inactive status in Bella FSM determines Salesforce User.isActive flag directly. Technicians without a verifiable email are flagged before migration for admin resolution or fallback User assignment to preserve historical job records.

Bella FSM Invoices map to Salesforce Opportunities when a deal-based workflow exists, with invoice amount populating Opportunity.Amount and invoice status stored as a custom Invoice_Status__c pick-list on the Opportunity. For pure invoicing without a sales pipeline, invoice records migrate to a custom Invoice__c object linked to the Account.

Bella FSM equipment records map to the standard Salesforce Asset object. Asset.Name maps from Bella FSM equipment name. SerialNumber maps to Product2 product code if a matching product exists, otherwise stored as a custom field. InstallDate and Status (Active/Retired) carry over from Bella FSM service history.

Bella FSM Vendors map to Salesforce Accounts with a Vendor_Type__c custom field set to 'Vendor' to distinguish them from customer Accounts. Vendor address, phone, and contact information map identically to Account fields. Account.vendor_type__c enables filtered views that separate vendor records from customer accounts in reports.

Bella FSM custom data fields on the Customer page (text, checkbox, or drop-down) become Salesforce custom fields on Account. Text fields map to Text(255) or TextArea. Checkbox maps to Checkbox. Drop-down values create a pick-list with the source options preserved verbatim. Field-level mapping is validated against the custom field definition export from Bella FSM before migration.

Bella FSM custom data fields on the Job page follow the same type-aware translation to Work_Order__c custom fields. Drop-down field values are mapped value-by-value using a pick-list mapping table. Any industry-specific fields (e.g., HVAC load calculations, electrical panel ratings) are preserved as custom text fields if no Salesforce standard field exists.

Bella FSM scheduled appointments map to Salesforce Events. StartDateTime and EndDateTime carry over. Subject is set from Bella FSM job name or appointment type. Event is linked to the related Work_Order__c record via WhatId. Recurring appointments in Bella FSM generate individual Event records per occurrence since Salesforce does not natively support recurrence across different objects.

Bella FSM file attachments (photos, signed forms, inspection checklists) are downloaded and re-uploaded as Salesforce Files linked to the corresponding Work_Order__c record. File size limits of 25MB per file apply. Inline images from notes are extracted and rehosted as Salesforce Files with a reference link in the Work_Order__c description.

Bella FSM inventory parts split across two Salesforce objects: Product2 holds the part name, part number, and standard price. A custom Inventory_Location__c object tracks quantity on hand per location (warehouse, truck) linked to Product2 via Lookup. This preserves truck-level inventory visibility that Bella FSM captures natively.