CRM migration
Field-level mapping, validation, and rollback between Property Raptor and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Property Raptor
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Property Raptor and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Property 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)
Nutshell
Company
1:1Property 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
Nutshell
Lead
1:1Property 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
Nutshell
Deal
1:1Property 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
Nutshell
Custom Object: Listing
1:1Property 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
Nutshell
Deal (amount field) or Custom Field on Listing
1:1Active 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
Nutshell
Task
1:1Property 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)
Nutshell
Activity
1:1Property 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
Nutshell
User
1:1Property 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)
Nutshell
Custom Field on Listing or Deal
1:1Property 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.
| Property Raptor | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company (Agency) | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Listing / Property | Custom Object: Listing1:1 | Fully supported | |
| Listing Price / Property Value | Deal (amount field) or Custom Field on Listing1:1 | Fully supported | |
| Task / To-Do | Task1:1 | Fully supported | |
| Activity History (calls, emails, meetings) | Activity1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Property / Field (listing type, area, status) | Custom Field on Listing or Deal1:1 | 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.
Property Raptor gotchas
Salesforce API limits apply to all migrations
Workflows and automations are non-portable
Regional customization creates picklist mapping complexity
Portal-specific listing IDs do not transfer between systems
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Property Raptor
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Property Raptor and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
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
Property Raptor: Specifically minimized by design; limits may be extended for high-usage patterns but this is rare.
Data volume sensitivity
Property Raptor exposes a bulk API — large-volume migrations stream efficiently.
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 Property Raptor to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Property Raptor
Other ways to arrive at Nutshell
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.