CRM migration
Field-level mapping, validation, and rollback between Propeller CRM and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Propeller CRM
Source
monday CRM
Destination
Compatibility
6 of 8
objects map 1:1 between Propeller CRM and monday CRM.
Complexity
CModerate
Timeline
3-4 weeks
Overview
Propeller CRM shut down on December 15, 2019 with no live API and no support team. We work exclusively from whatever data archive Propeller produced during its final export window, which covers Contacts, Companies, Deals, Pipeline Stages, Email Campaigns, and Email Templates, but not per-contact activity timelines, live engagement logs, or email open/click history. Monday.com CRM uses a People and Companies entity model alongside flexible board and column structures, which means Deal records from Propeller can land as Monday CRM Deals or as board Items depending on the customer's chosen configuration. We resolve the destination object type during scoping, design the Monday schema before any import, and deliver a written inventory of automations and campaign workflows requiring rebuild in Monday or an external sales engagement tool. The absence of a native activity timeline in Monday.com CRM is disclosed upfront so customers do not expect contact-level engagement history to appear post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Propeller CRM object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Propeller CRM
Contact
monday CRM
Person (People entity)
1:1Propeller Contacts map to Monday CRM People records. We extract name, email address, phone, company association, owner assignment, and any custom contact fields from the Propeller archive. The company name on the Contact resolves to a Monday Companies record via the Propeller company relationship or by name matching. People deduplication uses email address as the unique key. Note that Propeller's per-contact Gmail engagement history (opens, clicks, replies) was tracked live by the Chrome extension and was not included in the shutdown export — this data does not exist in the archive and cannot be migrated.
Propeller CRM
Company
monday CRM
Company entity
1:1Propeller Company records map to Monday CRM Companies. The company name becomes the Company entity name, and the domain field maps from Propeller's website field. We resolve duplicate company names by matching on normalized company name strings before insert. Company records are created before any associated People records so that the relationship link is satisfied at insert time.
Propeller CRM
Deal
monday CRM
CRM Deal or board Item (customer-confirmed)
1:1Propeller Deals map to Monday CRM Deals if the customer is using Monday CRM natively, or to board Items in a dedicated Deals board if the customer prefers a flexible board configuration. The Propeller deal name, amount, stage assignment, owner, and associated contact all migrate. Deal amount maps to Monday's native currency amount field. We confirm the destination object type during scoping because it determines the pipeline view configuration.
Propeller CRM
Pipeline Stage
monday CRM
Pipeline View / Stage column
lossyPropeller pipeline stages map to Monday Pipeline view stages or board group columns. Propeller allowed fully custom stage names with no enforced ordering in the export, so we capture the original sequence from the archive's stage-position metadata and replicate it in Monday's pipeline view. Stages that have no clear Monday equivalent are flagged for customer confirmation on placement before production migration.
Propeller CRM
Email Campaign
monday CRM
Reference record (not migrated as functional campaign)
1:1Propeller email campaigns included campaign names, associated contact lists, send dates, and template references. Monday.com CRM does not have a native email campaign or sales sequence feature, so functional campaign records cannot be replicated in the destination. We import campaign metadata as a reference item in a dedicated Monday board with a link to the associated People records, so the customer retains a historical record of what was sent and to whom.
Propeller CRM
Email Template
monday CRM
Reference record or external storage
1:1Propeller email templates with merge field names are exported from the archive. Monday.com CRM does not have a native email template library as a standalone CRM feature. We deliver template bodies as a written reference document so the customer can recreate them in Monday's email integrations (Gmail, Outlook) or an external sales engagement tool if sequences are required.
Propeller CRM
User/Owner
monday CRM
Team member
1:1Propeller user accounts mapped contacts and deals to individual email addresses. We match Propeller owner emails to Monday team members by email during migration. If a Propeller user has since left and their account is inactive, their contact and deal assignments cannot log in to re-assign in Monday. We flag these as reconciliation items and create placeholder team member records in Monday for the customer's admin to reassign ownership post-migration.
Propeller CRM
Custom fields
monday CRM
Custom columns (text, number, date, dropdown, checkbox)
lossyPropeller custom contact and deal fields migrate as Monday board columns or CRM entity custom fields. Monday supports text, number, date, dropdown, checkbox, and formula column types. We map Propeller field data types to the equivalent Monday column type during schema design. Complex multi-select or hierarchical Propeller fields that have no Monday equivalent are flagged during scoping for customer decision on splitting or flattening.
| Propeller CRM | monday CRM | Compatibility | |
|---|---|---|---|
| Contact | Person (People entity)1:1 | Fully supported | |
| Company | Company entity1:1 | Fully supported | |
| Deal | CRM Deal or board Item (customer-confirmed)1:1 | Fully supported | |
| Pipeline Stage | Pipeline View / Stage columnlossy | Fully supported | |
| Email Campaign | Reference record (not migrated as functional campaign)1:1 | Fully supported | |
| Email Template | Reference record or external storage1:1 | Fully supported | |
| User/Owner | Team member1:1 | Fully supported | |
| Custom fields | Custom columns (text, number, date, dropdown, checkbox)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Propeller CRM gotchas
Platform shutdown — no active API or support
Activity history not included in standard export
Deal stage mapping requires manual review
Owner/user assignment requires remapping
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and archive verification
We confirm whether a Propeller CRM data archive exists from the shutdown window (pre-February 2020 export request). If no archive was produced, migration cannot proceed and we document this as a hard blocker. If an archive exists, we audit its contents — record counts for Contacts, Companies, Deals, Pipeline Stages, Email Campaigns, Email Templates, and Users — and compare against the customer's expectations. We also identify what the archive does not contain (activity history, engagement logs) and disclose those gaps explicitly before proceeding.
Schema design and pipeline stage mapping
We design the Monday.com CRM schema based on the archive's object inventory. This includes configuring Monday People and Companies entities, designing the Pipeline view with stages ordered to match Propeller's original sequence, mapping Propeller custom fields to Monday column types, and confirming whether Deals migrate as Monday CRM Deals or as board Items. The schema is validated in a Monday sandbox or staging workspace before any production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Monday sandbox workspace using production-like data volume from the archive. The customer's team lead reviews record counts, spot-checks 20-30 records against the Propeller archive, and confirms that contact-company relationships and deal-stage assignments are correct. Any field mapping corrections, stage placement decisions, or owner reconciliation items surface here and are resolved before production migration starts.
Owner reconciliation
We extract every distinct Propeller user email referenced on Contact, Company, and Deal records and match them against the Monday workspace team. Inactive Propeller users without a corresponding Monday team member are flagged as reconciliation items. The customer's Monday admin either reactivates the Propeller user's team membership or reassigns their records to an active team member before the production migration phase begins.
Production migration in dependency order
We run production migration in record-dependency sequence: Companies first (to anchor the entity model), then People (with company associations resolved), then Deals (with stage, owner, and contact lookups resolved), then Pipeline stage metadata and Email Template bodies. Each phase produces a row-count reconciliation report before the next phase begins. We flag any records that cannot be imported due to missing parent references or unmapped field types.
Cutover, validation, and automation handoff
We deliver a written migration summary including record counts by object type, a gap register listing every data category not migrated (activity history, engagement logs, campaigns, templates), and a template inventory document for manual rebuild. We open a one-week hypercare window to address reconciliation issues. We do not rebuild Propeller automations or campaigns in Monday as part of standard scope — those are documented for the customer's admin to rebuild using Monday's automation recipes or an external sales engagement tool.
Platform deep dives
Propeller CRM
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Propeller CRM and monday CRM.
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Propeller CRM: Not applicable — platform shut down December 15, 2019.
Data volume sensitivity
Propeller CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Propeller CRM to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Propeller CRM to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Propeller CRM
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.