Migrate from Propeller CRM to Salesforce Sales Cloud

Propeller Contacts with no deal association or early-stage engagement map to Salesforce Lead. Propeller Contacts with an active or closed Deal and a linked Company map to Salesforce Contact attached to the mapped Account. We apply the split rule during import scoping, with the original Propeller contact record preserved in a custom field for audit. If the Propeller export lacks a deal association for a contact, we route it to Lead rather than create a Contact with no parent Account, which would leave it orphaned.

Propeller Company records map to Salesforce Account. The Company name becomes Account Name and is used as the dedupe key during import. If multiple Propeller Company records share the same name (a common data quality issue in lightweight CRMs), we deduplicate and link all associated contacts to the surviving Account. Account must be imported before Contact to satisfy the AccountId lookup.

Propeller Deals map to Salesforce Opportunity. The Deal amount, name, and close date migrate to Amount, Name, and CloseDate. Deal owner email resolves to Salesforce OwnerId via the User mapping. Closed-Lost and Closed-Won status migrate to Opportunity StageName. We import Opportunities after Accounts and Contacts so that AccountId and PrimaryContactId lookups are satisfied at insert time.

Propeller allowed fully custom pipeline stage names with no enforced ordering logic. We map each Propeller stage name to a Salesforce Opportunity StageName value, with stage probability percentages applied per the customer's confirmed placement. Stages that have no clear Salesforce equivalent (e.g., 'verbal yes', 'awaiting finance') are flagged during scoping for manual customer confirmation before the Sales Process is deployed to Sandbox.

Propeller Email Campaigns map to Salesforce Campaign records. Campaign name, associated contact list, send date, and campaign status migrate as Campaign fields. Campaign member status for each associated Contact migrates to CampaignMember. We do not migrate campaign email body content; Salesforce Campaign does not store rich HTML body by default and Propeller campaign templates are best treated as source documents for a Salesforce Marketing Cloud implementation.

Propeller email templates with merge fields migrate to Salesforce EmailTemplate. Template subject, body (rich text), and merge field API names transfer as Salesforce template fields. Merge field naming conventions differ between platforms; we translate Propeller merge field syntax to Salesforce merge field syntax during the transform phase. We do not migrate template-associated images or attachments as Salesforce EmailTemplate stores body content inline only.

Propeller user accounts are tied to individual email addresses and stored on every Contact, Company, and Deal record as the owner reference. We extract all distinct owner emails from the export and attempt to match them to Salesforce User records by email. Any owner email with no matching Salesforce User goes to a reconciliation queue — the customer's admin must provision a corresponding User (active or inactive depending on whether the original Propeller user is still with the company) before record import can complete.

Propeller's Gmail extension tracked per-contact activity logs — opens, clicks, replies, and meeting events — as live data inside the extension interface. These activity records were NOT included in the standard shutdown export package. We cannot reconstruct or rehydrate this data. We flag this gap explicitly during scoping and do not promise complete activity migration. Any existing activity data in the export archive (e.g., notes or tasks explicitly created as records) is migrated; extension-tracked interactions are not.

If the Propeller export includes explicit note records (user-created notes attached to contacts or deals as data records), these migrate to Salesforce Note objects linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Propeller notes created via the Gmail extension but not stored as database records are not included in the export.

Propeller did not support custom fields or custom objects. Any customer-specific field labels or data captured in text fields (e.g., deal custom data stored in a free-text Deal Name or Notes field) is migrated as raw text into a Salesforce custom field that we provision during schema design. We cannot retroactively type these fields; the customer reviews and reclassifies them post-migration.

File attachments linked to Propeller contacts, companies, or deals are included in the export archive if Propeller stored them as records. Attachments are migrated as Salesforce ContentVersion and ContentDocument records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Attachments stored only inside the Gmail extension (e.g., email attachments linked to Propeller-tracked threads) are not included in the export.

Propeller email campaigns and automated follow-up sequences cannot migrate as code because the destination platform uses a different automation model (Salesforce Flow with record-triggered, scheduled, and screen flow variants). We do not rebuild these. We deliver a written inventory of every Propeller email campaign, sequence step, and automation trigger with a recommended Salesforce Flow or Sales Engagement equivalent for the customer's admin to rebuild post-migration.