Migrate your Propeller CRM data

Contacts were the primary object in Propeller, stored with name, email, phone, and company association. The Gmail extension auto-logged all email interactions per contact. We preserve contact records and their associated email activity logs during export reconstruction, but destination mapping must account for the flattened activity log format Propeller used.

Companies were stored as separate records linked to Contacts. The relationship was maintained by company name matching in Propeller's schema. We resolve duplicate company records during import scoping and merge where the destination CRM uses a single Account/Company object.

Deals were the core pipeline object in Propeller, associated with a Contact and assigned to a Pipeline Stage. Deal amounts, names, and stage history were tracked. We preserve deal stage history as of the last export date, but open/active deal status may be stale since the platform shut down in 2019.

Pipeline stages were customizable per team but used a fixed stage-order schema. Destination CRMs often use different stage naming conventions. We map stage names to destination equivalents during import and flag any stage that has no clear equivalent in the target system.

Propeller supported automated email campaigns with template support. Campaign names, associated contacts, and send dates were tracked. We import campaign records as historical reference notes in the destination CRM since most CRMs do not have a native Campaign object at this tier.

Users created reusable email templates with merge fields. Template bodies and merge field names are exported from the archive. We map template content to email template objects in the destination CRM where supported, or preserve as plain-text reference records otherwise.

Activity logs (opens, clicks, replies, meeting scheduling) were tracked live inside Propeller's Gmail extension but were not exposed in the standard data export mechanism. We cannot reconstruct per-contact activity timelines from the shutdown archive. We flag this gap upfront and advise customers to capture any critical activity context before the export window closed.

User accounts mapped contacts and deals to individual sales reps. Owner assignment data is preserved in the export archive. We map owner email addresses to user accounts in the destination CRM, creating new users where no match exists.