Migrate from Friday CRM to Pipedrive

Friday CRM Company records map directly to Pipedrive Organization. The Friday company name, domain, address, phone, and industry fields map to their Pipedrive Organization equivalents. We use the Friday company name as the dedupe key during import and create Organizations first so that the Organization ID is available when we import People. Any Friday custom fields defined on Company carry over with their type converted to Pipedrive field types: text fields remain text, number fields remain number, date fields become date pickers, and dropdowns from Friday become Pipedrive select fields.

Friday CRM Contact records map to Pipedrive People. Standard fields (name, email, phone, address, job title) migrate directly. We resolve the parent Organization by matching the Friday Contact's associated company name against the Friday Company records already mapped, and pass the corresponding Pipedrive Organization ID during People import. Any Friday custom fields defined on Contact are converted to Pipedrive People custom fields with equivalent types, and we flag radio select conversions that result in a Pipedrive select field before migration begins.

Friday CRM Deals map directly to Pipedrive Deals. Deal title, value, stage, expected close date, and notes migrate to their Pipedrive equivalents. We resolve the parent Organization and Person by matching Friday's deal associations against the already-migrated Organization and Person records using the Friday contact name and company name as lookup keys. Closed-won and closed-lost status maps directly to Pipedrive's status field, and any Friday custom Deal fields carry over with type conversion applied.

Friday CRM's kanban pipeline stages map to Pipedrive Pipeline stages by display name and ordering. We read the Friday stage names from the Deals export and create Pipedrive Pipeline stages with matching labels in the same ordinal position. If Friday has more pipeline stages than Pipedrive's default, we extend the pipeline configuration before deal import. Stage probabilities are set to Pipedrive defaults and can be adjusted by the customer post-migration if their probability model differs from the standard.

Friday CRM's nine custom field types require type conversion for Pipedrive compatibility. Radio select becomes Pipedrive select (single value). Multiple checkboxes split into separate boolean checkbox fields, one per original checkbox option, because Pipedrive does not natively support multi-checkbox. Single checkbox migrates directly to Pipedrive boolean. URL fields become Pipedrive varchar fields formatted as links. Date picker, text, number, multi-line text, and dropdown migrate without type change. We document the full type conversion map before migration and confirm with the customer which semantic conversions are acceptable.

Friday CRM Notes attached to Contacts and Deals map to Pipedrive Activities of type note. We extract note body text, creation timestamp, and the associated Contact or Deal. The Pipedrive Activity is linked to the migrated Person and Organization using the resolved lookup IDs. If the Friday export includes notes without a timestamp, we use the import batch timestamp. Note ordering in Pipedrive's activity timeline is preserved by the Activity date field.

Friday CRM Tags applied to Contacts and Deals migrate as comma-separated string values mapped to Pipedrive's label functionality. We parse and deduplicate the tag list from the Friday export, create Pipedrive labels matching those values, and apply them to the corresponding migrated Person and Deal records. If the customer uses tags for segmentation or classification, we recommend Pipedrive's custom Activity Content Type as the equivalent for grouping activities.

Friday CRM does not expose file attachments through its documented CSV export or public API. We flag this limitation at the start of the engagement and recommend the customer use Friday CRM's UI to download any critical attachments before migration. We do not migrate attachments as data because there is no reliable programmatic path. Any attachment references in the Friday export are noted as pending manual handoff to the customer.

Friday CRM owner records (linked to Contacts, Companies, and Deals) map to Pipedrive Users. We match by email address. Any Friday Owner without a matching Pipedrive User goes into a reconciliation queue for the customer's admin to provision before deal import. Pipedrive requires an active User to own records, so Owner mapping is a prerequisite step that gates the main migration run.

Friday CRM's native integrations with Gmail, G Suite, Mailchimp, and RingCentral store OAuth tokens and connection credentials that are not part of the exportable data. We do not migrate integration settings. Every connected integration must be reconfigured from scratch in Pipedrive post-migration, including re-authenticating OAuth connections and updating any rules that depend on those integrations. We provide a written inventory of each Friday integration that requires rebuild in Pipedrive.