CRM migration

Migrate from PropFlo to Nutshell

Field-level mapping, validation, and rollback between PropFlo and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

PropFlo logo

PropFlo

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between PropFlo and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

PropFlo organizes real estate sales around leads, contacts, companies, deals, and real estate-specific objects like AOS (Agreement of Sale) and demand notes. Nutshell uses a simpler model: People (contacts), Companies, and Leads as separate entities, with a single Activity history per record and custom fields scoped per object type. FlitStack AI extracts PropFlo data via API — contacts, companies, deal records, activity timestamps, and custom field values — and maps them into Nutshell's schema. Real estate-specific metadata (property units, inventory status, payment milestones) migrates as Nutshell custom fields on the Company or Person record, since Nutshell has no native real estate object equivalent. Your workflows, approval flows, and AOS generation templates must be rebuilt in Nutshell's automation tools; we export the workflow definitions as a reference document. The migration runs in a delta-pickup window so any PropFlo changes during cutover land in Nutshell before go-live. Our migration process includes a detailed pre-audit of PropFlo custom objects, owner email resolution, and a test run to validate field mapping before the final data load.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

PropFlo logo

PropFlo

What's pushing teams away

  • Teams outgrow the platform when scaling to multiple large projects with complex inventory across hundreds of units, requiring more sophisticated ERP-level controls.
  • Limited integration ecosystem compared to established CRMs — teams needing deep third-party accounting or marketing tool connections may find PropFlo's options constrained.
  • Some users note that as the product rapidly releases new features, the learning curve for staying current with updates can create temporary friction.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How PropFlo objects map to Nutshell

Each row shows how a PropFlo object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

PropFlo

Lead / Contact

maps to

Nutshell

Nutshell Lead

1:1
Fully supported

PropFlo lead and contact records merge into Nutshell's Lead object when the source record has no closed deal association. The lead name, email, phone, source, and status fields map directly. Owner assignment resolves by email match against Nutshell user accounts. Records without a matching owner assign to a fallback Nutshell admin.

PropFlo

Contact (with closed deal)

maps to

Nutshell

Nutshell Person

1:1
Fully supported

PropFlo contacts that have associated closed PropFlo deals map to Nutshell Person records. The contact's primary company links to the corresponding Nutshell Company via the person-company association. PropFlo contact custom fields migrate as Nutshell Person custom fields created before the migration run.

PropFlo

Company

maps to

Nutshell

Nutshell Company

1:1
Fully supported

PropFlo company records map directly to Nutshell Company records. Company name, domain, address, industry, employee count, and annual revenue fields map to their Nutshell equivalents. Parent-company hierarchies in PropFlo map to Nutshell's parent-company relationship where supported. All standard address components, including city, state, and country, are transferred as separate fields.

PropFlo

Deal / Pipeline

maps to

Nutshell

Nutshell Pipeline + Stage

1:1
Fully supported

PropFlo deal pipelines map to Nutshell Pipelines. Each PropFlo pipeline stage becomes a Nutshell stage within that pipeline, with probability and expected-days values configured per Nutshell's stage settings. PropFlo's real estate-specific stage names (e.g., site visit scheduled, legal review, registry) map as custom stage labels or require Nutshell admin to configure matching stage names before data loads.

PropFlo

Deal Record

maps to

Nutshell

Nutshell Lead (in pipeline context)

1:1
Fully supported

Individual PropFlo deal records (with deal name, amount, close date, stage, owner) map to Nutshell Lead records that are placed in a pipeline. The deal amount maps to Nutshell's monetary fields; close date maps to expected close date; owner resolves by email match. The PropFlo deal ID is preserved as a custom field for traceability.

PropFlo

Activity (Call / Email / Meeting / Note)

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

PropFlo activity records — calls, emails, meetings, and notes — attach to the corresponding Nutshell Person or Company record by matching the parent contact or company ID. Original timestamps and activity owners are preserved. PropFlo's real estate event types (site visit, document upload) map as Nutshell activity notes with the event type appended to the activity subject.

PropFlo

AOS (Agreement of Sale)

maps to

Nutshell

Nutshell Custom Fields on Company or Person

1:1
Fully supported

PropFlo's AOS records have no native Nutshell equivalent. We map AOS fields — agreement date, unit number, consideration amount, payment schedule milestones, registration status — to custom fields on the associated Nutshell Company (for property-level AOS) or Person (for buyer-specific AOS) record. Your Nutshell admin creates these fields before migration.

PropFlo

Property / Unit

maps to

Nutshell

Nutshell Custom Fields on Company

