Migrate from Propeller CRM to Pipedrive

Propeller Contact records (name, email, phone, company association) map directly to Pipedrive Person. The Gmail extension auto-logged email interactions per contact in Propeller, but those interaction logs were not included in the shutdown export and cannot be reconstructed. We preserve contact name, email address, phone number, and company link. Propeller's company association is resolved via company name matching against the Organizations import.

Propeller Company records map to Pipedrive Organization. The Propeller schema maintained the company-contact relationship by company name lookup, which can produce duplicate Organizations if the same company appears under slightly different names (e.g., 'Acme Corp' and 'Acme Corporation'). We run a fuzzy name-matching pass during scoping and consolidate duplicates before import to avoid creating duplicate Organization records in Pipedrive.

Propeller Deals map to Pipedrive Deals with deal name, amount, associated contact, assigned owner, and pipeline stage preserved. The deal-contact linkage is resolved by matching the Propeller contact reference to the Pipedrive Person record created during the Persons phase. Deal amount and currency map to Pipedrive's monetary fields.

Propeller allowed fully custom pipeline stage names with no enforced ordering logic in the export. Pipedrive stages have a defined sequence and probability percentage. We map Propeller stage names to Pipedrive stage equivalents during import scoping, but stages with non-standard names (e.g., 'Pending Docs', 'verbal yes', 'awaiting finance') have no automatic Pipedrive match. These are flagged for customer confirmation before import, and the customer selects placement in the Pipedrive pipeline sequence.

Propeller email campaign records (campaign name, associated contacts, send dates) have no direct Pipedrive equivalent at the object level. Pipedrive's Campaigns add-on is a separate billing layer with a different data model. We import campaign records as historical Note entities attached to the relevant Person or Deal records, preserving campaign name and send date as reference content.

Propeller email templates with merge fields export as template body text. We map template content to Pipedrive Email Templates using the template name as identifier and the merge field names as template variable placeholders. Note that Pipedrive Email Templates use a different merge field syntax from Propeller, so the customer's admin should verify variable substitution after migration.

Propeller user accounts were tied to individual email addresses and appear as deal and contact owner assignments in the export. We map owner email addresses to Pipedrive User records by email match. If a team member has since left and their Pipedrive account has not been provisioned, their deal and contact assignments are flagged in a reconciliation queue. The customer provisions the missing Pipedrive user before records are assigned to them.

Activity logs tracked by Propeller's Gmail extension — email opens, clicks, replies, and meeting events — were not included in the standard shutdown data export. This is a known Propeller export gap, not a mapping limitation. We flag this absence during scoping and do not promise complete activity timeline migration. No post-migration reconstruction is possible from the Propeller side.

Propeller did not support custom objects but did allow custom fields on Contacts, Companies, and Deals. Any custom field values present in the export are mapped to Pipedrive custom fields, which we create in the destination account before import. Custom field type mapping follows Pipedrive's supported field types (text, numeric, date, picklist, address, and phone). Multi-select or checkbox fields from Propeller map to Pipedrive multi-select picklist where supported.

Propeller tracked which contacts were part of which email campaigns. We map this to a Person-tagged note in Pipedrive listing the campaign names associated with each Person, or to Pipedrive Activity notes appended to the Person record. This preserves the record of campaign participation without creating Pipedrive Campaign objects, which require the Campaigns add-on and a different data structure.