Migrate from Propeller CRM to Nutshell

Propeller Contacts map directly to Nutshell Person records. The standard fields (name, email, phone, address) use Nutshell's built-in Person fields. Propeller custom contact properties map to Nutshell custom Person fields, which we pre-create in Nutshell before import. If the Propeller export stores the contact's company as a text name rather than a foreign key, we resolve it against the Company export using string matching and write the result to the Nutshell Person's companyName or links attribute.

Propeller Company records map to Nutshell Company. Domain, address, industry, and employee count migrate to Nutshell Company fields. We deduplicate companies by name during scoping since Propeller's Gmail extension created loose associations by company name rather than a strict relational key. The Nutshell Company is created before any Person import so that the Person-Company relationship is satisfied on insert.

Propeller Deals map to Nutshell Lead records when the deal represents an unqualified or in-progress opportunity. We write the Propeller deal amount to Nutshell Lead's value field, the deal name to the subject or name field, and the Propeller pipeline stage to a custom Lead status field. Nutshell's Lead object is the closest structural match to Propeller's deal model; closed-won deals may alternatively map to Account-level opportunity records depending on the customer's preference.

Propeller allowed fully custom stage names with no enforced ordering. We map stage names to Nutshell Lead Status values and create custom status options where there is no close-enough default. Stages with non-standard names (e.g., 'verbal yes', 'awaiting finance') require customer confirmation on placement during scoping. The mapping is documented in a stage-reference sheet delivered with the migration scope.

Propeller Email Campaigns are imported as Nutshell Notes attached to the relevant Person or Lead record. The Note body contains the campaign name, associated contacts, and send date. This preserves the campaign record as historical reference but does not recreate the automated cadence or enrollment logic, which requires manual rebuild in Nutshell's automation layer.

Propeller email templates migrate to Nutshell email templates. We extract the template body and merge field names from the Propeller export and write them into Nutshell's template format. Merge field mapping follows Nutshell's standard variable syntax so that templates are functional upon import.

Propeller user accounts mapped contacts and deals to individual sales reps by email address. We map owner email addresses from Propeller to Nutshell User records. If a Propeller owner email has no corresponding Nutshell User, we create a placeholder User account and flag the assignment for the customer's admin to reassign after migration. This prevents deal and contact records from landing with an unresolved OwnerId.

Propeller's Gmail extension tracked opens, clicks, replies, and meeting events as live activity logs inside the platform, but these were not included in the standard data export produced at shutdown. We cannot reconstruct per-contact activity history from the archive. We disclose this gap explicitly during scoping and do not promise complete engagement migration. Campaign names and send dates are preserved as Notes; the per-contact response timeline is not recoverable.