CRM migration

Migrate from Property Raptor to Nutshell

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

Property Raptor logo

Property Raptor

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Property Raptor and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Property Raptor is a Salesforce-backed real estate CRM with property objects, AI listing matching, and listing-portal integrations (PropertyFinder, Bayut, Rightmove, Zoopla). Nutshell is a general-purpose CRM built for small-to-mid-market sales teams — its data model covers People, Companies, Leads, and Deals with a four-view pipeline. The platforms share no native object parity: Property Raptor's Listings, Properties, and custom real-estate fields have no direct Nutshell equivalent. We map contacts → People, companies → Companies, leads → Leads, and opportunities → Deals. Property-specific fields (property type, listing status, price, area) migrate as Nutshell custom fields on People or Deals — your team decides whether they belong on the contact record or the deal record based on your sales process. Listings and property hierarchies require a custom-object build in Nutshell before migration; we deliver the schema plan upfront. Workflows, automations, portal integrations, and listing-portal syncs do not migrate — they must be rebuilt in Nutshell or replaced with Nutshell's built-in automation triggers. All migration runs against Nutshell's REST API with scoped read access on Property Raptor; your team continues working in Property Raptor throughout the process, with a 24–48 hour delta pickup window at cutover.

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

Property Raptor logo

Property Raptor

What's pushing teams away

  • Gartner reviewers explicitly call out that integration with common listing platforms 'is not well-developed' and that UI/UX could be more user-friendly — counter to the 30+ portals marketing claim.
  • Support is unavailable outside business hours, forcing reliance on a chatbot for off-hours issues, which is problematic for agencies operating across multiple time zones.
  • Pricing is fully custom and sales-led — no published per-user tiers means buyers cannot evaluate cost without a sales conversation.
  • Implementation is slow and requires dedicated CRM admin capability, ruling out solo agents or small brokerages wanting fast self-serve onboarding.
  • Workflows and automations are Salesforce-native and not portable — exiting the platform means rebuilding every workflow rule, lead routing, and notification trigger from scratch.

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 Property Raptor objects map to Nutshell

Each row shows how a Property Raptor 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.

Property Raptor

Contact

maps to

Nutshell

Person

1:1
Fully supported

Property Raptor Contact maps directly to Nutshell Person. Nutshell Person holds name, email, phone, address, and custom fields. Primary company association resolves to a Nutshell Company record. Owner is resolved by email match to a Nutshell user. The original create date is preserved as a custom datetime field in Nutshell, and the Property Raptor internal ID is stored for traceability and delta-run de-duplication. A pre-flight validation checks that every Contact has a valid owner before migration begins.

Property Raptor

Company (Agency)

maps to

Nutshell

Company

1:1
Fully supported

Property Raptor's agency-level company records (the brokerage or firm) map to Nutshell Company. Domain, industry, employee count, and annual revenue fields carry over as direct maps or custom fields depending on Nutshell's field availability in the target account. Primary contact association resolves to a Nutshell Person record, and the owner is resolved by email match to a Nutshell user for accountability tracking. The original created date and source system ID are preserved for audit purposes.

Property Raptor

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Property Raptor Lead maps to Nutshell Lead — both use a first name, last name, email, phone, and source-field model. Nutshell Lead Status (New, Attempting Contact, Working, Nurture, Converted) is applied as a default; any Property Raptor lead-stage custom field maps via value-mapping to the nearest Nutshell status.

Property Raptor

Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

Property Raptor Opportunity maps to Nutshell Deal — deal name, amount, stage, close date, owner, and description carry over. Nutshell's four pipeline views display the same deal data; the pipeline assignment in Nutshell is chosen during migration scoping based on your team's workflow.

Property Raptor

Listing / Property

maps to

Nutshell

Custom Object: Listing

1:1
Fully supported

Property Raptor's Listing and Property objects have no direct Nutshell equivalent. We create a Nutshell custom object (Listing) with fields for property address, listing price, property type, listing status, and area — matching Nutshell's custom object creation workflow (Settings → Customize → Custom Objects). The listing record is linked to a Person or Deal via a custom lookup field.

Property Raptor

Listing Price / Property Value

maps to

Nutshell

Deal (amount field) or Custom Field on Listing

