Migrate from Propeller CRM to Microsoft Dynamics 365 Sales

Propeller Contacts map to Dynamics 365 Lead by default, preserving name, email, phone, and the original company association. We create a custom field original_company__c to carry the Propeller company name when no matching Dynamics 365 Account exists. If the Contact has an associated Deal in Propeller, we flag it for Contact status post-conversion. Lifecycle stage properties from Propeller migrate to a custom Lead field original_lifecycle_stage__c for reporting continuity.

Propeller Company records map to Dynamics 365 Account. Company name is the primary Account name field. We deduplicate by exact name match during import scoping; near-duplicates (differing by punctuation or capitalization) are flagged for customer confirmation. Account is loaded before Contact so that the Parent Account lookup is satisfied at insert time.

Propeller Deals map to Dynamics 365 Opportunity with deal name, amount, expected close date, and owner preserved. The Propeller pipeline stage assignment maps to a Microsoft Dynamics 365 Sales Process stage value that we configure before migration. If the Propeller deal references a Contact, we attach that Contact to the Opportunity via ContactId after the Contact-to-Lead conversion is confirmed.

Propeller pipeline stage names migrate as Dynamics 365 stage values under a Sales Process that we configure to match Propeller's stage order. Stage probability percentages map from Propeller where available. Stages with non-standard names (e.g., 'verbal yes', 'awaiting finance') are flagged for customer confirmation on placement in the Dynamics 365 stage sequence before migration begins.

Propeller Email Campaigns migrate as Dynamics 365 Campaign records holding the campaign name, send date, and contact count. Campaign notes include send volume and revenue attribution where the Propeller export preserved those metrics. We do not recreate campaign delivery records, open/click data, or individual email send history because that data was not included in the Propeller shutdown export.

Propeller email templates migrate to Dynamics 365 Email Template records. Template bodies and merge field names transfer as-is where the Propeller archive preserves template content. Merge field syntax differs between platforms; we document the original Propeller field names alongside the Dynamics 365 equivalent as a reference for the admin team during template rebuild verification.

Propeller owner assignments (user email per record) map to Dynamics 365 User by email lookup. If a Propeller owner email has no matching Dynamics 365 User, we create an inactive placeholder User record so that OwnerId references do not break during import. The customer confirms which placeholder Users should be activated, reassigned, or left inactive after migration.

Activity history — email opens, link clicks, replies, meeting scheduling events, and call logs — was tracked inside Propeller's Gmail extension but was not included in the standard shutdown data export. We cannot reconstruct this data from the archive. We explicitly flag this gap during scoping and do not promise a full activity timeline migration. Any engagement records present in the archive migrate as Note records attached to the relevant Contact or Deal.

Propeller's field schema was limited to standard types (text, number, date, checkbox, dropdown). Any extended custom field data from the export maps to Dynamics 365 custom attributes created during the schema design phase. Fields with no direct Dynamics 365 equivalent are flagged for customer decision: create a custom field, map to an existing standard field, or drop the data.