Migrate from Bella FSM to HubSpot

Bella FSM customers split into HubSpot Contacts (individual service requesters) and Companies (business accounts). When Bella stores a business name on a customer record, that becomes both a HubSpot Company and a Contact linked to it. Unnamed individual customers become Contacts without a Company association.

Bella FSM work orders map to HubSpot Deals as the primary job container. Deal name derives from the Bella job title or a auto-generated string combining customer name + date. Job status (Estimate, Scheduled, In Progress, Completed, Invoiced) maps to custom deal properties; HubSpot's native Deal Stage tracks revenue pipeline separately.

Bella's job status values (Estimate, Scheduled, In Progress, On Hold, Completed, Invoiced, Cancelled) map to a custom single-select property (Job_Status__c) on the Deal. Each value carries forward exactly. Stage-based pipeline reporting in HubSpot uses a separate native Deal Stage property for revenue forecasting.

Bella's equipment records (asset name, serial number, install date, maintenance intervals) become a HubSpot custom object Equipment__c linked to the Customer's Contact or Company record. Custom properties capture serial number, model, warranty expiration, and last service date. N:1 associations connect each piece of equipment to its registered customer.

Bella's Advanced Inventory records (part number, description, quantity on hand, warehouse location) migrate to a HubSpot custom object Inventory_Item__c. Each inventory item associates to the vendor Company record. Quantity adjustments and purchase orders require manual rebuild in HubSpot's Operations Hub or an inventory management integration.

Bella FSM vendors become HubSpot Companies with a custom property Vendor_Type__c set to 'Vendor' to distinguish them from customer accounts. Vendor contact records attach to the Company as associated Contacts. Vendor-specific terms and payment info migrate as custom text properties.

Bella invoices with parts and labor line items become HubSpot Deal line items on the associated Job Deal. Each line item carries product name, quantity, unit price, and total. Invoice status (Draft, Sent, Paid, Overdue) migrates as a custom property on the Deal; actual invoice PDF generation requires QuickBooks or a third-party billing tool.

Bella FSM estimates become HubSpot Deals with status set to 'Estimate'. The estimate total amount maps to Deal Amount. If converted to a job in Bella, the Deal stage updates to reflect job status. Estimate expiry dates migrate as a custom date property on the Deal.

Bella's custom fields on the customer page (text inputs, checkboxes, dropdowns) become HubSpot contact properties. Field type maps directly — Bella dropdowns become HubSpot pick-list properties, checkboxes become single-checkbox properties, text inputs become single-line text properties. Property names preserve Bella's labels for traceability.

Bella's custom fields on the job page migrate as custom Deal properties using the same type-mapping logic. Field inspections, checklists, approval flags, and any custom fields capturing job-specific data carry forward as HubSpot deal properties or single-checkbox fields for process tracking. Property names and labels are preserved from Bella for traceability back to source records.

Bella FSM file attachments on jobs and customers download and re-upload to HubSpot Files associated to the matching Contact, Company, or Deal record. Large files (Bella allows any file type) are subject to HubSpot's file size limits. Inline images in notes are rehosted as HubSpot-hosted files.

Bella FSM technician and staff accounts resolve to HubSpot users by email match. Unmatched users are flagged before migration — teams either invite them to HubSpot first or assign their records to a fallback owner. Bella user roles (admin, standard) are noted but HubSpot's role and team model must be reconfigured post-migration.

Bella's recurring visit schedules become HubSpot Deals with a custom property Recurring_Frequency__c (weekly, monthly, quarterly) and Next_Service_Date__c. Each scheduled occurrence becomes a separate Deal linked to the parent recurring contract Deal for grouping and reporting. This structure allows service managers to track both individual visits and the overarching recurring service agreement.

Bella's Customer Portal add-on — giving clients online access to request service, view job history, and approve estimates — has no direct HubSpot equivalent. We document the portal access configuration for reference so teams can evaluate HubSpot's customer portal features (available in Service Hub Enterprise) post-migration.

Bella eSignature captures on estimates and work orders migrate as Documents attached to the corresponding Deal, with a custom property Signature_Captured__c set to true and a timestamp. HubSpot's native document signing feature (Sales Hub Professional+) can replicate this capability for new documents going forward.

Bella's QuickBooks integration syncs invoices and customer records to accounting. We preserve the QuickBooks ID as a custom property (QB_Invoice_ID__c, QB_Customer_ID__c) on Deals and Contacts for reference, but the integration must be rebuilt using HubSpot's QuickBooks connector or a middleware tool post-migration. All QB ID references are preserved for reconciliation during the transition period.