1:1
Fully supported

Active listing price migrates as a numeric custom field on the Listing custom object. For listings with associated deals (buyer representation side), the deal amount carries into the Nutshell Deal amount field so pipeline revenue views reflect actual transaction value.

Property Raptor

Task / To-Do

maps to

Nutshell

Task

1:1
Fully supported

Property Raptor To-Dos map to Nutshell Tasks — subject, due date, completion status, and owner carry over. Nutshell Tasks attach to Person, Company, Lead, or Deal records via the CRM links model. Completed status is preserved as a boolean field.

Property Raptor

Activity History (calls, emails, meetings)

maps to

Nutshell

Activity

1:1
Fully supported

Property Raptor activity records (call logs, email threads, meeting notes) migrate as Nutshell Activity entries on the relevant Person or Deal record. Original timestamps and activity owners are preserved. Attachments and inline images are downloaded and re-hosted in Nutshell's file storage.

Property Raptor

User / Owner

maps to

Nutshell

User

1:1
Fully supported

Property Raptor user records resolve to Nutshell users by email address match. Unmatched owners are flagged before migration — you either invite them to Nutshell or assign their records to a fallback user. Property Raptor's role-based permissions do not transfer; Nutshell role configuration is handled separately post-migration.

Property Raptor

Custom Property / Field (listing type, area, status)

maps to

Nutshell

Custom Field on Listing or Deal

1:1
Fully supported

Property Raptor's custom property fields on Listing and Property objects (e.g., listing_type, property_area_sqft, listing_status) are created as custom fields on the Nutshell Listing custom object before migration. Field type is matched — text fields to Nutshell text, pick-list fields to Nutshell choice fields, numeric fields to Nutshell number fields.

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.

Property Raptor logo

Property Raptor gotchas

Medium

Salesforce API limits apply to all migrations

High

Workflows and automations are non-portable

Medium

Regional customization creates picklist mapping complexity

Low

Portal-specific listing IDs do not transfer between systems

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

  • Listing and Property objects require a custom object build in Nutshell before any data moves

    Property Raptor's Listing and Property objects store real-estate-specific data (address, price, type, status, bedrooms, area) that has no native equivalent in Nutshell's standard data model. Nutshell supports custom objects created via Settings → Customize → Custom Objects, but those must exist before data can land in them. FlitStack AI delivers a custom-object schema plan as part of the migration package — your Nutshell admin (or our team) creates the Listing custom object with the required fields before we run any test migration. Skipping this step causes all listing-related records to fail validation.

  • Property Raptor's listing-portal integrations (Rightmove, Zoopla, PropertyFinder, Bayut) do not migrate

    Property Raptor maintains live bidirectional syncs with PropertyFinder, Bayut, Rightmove, and Zoopla — these connections are stored in Property Raptor's integration layer and have no counterpart in Nutshell. When you cut over to Nutshell, those portal listings will stop syncing automatically. You need to re-establish each integration separately in Nutshell or through a middleware connector (Zapier, Make) that Nutshell supports. This is a manual rebuild step, not a data migration step — we document which portals were active in Property Raptor so your team can prioritize reconnecting them.

  • Nutshell's contact-count plan limits affect post-migration pricing

    Nutshell's pricing tiers are gated by contact count (e.g., 500 contacts on the Starter tier, scaling up to 2,500 and beyond). Property Raptor does not impose a contact-count cap — your existing database may exceed the plan you initially select in Nutshell. After migration, Nutshell counts all Person records against your plan limit, not just active contacts. We flag your total Person count before migration so you can select the correct Nutshell plan tier. Exceeding the plan limit post-migration triggers an upgrade prompt and potential write restrictions.

  • Property Raptor's AI listing-matching data has no equivalent in Nutshell

    Property Raptor's AI algorithm generates buyer-matching scores and listing-recommendation data tied to specific property records. Nutshell does not have a native AI-matching engine for real estate listings — the matching data (scores, recommendation reasons, buyer profiles) stores as custom fields with no built-in display mechanism. We preserve the raw scores and recommendation data as text or numeric custom fields on the Listing record, but the UI that surfaces those recommendations in Property Raptor does not exist in Nutshell and must be handled as a process change rather than a data migration issue.

  • Multi-address contacts (agent with multiple office locations) need manual consolidation

    Property Raptor supports multiple addresses per contact record using its relation-data model (one profile → many locations). Nutshell Person records hold a single primary address field. We migrate the most-recently-modified address as the primary address on the Nutshell Person record. Secondary addresses are preserved as a custom text field (address_list__c) in a pipe-delimited format. Your team decides whether to maintain multiple Person records per office or collapse to one record with the primary address — we surface the count of multi-address contacts before migration so the decision is made before data lands.

