Migrate from Bella FSM to HighLevel

Bella FSM Customer records migrate directly to HighLevel Contacts with all standard contact fields preserved. Name, email, phone, and address map one-to-one. The Bella customer record ID is stored in a custom field for traceability and future delta-run de-duplication. Any duplicate customer detection flags records with matching email addresses before insertion to prevent duplicate contact creation in the target HighLevel account.

Bella FSM business name, phone, website, and address fields map to a corresponding HighLevel Company record. Where no separate company exists in Bella FSM, the contact's company name becomes the Company name in HighLevel. We preserve the Bella company ID in a custom Company field to maintain referential integrity between migrated customer and company records. Parent-company hierarchies in Bella FSM map to HighLevel company relationships.

Each Bella FSM Job becomes a HighLevel Opportunity. The job name becomes the opportunity name, the Bella job status maps to a HighLevel pipeline stage value, and the assigned Field Resource is stored in a custom opportunity field. Original job ID is preserved in a custom field for delta-run de-duplication. Line items attached to the Bella job migrate as Opportunity Product items linked to the opportunity record.

Bella FSM job status pick-list values such as 'Scheduled', 'In Progress', 'Completed', or 'Contract' map to corresponding HighLevel pipeline stage values. Custom Bella status names require value-by-value mapping against your target HighLevel pipeline stages before migration runs. We provide a status-mapping worksheet during discovery and require written confirmation of the mapping before any records load. Mis-mapped statuses cause jobs to land in the wrong pipeline stage, which then breaks downstream automation triggers.

Bella FSM Field Resources (technicians and employees) do not have a native equivalent in HighLevel. We create a custom text or contact-reference field on the relevant Opportunity to store the assigned technician name. Employee role data migrates as a custom field value. Field resource records themselves can optionally be created as separate Contacts tagged as 'Field Resource' for internal reporting and dispatch lookup in HighLevel.

Bella FSM Vendor records map to HighLevel Contacts with a vendor-type tag applied. Vendor contact name, email, phone, and address migrate as contact fields. The vendor tag distinguishes vendor contacts from customer contacts in HighLevel reporting and workflow filters. Vendor-specific custom fields on the Bella vendor record replicate as Contact custom fields in HighLevel. Vendor-to-job purchase order associations are preserved via the opportunity record.

Bella FSM custom fields on the Customer page (text, checkbox, dropdown) require pre-creation as HighLevel Contact custom fields before migration. The field type (text, checkbox, picklist) is replicated in HighLevel's custom field schema. We map field values value-by-value during the bulk import, and picklist options in Bella translate to picklist options in HighLevel. Any conditional visibility rules in Bella custom fields must be rebuilt manually in HighLevel's form builder post-migration.

Bella FSM custom fields on the Job page migrate as HighLevel Opportunity custom fields. Note that HighLevel does not allow switching a field between Contact and Opportunity type after creation — we confirm the correct object assignment before creating any fields. We audit the Bella custom field definition for each job-page field during discovery to determine the appropriate field type in HighLevel. Hidden or read-only field behaviors in Bella do not carry over and require manual configuration in HighLevel.

Bella FSM's Equipment Tracking module has no native equivalent in HighLevel. Equipment records including serial number, model, status, and maintenance notes migrate as a HighLevel Custom Object with custom fields for each attribute. Junction relationships to Customer or Job records require custom relationship fields. Maintenance history and service logs associated with equipment records are preserved as note attachments or in a separate custom object since HighLevel lacks native asset lifecycle tracking.

Bella FSM Advanced Inventory — parts, warehouses, stock levels, and purchase orders — splits across two destinations: line items on migrated Jobs become Opportunity Product items in HighLevel. Serialized inventory tracking and multi-warehouse stock levels require a custom inventory object rebuild post-migration. Purchase order records do not have a native HighLevel equivalent and must be exported as CSV for manual re-entry or third-party inventory management integration.

Bella FSM Estimates and their line items map to HighLevel Opportunity Product items. The estimate total and individual line-item prices migrate with the job-opportunity record. Estimate status (e.g., Draft, Sent, Accepted) is preserved as a custom opportunity field. If the Bella estimate includes custom fields, those replicate as custom fields on the HighLevel opportunity record. Accepted estimates in Bella that represent signed work authorizations can trigger pipeline stage advancement in HighLevel workflows.

Bella FSM file attachments on Customer and Job records are downloaded and re-uploaded to the corresponding HighLevel Contact or Opportunity record. Standard HighLevel file size limits apply: 25MB per file for standard accounts and up to 100MB for accounts with expanded storage. We preserve original file names and attachment timestamps. Attachments associated with equipment records are linked to the custom Equipment object in HighLevel using custom relationship fields.