Migrate from Bella FSM to Odoo CRM

Bella Customer records map directly to Odoo res.partner. Bella's customer type (residential/commercial) becomes a custom selection field on res.partner since Odoo uses the same object for contacts and companies. Primary address, phone, and email map as-is. Multi-location customers require multiple partner records with parent_id linking.

Bella Vendor records map to Odoo res.partner using the vendor flag to set supplier_rank. The supplier checkbox on res.partner mirrors Bella's vendor concept precisely. Vendor address and contact information transfers directly without transformation. Vendor-specific metadata like tax documentation status, W-9 completion, or insurance certificates require a custom Boolean or selection field on res.partner created via Odoo Studio to preserve this information during migration.

Bella Job records become Odoo project.project entries. Each job maps to a project so that related work orders attach as tasks. Job status (Open, Closed, On Hold) maps to project.project stage values. The Bella job description transfers to project.project description field. Multiple jobs per customer are supported by Odoo's project-per-customer model.

Bella Work Order records map to project.task within the corresponding project.project. Work order status (Pending, In Progress, Completed, Invoiced) maps to Odoo task stage values. Original work order number becomes task name or a custom reference field. Checklist items transfer as task checklist lines if using Odoo Project Enterprise.

Bella work order line items (labor, parts, travel) merge into Odoo sale.order.line entries on the linked sale order. The work order's total labor hours map to a custom field on the sale order line since Odoo line items track product quantity and price rather than time entries natively. Multiple line types require product creation or a custom model.

Bella Equipment records map to Odoo maintenance.equipment. Equipment serial number, model, and make transfer to the corresponding equipment fields. Customer link (which customer owns the equipment) maps to equipment.partner_id. Equipment maintenance history from Bella transfers as maintenance.request records linked to the equipment.

Bella inventory items become Odoo product.product records. Part number, description, cost, and price map to product.product fields. Odoo stock.quant tracks on-hand quantity per location. If Bella tracks inventory by warehouse or truck, Odoo's multi-location stock model handles this via stock.location records.

Bella's custom data fields on the Customer page (text, checkbox, dropdown) require Odoo custom field creation via Odoo Studio or a custom module. Each custom field is added to res.partner with the matching field type. Selection options for dropdown fields map as is. Field labels are preserved for reference.

Bella's custom data fields on the Job page migrate as custom fields on project.task in Odoo. Text fields, checkboxes, and dropdown selections all transfer. The custom field's section grouping in Bella does not transfer — fields appear individually on the task form in Odoo.

Bella Estimates become Odoo sale.order records in draft/quotation state. Line items map to sale.order.line. Estimate status (Draft, Sent, Approved, Declined) maps to sale.order state. If Bella's estimate includes custom pricing per job, the lines transfer as-is with the custom price override flag.

Bella Invoices map to Odoo account.move records with type='out_invoice'. Invoice line items map to invoice lines. Payment status (Paid, Unpaid, Overdue) maps to Odoo's payment_state field. Bella's payment terms and credit card processing data require custom fields since Odoo handles payments separately via account.payment.

Bella file attachments on work orders, customers, and equipment migrate as Odoo ir.attachment records linked to the corresponding record using the res_model and res_id fields. Files re-upload to Odoo's filestore with the original filename preserved. Inline images embedded within notes or description fields are detected, extracted, and stored as separate attachment records with the correct mimetype classification for proper rendering in Odoo's document viewer.

Bella recurring service visits translate to Odoo project.task records configured with a recurrence rule using Odoo's native task recurrence feature. If the Odoo Subscriptions application is installed and active, recurring service contracts alternatively map to sale.subscription for subscription-based billing scenarios. The recurring frequency (daily, weekly, monthly) and interval parameters transfer as subscription recurrence configuration, preserving the original service schedule cadence from Bella.

Bella user accounts including administrator and standard technician roles map to Odoo res.users records using email address as the primary matching identifier. Bella role permissions and team assignments do not transfer automatically because Odoo's record rules, access groups, and permission profiles operate under a different security model that requires destination-side configuration. Any Bella user account without a corresponding Odoo user email is flagged in the migration report and assigned to a designated fallback Odoo administrator account pending user creation.