Migrate from Getfly CRM to Pipedrive

Getfly Accounts containing individual contacts map to Pipedrive Person records with name, email, phone, and address fields. Getfly Accounts containing company records map to Pipedrive Organization records. When a Getfly Account holds both a company and its contacts, we split into one Organization and multiple Person records linked to that Organization. Custom fields on Getfly Accounts become custom fields on the corresponding Pipedrive Person or Organization object. We preserve any Getfly Account ID as a custom field for reconciliation.

Getfly's configurable deal stages map to Pipedrive Pipeline Stages. Stage names, display order, and probability percentages transfer from Getfly to Pipedrive. Each Getfly pipeline becomes a separate Pipedrive Pipeline, and stage probabilities are entered in the Pipedrive Pipeline settings. Customer-specific stage naming conventions are preserved to avoid confusing the sales team post-migration.

Getfly Deals map directly to Pipedrive Deals with title, value, stage, owner, expected close date, and linked Account preserved. The Getfly dealstage property maps to a Pipedrive Pipeline Stage by name match. Closed-Lost and Closed-Won outcomes transfer as stage transitions. Deals without an associated Account link to the corresponding Pipedrive Organization or Person at migration time using the Getfly Account ID stored as a custom field.

Getfly Products with pricing, SKU, and custom fields map to Pipedrive Products. Product name, price, and SKU migrate directly. Any Getfly detail_custom_fields nested object is flattened into Pipedrive custom fields on the Product object. Products are created before Deal migration so that Line Items can reference them during import.

Getfly Tasks map to Pipedrive Activity records with type=Task, subject, due date, status, and owner preserved. Task assignment resolves by matching Getfly owner email to Pipedrive User email. Completed status maps directly; open tasks remain open in Pipedrive with the original due date.

Getfly PABX call records map to Pipedrive Call activities with call direction, duration, and disposition preserved in custom fields. Call recording URLs are downloaded at export time and re-uploaded to Pipedrive's file management linked to the Call activity. This step requires explicit scoping: if the customer replaces their PABX alongside the CRM, recording continuity must be confirmed before migration. Pipedrive has no native call recording storage, so re-hosted files are the replacement.

Getfly meeting records map to Pipedrive Activity records with type=Meeting, subject, date and time, location, and linked Account preserved. Attendee lists migrate as a custom field or note attachment if the meeting record includes participant details.

Getfly Users (owners) map to Pipedrive Users by email match. Active Getfly users map to active Pipedrive users; inactive users map to inactive Pipedrive users. Any Getfly user without a matching Pipedrive User is held in a reconciliation queue for the customer to provision before record import resumes. Role and permission information from Getfly is documented for manual rebuild in Pipedrive's access control settings.

Getfly file attachments linked to Accounts or Products are downloaded to local storage during export, then uploaded to Pipedrive's file management linked to the corresponding Person, Organization, Deal, or Activity. Original filenames are preserved. Pipedrive's file size limit is 150 MB per file; files exceeding this threshold are flagged for the customer to host externally and link.

Getfly marketing campaigns with name, start/end dates, and linked accounts migrate as Pipedrive Activity records of type=Note containing campaign metadata. Pipedrive has no native campaign membership object, so campaign-to-account relationships are preserved as tagged labels on the linked Person or Organization. The customer may alternatively use Pipedrive's Labels feature for campaign segmentation post-migration.

Getfly Workflow Rules are not exportable via API. We deliver a written inventory of every active Getfly automation with its trigger, conditions, actions, and recommended Pipedrive Workflow equivalent. The customer's admin rebuilds the automations in Pipedrive Workflows post-migration. This inventory is completed during the discovery phase using a workflow audit questionnaire that the customer fills out before migration begins.