Migrate from Firmao CRM to Freshsales

Firmao Contact records map directly to Freshsales Contact. The contact firstName, lastName, phone, email, and address fields map to typed Freshsales Contact fields. Custom contact fields (customFields.customN) migrate to Freshsales custom_contact_fields using the dot-notation key as the source label; we cross-reference with the customer's import documentation to confirm which keys carry active data. Tags stored as comma-separated values on the contact record migrate to Freshsales Contact_tags multi-select field.

Firmao Company records map to Freshsales Account. The companyName becomes the Account name; address, city, country, and industry fields map directly. Firmao companyId is preserved in a custom field for reconciliation. Account is created before Contact import so that the parent relationship is satisfied at Contact insert time. If the destination Freshsales org uses Organizations rather than Accounts, we rename the object during import.

Firmao Deals (Professional+ only) map to Freshsales Deals. The dealName, dealValue, currency, and owner assignment migrate directly. Firmao's pipeline stage is a property on the Deal record, not a separate object; we map this to Freshsales Deal stage values that we configure as a named Pipeline before migration. If the source account is on Firmao Standard, we flag that Deals are not accessible via API and note the customer must upgrade before Deals can be included in the migration scope.

Firmao Tasks map to Freshsales Task records with title, due_date, priority, status, and assignee preserved. The contact or deal association uses Firmao's subClass/subId envelope for object relationships; we resolve the subClass type (Contact or Deal) and subId to the corresponding Freshsales record ID at migration time. Tasks without a resolvable parent association are imported as standalone tasks and flagged for manual review.

Firmao Products map to Freshsales Product records with name, sku, description, and base pricing preserved. The base product fields migrate cleanly. Per-warehouse variants (Firmao subClass=warehouse entries with netPriceInStore and currentStoreState) require special handling: we extract each warehouse variant as a separate Freshsales product with the warehouse name appended to the product name and the variant-specific pricing as the standard price, then flag that multi-warehouse stock tracking cannot be natively represented in Freshsales and should be managed via a third-party inventory integration post-migration.

Firmao Projects (Professional+ only) with Gantt and Kanban views do not have a direct Freshsales equivalent. We extract the project name, description, start and end dates, and task associations. We create a Freshsales Contact or Deal record for the project and attach all project tasks as Freshsales Task records tagged with the project name in a custom field. Visual layout data (Gantt bar positions, Kanban column configuration) does not migrate; we document the layout requirements in the handoff inventory for the customer's admin to configure in Freshsales Tasks or a project management tool.

Firmao Invoices include VAT invoice, bill, receipt, and accounting note types with line items, tax codes, and payment status. Freshsales does not have a native accounting-grade invoice object. We map invoice headers to Freshsales Quotes and invoice line items to Quote Items, preserving product references, quantities, unit prices, and tax codes. Payment status and billing history do not migrate; we flag this for the customer's finance team to handle in their accounting system of record. Invoice PDFs cannot be extracted via API and must be manually exported from Firmao's cloud vault.

Firmao Users (name, email, role) map to Freshsales User records. We resolve owners by email match against the Freshsales destination's user list. Any Firmao User without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before Deal and Task import resumes. Owner assignments on Deals and Tasks resolve through the user mapping.

Firmao custom fields (Professional+ only) use dot-notation keys like customFields.custom5 with string values. We enumerate which keys are populated by querying a sample of contact, company, and deal records before migration, then create matching custom fields in Freshsales with human-readable names mapped from the customer's import documentation. Empty keys (no values in the sample) are flagged as potentially deleted and excluded. Freshsales custom fields are typed (text, number, date, picklist, checkbox) and we infer the appropriate type from the source data format.

Firmao pipeline stages are a property on the Deal object, not a standalone API object, and vary by organization. We export deal records including the current stage value, then configure Freshsales Deal Stages to match the customer's active stages before migration. Stage order, probability, and open/closed status are preserved. The customer confirms the stage mapping during scoping.