Migrate from Bella FSM to Pipedrive

Bella FSM Customer maps directly to Pipedrive Organization. The company name becomes Organization.Name, domain maps to Organization.Address, and industry can be mapped via value_mapping. Multi-location customers require separate Organization address records or address custom fields. We also recommend storing the customer’s primary phone as Organization.Phone via a custom field, and flagging multi-location accounts with a Location_Count metric to preserve reporting continuity.

Bella FSM Customer contact details (name, email, phone) map to Pipedrive Person. The primary contact on the Bella FSM Customer record becomes a Person linked to the Organization via the Person's Organization ID relationship. Secondary contacts on the same customer may require duplicate Person records or an alternate contact role field.

Bella FSM Job maps to Pipedrive Deal. The job name becomes Deal.title, job status maps to a Pipedrive pipeline stage value (Quote Sent → Won, In Progress → Deal, Completed → Won/Closed Lost), and the linked Customer becomes the Deal's Organization. The job value or estimated amount maps to Deal.value.

Bella FSM job statuses ('Quote Sent', 'Job Scheduled', 'In Progress', 'Completed', 'Cancelled') map to Pipedrive pipeline stage values. Each Bella FSM pipeline in use requires a corresponding Pipedrive pipeline. We preserve the original job status as Deal.Status or as a custom field for historical reporting continuity.

Bella FSM Work Orders are operational sub-records of a Job tracking dispatch, technician assignment, and completion notes. Pipedrive has no Work Order object. We migrate Work Order data as Deal Activities (Type: task) with the dispatch notes in the activity body and technician assigned via the owner_id mapping. Work Order completion status is preserved as a custom field on the Activity.

Bella FSM custom data fields on the Customer page (text, checkbox, drop-down) have no Pipedrive equivalent in the standard Person or Organization schema. We create Pipedrive custom fields via POST /personFields and /organizationFields using matching field types (text to VARCHAR, checkbox to BOOLEAN, drop-down to SET). The exact field type must be confirmed during the field-level diff before creation.

Bella FSM custom data fields on the Job page (text, checkbox, drop-down) map to Pipedrive Deal custom fields. Created via POST /dealFields. Drop-down custom fields in Bella FSM with custom option lists require value_mapping against the Pipedrive custom field's options — those must be created in Pipedrive before the migration map is finalized.

Pipedrive has no native Equipment or Asset object. If the Equipment Tracking add-on is in use, we recommend creating a Pipedrive custom object (Equipment) linked to Organization via a custom relationship field, or storing key equipment attributes (serial number, model, last service date) as custom fields on the Organization record. We surface this decision in the migration plan before data lands.

Bella FSM Invoice records with line items (labor hours, parts) map to Pipedrive Products linked to the corresponding Deal. Each line item becomes a Product record; the quantity and price map to the Product's price. Note that Pipedrive has no native Invoice object — if invoice PDFs are required, the migration plan should include a note that invoices must be generated via Pipedrive's integration with QuickBooks or Xero.

Bella FSM file attachments (images, PDFs, documents) on Customer or Job records are downloaded and re-uploaded as Pipedrive Notes attached to the corresponding Person, Organization, or Deal. Pipedrive's file size limits apply (25MB per file for standard plans). We include inline images in Notes when the destination plan supports embedded attachments.

Bella FSM technicians and dispatchers (User records) map to Pipedrive users. Resolution is by email address — the Bella FSM user email is matched against existing Pipedrive user emails. Unmatched users are flagged before migration. If a Bella FSM technician has no Pipedrive user account, their records default to the migration initiator's Pipedrive user until the account is created.

Bella FSM's Advanced Inventory add-on tracks parts with SKU, description, cost, and quantity. These map to Pipedrive Products for line-item tracking on Deals. Inventory quantity on hand has no Pipedrive equivalent and is not migrated unless the service business also uses Pipedrive for supply quoting — we flag this as a post-migration decision point.