Migrate from Bella FSM to Twenty CRM

Bella FSM stores company name, address, and primary contact fields in a single Customer record. FlitStack AI splits this into a Twenty Company record (company name, domain, industry, address) and a Twenty People record (contact name, email, phone, job title) linked via companyId. The primary contact's details populate the People record; company-level data populates Company.

Bella custom data fields on the Customer page (text input, checkbox, dropdown) map directly to Twenty People custom fields with the same data type. The field name is preserved; dropdown options in Bella map to Twenty select options. All custom fields must be pre-created in Twenty's Settings → Data Model before import runs.

Bella Jobs contain status, description, scheduled date, assigned technician, parts used, labor hours, and checklist results. These map to Twenty Tasks (title, due date, assignee, body with job notes) or a custom ServiceTicket object if the team needs to preserve parts, labor cost, and checklist data as structured fields rather than free-text notes.

Bella custom data fields on the Job page migrate as Twenty Task custom fields. Text fields, checkboxes, and dropdowns map to their Twenty equivalents. Job-specific dropdowns (e.g., job type, priority) require value-mapping if the options differ between Bella and Twenty.

Bella FSM's Equipment Tracking stores asset serial numbers, model numbers, maintenance history, and customer linkage. Twenty has no standard Equipment object. FlitStack AI creates a custom Equipment object in Twenty with fields for serialNumber, model, lastServiceDate, and a Company relation. Historical maintenance records migrate as Tasks linked to the Equipment record.

Bella FSM's Advanced Inventory tracks parts across warehouses, trucks, and job sites. This has no Twenty equivalent. We create a custom InventoryItem object with fields for partNumber, description, quantityOnHand, location, and a relation to Company for parts assigned to a customer site.

Bella FSM's invoicing module generates line-item invoices with payment status. Twenty CRM has no native invoicing. We preserve invoice data as a custom Invoice object (invoiceNumber, amount, status, date, line items) linked to the associated Company or People record. Payment history is stored as custom fields on the Invoice record.

Bella FSM's Vendor records contain name, contact, and payment terms. These map to Twenty Company records with a vendorType custom field set to 'Vendor'. The same Company object is used for both customers and vendors — a type tag distinguishes them.

Bella FSM employees and technicians map to Twenty WorkspaceMembers. FlitStack AI resolves Bella employee email addresses against Twenty user invitations — technicians must be invited to Twenty before migration so job assignments can map to the correct assignee. Unmatched technicians are flagged for manual resolution.

Bella FSM file attachments on customers, jobs, or equipment re-upload to Twenty as Notes with file attachments. The original file name and create date are preserved. Bella's File Attachments add-on content migrates as Twenty Note records linked to the relevant People, Company, or Task.

Bella FSM's scheduling and dispatch calendar (drag-drop calendar, technician routing, real-time dispatch board) has no Twenty CRM equivalent. Scheduling data is not migrated. Teams rebuild scheduling logic in Twenty's workflow builder or integrate a dedicated scheduling tool post-migration.

Bella FSM automations and dispatch rules do not transfer to Twenty CRM. These include time-based triggers, event-driven actions, and conditional logic built within Bella's workflow engine. Twenty's own workflow builder can recreate similar time-based and event-based automations, but the specific rules must be documented and manually rebuilt. FlitStack AI exports Bella workflow definitions as a reference document for your operations team to use during the rebuild process.