1:1
Fully supported

PropFlo properties and units are real estate-specific objects with unit numbers, tower/phase, floor, inventory status, and pricing fields. Nutshell has no property object. We map these as custom fields on the Nutshell Company record representing the development or property, or as a separate custom object if your Nutshell plan supports it. Unit-level detail stores as repeating custom fields or JSON-encoded custom field values.

PropFlo

Custom Field (Lead / Contact / Company)

maps to

Nutshell

Nutshell Custom Field

1:1
Fully supported

PropFlo custom fields on leads, contacts, and companies migrate to Nutshell custom fields on the corresponding Nutshell entity (Lead, Person, Company). The Nutshell admin must create the custom fields in Nutshell Settings before migration. Pick-list custom fields require value-by-value mapping where Nutshell's pick-list options differ from PropFlo's values.

PropFlo

Workflow / Approval Flow

maps to

Nutshell

None — export for rebuild

1:1
Fully supported

PropFlo workflows, approval flows, and automated sequences do not migrate. These are platform-specific automation constructs with no Nutshell equivalent. FlitStack exports your PropFlo workflow definitions as a structured reference document so your Nutshell admin can rebuild them in Nutshell's workflow builder or third-party automation tools.

PropFlo

User / Owner

maps to

Nutshell

Nutshell User (by email)

1:1
Fully supported

PropFlo owner assignments on records map to Nutshell users by email address lookup. PropFlo user records (name, email, role) are resolved against Nutshell user accounts. Any PropFlo owner without a corresponding Nutshell user is flagged before migration for admin action — either create the Nutshell user or reassign the record.

PropFlo

Attachment / File

maps to

Nutshell

Nutshell File Attachment

1:1
Fully supported

PropFlo file attachments on contacts, companies, and deals download and re-upload to Nutshell's file storage attached to the corresponding Person, Company, or Lead record. File size limits apply per Nutshell's attachment constraints. Inline images in PropFlo notes are extracted and rehosted as Nutshell attachments.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

PropFlo logo

PropFlo gotchas

High

No documented REST API constrains migration approach

Medium

AOS and Demand Note document files require separate handling

Medium

WhatsApp conversation media attachments not included in standard export

Low

Workflow automations cannot be exported and must be rebuilt

Low

Dashboard and report definitions are not exportable

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • AOS and real estate transaction records have no native Nutshell equivalent

    PropFlo's Agreement of Sale (AOS) object — with fields for agreement date, unit number, consideration amount, payment schedule milestones, and registration status — does not exist as a standard object in Nutshell. Nutshell is a general-purpose CRM without a real estate transaction model. FlitStack maps AOS data to custom fields on the Nutshell Company record (for property-level AOS data) or Person record (for buyer-specific AOS data). Your Nutshell admin must pre-create these custom fields — agreement date, unit number, consideration, payment milestones, registration status — before the migration loads. If you have hundreds of active AOS records with detailed payment schedules, the custom field setup and value mapping is the longest planning step in this migration.

  • PropFlo pipelines with real estate-specific stage names require manual Nutshell stage configuration

    PropFlo deal pipelines use real estate-specific stage names such as 'Site Visit Scheduled', 'Booking Confirmed', 'Agreement Executed', 'Registry Submission', and 'Handed Over'. Nutshell's pipeline stage configuration requires each stage to have a probability percentage and expected-days value configured per pipeline. If your PropFlo pipeline has more than five stages with custom real estate labels, the Nutshell admin must manually create matching stage names in the Nutshell pipeline settings before migration data can land with correct stage assignments. FlitStack delivers a stage-mapping plan as part of the pre-migration schema setup document.

  • Property and Unit objects collapse to Company custom fields or require a custom object

    PropFlo's Property and Unit objects store tower/phase names, unit numbers, floor levels, inventory status (available, sold, blocked), and per-unit pricing. Nutshell has no property or unit object. The standard migration approach maps property metadata to custom fields on the Nutshell Company record representing the development. If your PropFlo setup tracks hundreds of individual units with independent status and pricing, you may need a custom object in Nutshell — which requires Nutshell Enterprise or a custom object add-on. We surface the unit count and data complexity in the pre-migration audit so you can confirm whether a custom object is needed before migration planning begins.

  • Workflows, approval flows, and AOS generation templates do not migrate

    PropFlo's built-in workflows — demand-note approval flows, payment reminder sequences, lead assignment rules, and AOS document generation templates — are platform-specific automation constructs that have no equivalent in Nutshell. They cannot be converted or transferred. Nutshell's automation tools (email sequences, task triggers, and webhooks in Nutshell Pro and above) offer different logic models. FlitStack exports your PropFlo workflow definitions as a structured reference document so your Nutshell admin has a rebuild guide. The automation rebuild effort is a separate project scope not included in the standard migration quote.

  • Multi-company contact associations collapse to a primary Company link in Nutshell

    PropFlo allows a contact to be associated with multiple companies simultaneously — a common pattern in real estate where an agent works across multiple developments. Nutshell Person records link to a single primary Company. Any additional company associations in PropFlo require either manual recreation in Nutshell as secondary Person-Company relationships or a custom junction approach. We migrate the most recently modified company association as the primary Company link and flag secondary associations for admin review. If your team relies heavily on multi-company contact associations, the migration plan should include a review of how to handle them in Nutshell's model.

