Migrate from Firmao CRM to Nutshell

Firmao Contact records map to Nutshell Person. Standard fields (name, email, phone, address) map directly. Custom contact fields using Firmao dot-notation (customFields.customN) migrate to Nutshell custom fields on Person, but only after Nutshell custom fields are pre-created in Settings with matching data types. Tags stored as comma-separated values on the Firmao contact record map to Nutshell Person tags. We use email as the dedupe key during import and flag any duplicate emails for customer review before insert.

Firmao Company records map directly to Nutshell Company. Company name is the primary field and is used as the dedupe key. We import Companies first so that Person-Company associations are resolved at the time of Person insert. Firmao's multi-currency support maps to Nutshell's currency field on Company if the destination Nutshell account uses multi-currency. Address, website, industry, and employee count fields migrate directly where populated.

Firmao Deals map to Nutshell Deals. This mapping is gated by the customer's active Firmao plan tier—Deals are accessible only on Professional and above. If the customer is on a Standard plan during scoping, we confirm this before migration and ask them to upgrade or acknowledge the exclusion. Deal name, value, stage, owner, and expected close date map directly. Nutshell's Deal record type does not support a visual pipeline layout migration; the pipeline configuration is documented for the customer admin to configure post-migration.

Firmao Tasks map to Nutshell Tasks. Task name, due date, status, and priority migrate directly. Task associations to Contacts or Deals in Firmao use the subClass/subId envelope structure—since Firmao does not expose internal IDs in the GET response, we use contact name matching and deal name matching to resolve associations. We import Deals before Tasks to satisfy the lookup resolution order and flag any Tasks with unresolved associations for customer review.

Firmao Products map to Nutshell Products if the destination Nutshell plan supports the Products feature. Product name, SKU, and base price migrate directly. Per-warehouse stock levels in Firmao are stored as subClass=warehouse entries on the Product object and are not a standalone entity; we extract netPriceInStore and currentStoreState per subId and flag warehouse-level inventory as a manual export for the customer because Nutshell Products does not support warehouse-level stock tracking natively.

Firmao Users export via /svc/v1/user and include name, email, and role. Owner assignments on Deals and Tasks resolve by email match against Nutshell's user list. We extract all distinct owner emails and confirm that corresponding Nutshell users exist or are provisioned before migration begins. Any Firmao owner without a matching Nutshell user is placed in a reconciliation queue.

Firmao Invoices (VAT invoices, bills, receipts, accounting notes) have no equivalent object in Nutshell, which is a CRM without invoicing capabilities. We export the invoice header and line item structure as a structured CSV and flag the file for the customer's accounting team to import into their chosen accounting platform (QuickBooks, Xero, FreshBooks, or equivalent). Invoice associations to Contacts and Deals in Firmao are preserved in the exported CSV for reference.

Warehouse is a subClass of the Product object in Firmao rather than a top-level entity. Net price per store and current stock state are extracted as subId entries per product during export, but Nutshell Products does not support warehouse-level inventory. We flag the warehouse-stock export as a manual handoff and note the product-to-warehouse mapping in the export manifest for the customer's inventory management team.

Firmao Projects (available on Professional and above) include name, description, dates, and task associations. Gantt and Kanban visual layout data does not migrate. We export project metadata as a CSV and flag the records for the customer's project management team to migrate to a dedicated PM tool (Asana, Monday.com, Jira, or equivalent) if required. Project-task associations are preserved as a flat list in the export for reference mapping.

Firmao custom fields (available on Professional and above) use dot-notation keys (customFields.custom5, customFields.custom12) that are not self-documenting in the API response. We retrieve a sample record via GET first to enumerate which custom fields are populated, then cross-reference with the import documentation the customer provides. Fields with no values in the sample are flagged as potentially deleted and excluded. Before migration, Nutshell custom fields must be created in Settings with the appropriate data type (text, number, date, picklist, checkbox); we provide a custom field creation checklist as part of the pre-migration deliverable.