Migrate from Propeller CRM to Zoho CRM

Propeller Contacts map directly to Zoho CRM Contacts. We map full name, primary email address, phone number, and job title to Zoho's standard Contact fields. Company association resolves to a Zoho Account lookup via company name matching during import. Any Propeller Contacts without a matching company name are imported as standalone Contacts with a blank Account lookup and flagged for customer review. Multi-email-address records are handled by importing the primary as Email and secondary as a custom field.

Propeller Companies map to Zoho CRM Accounts. The company name becomes the Account Name, domain is stored in the Website field, and industry, address, and phone fields map to their Zoho equivalents where present in the export. Account is imported before Contacts so that the Account-Contact lookup relationship is satisfied at Contact insert time. Duplicate company records created by name-variant exports (e.g., 'Acme Corp' vs 'Acme Corporation') are flagged for manual dedup review.

Propeller Deals map to Zoho CRM Potentials (Zoho's Opportunity equivalent). Deal name maps to Potential Name, deal amount maps to Amount, and Propeller's pipeline stage name maps to the Stage field in Zoho's Sales Process. We assign a default Zoho Pipeline and Sales Process during import, with the customer's confirmation on which existing pipeline to use. Closed-Won and Closed-Lost dispositions from Propeller map to Zoho's Stage field if the customer has pre-configured matching stage values.

Propeller's customizable stage names map to Zoho CRM Stage values within the designated Pipeline and Sales Process. Stages with standard names (e.g., 'Qualified', 'Proposal Sent', 'Negotiation', 'Closed Won', 'Closed Lost') map directly. Stages with non-standard names ('verbal yes', 'awaiting finance', 'Pending Docs') require customer confirmation on placement in the Zoho stage sequence. We create a stage-mapping document during scoping that the customer's admin approves before import begins. Stage ordering is inferred from Propeller's stage sequence if preserved in the export.

Propeller user accounts mapped Contacts, Deals, and Companies to individual sales reps via email address. We extract every distinct owner email from the export archive and match against Zoho CRM User records by email. Users without a matching Zoho account are created as inactive placeholder Users so that the Owner lookup is satisfied on import. The customer's admin activates and assigns roles to placeholder Users post-migration. Any Contacts or Deals assigned to inactive owner emails that cannot be matched are flagged in a reconciliation report for manual reassignment.

Propeller Email Campaigns are imported as Zoho CRM Notes attached to the relevant Account or Contact where a send relationship exists in the export. The Note body contains campaign name, send date, and contact count. Campaigns are not recreated as live Zoho automation records because Zoho's email campaign functionality lives in a separate Zoho Campaigns module that has different configuration requirements. We document which Contacts received which campaign sends so the customer can build Zoho Campaigns lists manually if needed.

Propeller Email Templates with merge fields are imported into Zoho CRM's Email Templates module. Merge field names from Propeller are mapped to Zoho's corresponding merge field syntax (e.g., ${contact.first_name} in Propeller maps to {{Contact.First Name}} in Zoho). Template bodies transfer as-is where the merge field mapping is unambiguous. Templates with complex conditional logic or non-standard field references are flagged for manual rebuild in Zoho's template editor post-migration.

Propeller's Gmail extension tracked email opens, clicks, replies, and meeting events as live activity logs. These were not included in the standard shutdown data export package. There is no data to migrate for this object. We flag this gap during scoping and do not promise complete activity timeline migration. If the customer manually exported activity data during the active platform period, we can assess its importability on a case-by-case basis. This object carries a 'none' mapping type because the migration scope for it is zero records.

Call engagement records tracked inside Propeller's Gmail extension were not included in the standard shutdown export. Like email activity, call logs were a live-extension feature that did not persist to the archive. We flag this gap explicitly so that customers do not expect a historical call log timeline in Zoho CRM after migration. Zoho's native Call Log feature can be used to log new calls post-migration.

Propeller's deal stage history — which records the sequence of stage transitions and dates for each Deal — is partially available in the export if Propeller's data model included a stage history table. Where present, we import stage transitions as Zoho CRM Potential History entries via the API. Where the export contains only the current stage without history, we import the current stage only and flag the absence of historical transitions in the reconciliation report. The customer can enable Zoho's native audit trail for Potentials to capture future stage changes.

Propeller maintained the Contact-Company relationship by company name matching. We resolve this relationship during Zoho import by matching Contact.company_name from the export against Account.account_name, creating the Account-Contact lookup at import time. Contacts that reference a company name not found in the exported Companies table are flagged as potential orphans and held in a review queue. The customer confirms whether to create placeholder Account records for unmatched company names or to leave the Contact.AccountId field blank.