Migration approach

Six steps for a successful PropFlo to Nutshell data migration

  1. Audit PropFlo data volume and custom field inventory

    FlitStack connects to PropFlo via API and inventories all leads, contacts, companies, deals, activity records, and custom fields. We identify real estate-specific objects (AOS, Properties, Units) and their field counts. The audit output includes record counts per object, custom field names and types, pipeline and stage names, and owner distribution. This report forms the basis of the migration scope and pricing quote.

  2. Design Nutshell custom field schema and pipeline configuration

    Based on the audit, FlitStack delivers a Nutshell schema setup plan: custom field names and types to create on Lead, Person, and Company objects; pipeline and stage names to configure in Nutshell settings; and AOS/property field mapping for real estate-specific data. Your Nutshell admin creates the fields and pipelines before we begin data migration. We provide step-by-step instructions for each Nutshell UI action required.

  3. Resolve owners by email match against Nutshell users

    PropFlo owner assignments on every record are matched against Nutshell user accounts by email address. Any PropFlo owner without a corresponding Nutshell user is flagged in a pre-migration report with the affected record count. Your team either creates the missing Nutshell user accounts or assigns those records to a fallback owner before the migration run. No record migrates without a confirmed Nutshell owner assignment.

  4. Run a sample migration with field-level verification

    A representative slice of PropFlo data — typically 100–500 records spanning leads, contacts, companies, deals, and activities — migrates to Nutshell in a test run. FlitStack generates a field-level diff showing every mapped field, the source value, and the destination value. You verify that AOS fields landed in the correct Nutshell custom fields, deal stages mapped to the right pipeline stages, and owner assignments resolved correctly before the full migration commits.

  5. Execute full migration with delta-pickup window

    The full PropFlo dataset migrates to Nutshell using the verified field mapping from the sample run. A delta-pickup window (typically 24–48 hours) captures any records created or modified in PropFlo during the cutover window so Nutshell reflects PropFlo's final state at go-live. Audit logs record every record created, updated, or skipped. One-click rollback is available if reconciliation detects data integrity issues.

Platform deep dives

Context on both ends of the pair

PropFlo logo

PropFlo

Source

Strengths

  • AI-powered lead scoring and automated nurturing reduce manual follow-up overhead for sales teams.
  • End-to-end coverage from lead capture through post-sales document generation (AOS, Demand Notes) in a single platform.
  • Highly rated ease of use (top 5 globally per G2) with rapid onboarding reported by multiple customers.
  • WhatsApp, email, and telephony integration for omni-channel client engagement within the CRM.
  • Affordable positioning targeting young real estate businesses, with strong customer support ratings.

Weaknesses

  • No publicly documented REST API — data export relies on admin panel functionality and manual coordination.
  • Dashboard and report definitions do not export and must be manually rebuilt in the destination platform.
  • Export limits (2K accounts/month noted in Crunchbase) may restrict bulk migration speed for larger datasets.
  • Limited third-party integration ecosystem compared to established CRM platforms.
  • As a younger product, documentation depth and community resources are less mature than competitors.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across PropFlo and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    PropFlo: Not publicly documented.

  • Data volume sensitivity

    B

    PropFlo doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your PropFlo to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about PropFlo to Nutshell data migrations

Answers to the questions buyers ask most during PropFlo to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your PropFlo to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most PropFlo-to-Nutshell migrations complete in 48–72 hours of clock time for under 50,000 total records. Larger setups with 500,000+ records, multiple AOS and property objects, or extensive custom field configurations extend to 5–7 days. The longest planning step is configuring Nutshell custom fields and pipeline stages to match PropFlo's real estate-specific data model before data can land correctly. This timeline assumes your Nutshell environment is prepared with the required custom fields and pipeline stages.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PropFlo.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day