Migrate from Propeller CRM to Freshsales

Propeller Contact records (name, email, phone, company association) map to Freshsales Contact. We use email address as the dedupe key during import. Propeller's Gmail extension auto-logged email interactions per contact, but these activity records were not included in the shutdown export — we note this gap but do not falsely promise complete activity migration. Contact records without a company association in Propeller import as standalone contacts; we flag these as potentially orphaned and present them for customer review.

Propeller Company records map to Freshsales Account. Propeller matched companies by company name string, which frequently created duplicate Account records when the same company appeared under slightly different name variations (e.g., 'Acme Corp' and 'Acme Corporation'). We run deduplication against the Propeller archive before import, matching on normalized company name and domain where present, and consolidate duplicates into single Freshsales Account records with all associated Contacts re-linked.

Propeller Deals map to Freshsales Deals. The Contact association from Propeller becomes the Primary Contact lookup in Freshsales. Deal amount, deal name, and stage assignment migrate directly. Owner assignment maps by resolving Propeller owner email to Freshsales User email; we create placeholder inactive User records in Freshsales for any owner email that has no corresponding Freshsales user account.

Propeller pipeline stages were fully customizable per team with no enforced ordering schema in the export. We map each Propeller stage name to the nearest Freshsales deal stage equivalent. Stages with no clear Freshsales equivalent (e.g., 'Pending Docs', 'verbal yes', 'awaiting finance') are flagged for customer confirmation on placement. Stage probability percentages are not stored in the Propeller export, so we assign Freshsales default probabilities unless the customer specifies a custom probability matrix.

Propeller Email Campaigns (campaign names, associated contacts, send dates, and template references) are imported as Freshsales Notes attached to the relevant Contacts. The campaign name becomes the Note title prefixed with [Propeller Campaign]. We do not re-create campaigns as Freshsales workflow sequences because Propeller campaign logic (trigger conditions, delays, A/B testing) was not exported in a structured format. We deliver a campaign inventory document listing each imported campaign name, contact count, and send date for the customer's admin to reference when rebuilding sequences in Freshsales.

Propeller email templates (template body text and merge field names) are mapped to Freshsales Email Templates. We preserve merge field names from Propeller in the template body and flag any template that uses Propeller-specific merge field syntax for manual review before activation in Freshsales.

Propeller user accounts mapped contacts and deals to individual sales reps by email address. We resolve each Propeller owner email against Freshsales User records by email match. Any owner email with no corresponding Freshsales user is held in a reconciliation queue — the customer's admin must provision the Freshsales user account before deal and contact owner assignments can be completed. Inactive Propeller users (departed employees) are created as inactive Freshsales users so that historical assignment data is preserved even if the person no longer has system access.

Propeller tracked opens, clicks, replies, and meeting scheduling as live activity logs inside its Gmail extension, but these were not included in the standard data export produced at shutdown. We explicitly exclude activity history from the migration scope and document this gap in the final migration report. Freshsales does not receive any engagement timeline data from Propeller's Gmail extension for the simple reason that Propeller did not export it. Customers who need engagement intelligence in Freshsales start fresh tracking from the day of cutover.