Migration approach

Six steps for a successful Property Raptor to Nutshell data migration

  1. Audit Property Raptor data volume and custom field inventory

    FlitStack AI connects to Property Raptor via scoped read access and inventories all contacts, companies, leads, deals, listings, and tasks — plus every custom field on each object. We count records by type, flag records with multiple owners, identify multi-address contacts, and surface which listing-portal integrations are active. The output is a data inventory document that drives the migration plan and the Nutshell custom-object schema design.

  2. Design Nutshell custom object schema for listings and property fields

    Before any data moves, we deliver a Nutshell custom-object schema plan: the Listing custom object name, field names, field types, and pick-list values to create in Nutshell's Settings → Customize → Custom Objects. If your team uses Nutshell's Pro or Enterprise tier, we also map property-type and listing-status custom fields to the appropriate choice-field format. The Nutshell admin creates the schema — we provide the exact specification so there is no back-and-forth during the migration run.

  3. Resolve owners by email and create Nutshell user mapping

    Property Raptor user records are matched to Nutshell users by email address. Unmatched owner records are flagged in a pre-flight report — your team either invites the missing users to Nutshell or assigns a fallback owner before migration. No record migrates without a valid Nutshell owner; this prevents orphaned records that show no assigned user in Nutshell's pipeline views. This owner-resolution step also ensures that deal and task assignments remain intact after cutover, maintaining accountability across your sales pipeline.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records migrates first — spanning contacts, companies, leads, deals, listings, and tasks. We generate a field-level diff showing source values against destination values for every mapped field. You verify that property addresses landed correctly in the Listing custom object, deal amounts are correct, owner assignments match expectations, and listing-status value-mapping produced the intended Nutshell choice values. Sample approval gates the full migration.

  5. Execute full migration with delta-pickup window

    Full migration runs against Nutshell's REST API. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in Property Raptor during the cutover period. All operations are logged in an audit trail. If reconciliation fails — record counts, field values, or association links do not match — one-click rollback reverts the Nutshell account to its pre-migration state. After rollback confirmation, you can re-run with corrected mapping.

Platform deep dives

Context on both ends of the pair

Property Raptor logo

Property Raptor

Source

Strengths

  • Built on Salesforce infrastructure with enterprise-grade security and scalability from Hong Kong-based IMS.
  • AI-powered property matching and recommendation engine for connecting clients with suitable properties.
  • Multi-region and multi-currency support for agencies operating across different markets.
  • Native integrations with major listing portals including Rightmove, Zoopla, PropertyFinder, and Bayut.
  • WhatsApp Business, email, and chat automation within a unified CRM workflow.

Weaknesses

  • Pricing is fully custom and requires direct consultation, making cost estimation difficult without a sales conversation.
  • Implementation can be complex and slow, with users reporting extended setup timelines.
  • Limited native email integration — relies on Salesforce internal delivery or external Gmail and Outlook connections.
  • Offline access is not supported as Property Raptor is a fully online SaaS application.
  • Workflows and automations do not migrate directly and must be rebuilt on the destination platform.
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 Property Raptor 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

    Property Raptor: Specifically minimized by design; limits may be extended for high-usage patterns but this is rare.

  • Data volume sensitivity

    A

    Property Raptor exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Property Raptor 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 Property Raptor to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Property Raptor to Nutshell migrations complete in 48–72 hours of clock time for databases under 25,000 total records. Larger setups with 250,000+ records, a custom Listing object with many fields, or complex owner resolution extend to 5–10 days. The Nutshell custom-object schema design (Step 2) is typically the longest planning step if your team has not yet provisioned the Listing object in Nutshell — we deliver that specification before any data moves so schema creation runs in parallel with planning.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Property Raptor.
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