Migrate from Firmao CRM to Pipedrive

Firmao Contacts map directly to Pipedrive People. Standard fields (name, email, phone, address, tags) migrate directly. Firmao stores tags as a comma-separated string on the contact record; we split these into individual Pipedrive label entries during import. Custom field dot-notation keys (customFields.customN) map to Pipedrive custom fields of equivalent type (string, number, date, or picklist). Custom field labels are confirmed against the customer's Firmao import documentation during scoping because the API response does not expose human-readable labels. Companies must be imported before Contacts to satisfy Pipedrive's person.primaryEmail requirement and maintain organization linkage.

Firmao Companies map to Pipedrive Organizations. The companyName becomes the organization name, and address fields map to the address property. Firmao's multi-address capability (subsidiaries, billing vs shipping) collapses into a single Pipedrive address; additional addresses are logged as activity notes for manual follow-up. Organization is imported first, before any Person records, to enable the primaryEmail-to-organization linkage Pipedrive requires.

Firmao Deals map to Pipedrive Deals. This object is gated behind Firmao's Professional tier — we confirm the customer's active plan during scoping and flag the upgrade requirement before migration begins if the account is on Standard. The dealName maps to Pipedrive's title, dealValue to weighted_value, and stage names from Firmao are matched against the Pipedrive pipeline stages the customer configures. Pipeline configuration in Pipedrive is set up before Deal import so that stage assignments resolve at import time. Owner assignment maps via email matching against the User object.

Firmao Tasks map to Pipedrive Activities with type = Task. The task title becomes the activity subject, dueDate maps to dueDate, and status maps to Pipedrive's done flag (0 = open, 1 = completed). Firmao stores the parent reference via a subClass/subId envelope (dealId or contactId) rather than a named foreign key — we resolve this using the name or value matching established during the Company and Deal import phases. Tasks are imported after Deals to ensure dealId resolution succeeds.

Firmao Products map to Pipedrive Products. The productName becomes the Pipedrive name field, and pricing fields (basePrice, netPriceInStore) map to the standard price. Stock quantities per warehouse require extraction from the subClass=warehouse envelope in Firmao's product modification log before import, because warehouse is not a top-level Firmao object. We extract each subClass=warehouse subId entry (with its netPriceInStore and currentStoreState values) and create corresponding Pipedrive warehouse location records, then link them to the product. This envelope-flattening step adds a transformation phase to the product migration.

Firmao Users map to Pipedrive Users by email match. We export the user list from Firmao during discovery, match each user email against the destination Pipedrive org, and provision any missing Pipedrive users before record migration begins. Active versus inactive status maps directly. Owner assignments on Deals and Tasks resolve through the User mapping.

Firmao custom fields (customFields.custom5 style) are defined in the Professional tier and above. We enumerate which custom fields are populated by retrieving a sample record via GET first, then cross-reference against the customer's Firmao import documentation for human-readable labels. Each populated custom field is created as a typed Pipedrive custom field (text, numeric, date, or picklist) before Contact, Company, or Deal import begins. Empty custom fields from the sample export are flagged as potentially deleted and excluded from migration.

Firmao stores tags as a comma-separated string property on the contact or company record. There is no dedicated /tags endpoint. We split the comma-separated value into individual label entries and assign them to the corresponding Pipedrive Person or Organization record during import. Label names are normalized (trimmed, lowercased) to prevent duplicates from inconsistent casing.

Firmao Invoices (including VAT invoices, bills, receipts, and accounting notes) are not migrated because Pipedrive does not have an invoice object as standard CRM scope. Invoice records are flagged in the scoping report with a recommendation to use a dedicated accounting tool post-migration. Line item data and payment status are preserved in a CSV export we deliver alongside the migration for the customer's finance team to reference.

Firmao Projects (with Gantt and Kanban views available on Professional and above) do not have a direct Pipedrive equivalent. Pipedrive's focus on sales pipeline does not include project management functionality. We deliver project names, descriptions, and task associations in a structured CSV export for the customer's project management team to adopt in a dedicated tool. Visual layout data (Gantt bar positions, Kanban column configuration) cannot be transferred.