CRM migration
Field-level mapping, validation, and rollback between Property Shell and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Property Shell
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Property Shell and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Property Shell models real estate sales around project-specific objects — leads tied to property listings, development-stage deal pipelines, and marketing automation for buyer nurturing campaigns. Nutshell uses a conventional CRM object model with People, Companies, Leads, Deals, Tasks, and Notes. The migration maps Property Shell contacts to Nutshell People, companies to Nutshell Companies, and active opportunities to Nutshell Deals with stage mapping. The key translation challenges are Property Shell's property-specific data (listing status, development stages, settlement milestones) which has no native equivalent in Nutshell — these are preserved as custom fields. Nutshell's marketing automation features are less developed than Property Shell's dedicated campaign management tools; teams expecting feature parity in this area will need to rebuild sequences manually. We use Nutshell's JSON-RPC API to write records sequentially — People before Deals (since Deals link to People), then Companies — with owner resolution by email match against Nutshell user accounts. A delta-pickup window runs during cutover to capture in-flight changes.
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 Shell 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 Shell
Contact
Nutshell
People
1:1Property Shell Contacts map directly to Nutshell People. Nutshell People store name, email, phone, address, and custom fields. We match owner IDs to Nutshell user accounts by email during migration so assigned records land with the correct owner. Where duplicate contacts exist, we flag them for review before insert to prevent double‑booking in Nutshell.
Property Shell
Company
Nutshell
Companies
1:1Property Shell Company records migrate to Nutshell Companies with company name, domain, industry, employee count, and revenue preserved. Multi-contact companies in Property Shell map to one Nutshell Company record with all associated People linked. We also transfer the original create timestamp and resolve the owner by email match so the Nutshell Company shows the correct creator and assigned user.
Property Shell
Lead
Nutshell
Lead
1:1Property Shell Leads map 1:1 to Nutshell Leads. Lead status pick-list values require value-by-value mapping since Property Shell uses custom status labels tied to property interest levels (Inquired, Qualified Buyer, VIP). Lead source field maps to Nutshell's standard source field.
Property Shell
Deal
Nutshell
Deal
1:1Property Shell Deals map to Nutshell Deals with deal name, value, close date, and stage preserved. Stage names (Off the Plan, Under Contract, Settlement Due, Settled) map to Nutshell stage values — these require value mapping since the stage labels differ between platforms.
Property Shell
Pipeline
Nutshell
Pipeline
1:1Property Shell's multiple deal pipelines map to a single Nutshell pipeline with stage-based grouping. If Property Shell uses separate pipelines for different development projects, these collapse into Nutshell's unified pipeline view — project attribution preserved as a custom field on each Deal.
Property Shell
Task/Activity
Nutshell
Task
1:1Property Shell tasks and activities migrate to Nutshell Tasks with original due dates, assigned owners, completion status, and task descriptions preserved. Task type (Call, Email, Meeting, Follow-up) maps to Nutshell's task type field. We also preserve the original created timestamp and link each task to its related Nutshell People, Company, or Deal using the migration ID map.
Property Shell
Note
Nutshell
Note
1:1Property Shell Notes migrate as Nutshell Notes with original create timestamps and owner attribution. Notes linked to specific contacts, companies, or deals are re-linked to the corresponding Nutshell records using the migration ID map. All note body text is transferred verbatim, and any empty notes are omitted to keep the Nutshell timeline clean.
Property Shell
Attachment/File
Nutshell
Attachment
1:1Property Shell file attachments on contacts, companies, and deals are re‑uploaded to Nutshell's attachment model, preserving original file names and upload dates. File size limits apply — files exceeding Nutshell's attachment size cap are flagged and held in a secure staging bucket, with a manifest listing each file, its original record, and size for manual re‑upload by your team post‑migration.
Property Shell
Property-Specific Data (listing status, development stage, settlement date)
Nutshell
Custom Fields on Deal
1:1Property Shell's property-listing fields (listing status, development stage, settlement milestone, deposit amount, floor plan reference) have no native Nutshell equivalent. We create custom fields on Nutshell Deals — Listing_Status__c, Development_Stage__c, Settlement_Date__c, Deposit_Amount__c — and migrate the values. These require Nutshell-side field creation before the migration runs.
Property Shell
Custom Property Fields
Nutshell
Custom Fields on People/Companies/Leads/Deals
1:1Property Shell custom properties (industry‑specific fields like Preferred_Area__c or Investment_Type__c) migrate to Nutshell custom fields on the appropriate object. We identify the target object by examining which records the custom property appears on in Property Shell's schema export. Where a custom field does not yet exist in Nutshell, we add it using Nutshell's field builder, matching data types such as text, pick‑list, or currency.
Property Shell
User/Owner
Nutshell
User
1:1Property Shell owner IDs are resolved against Nutshell user accounts by matching email addresses. Unresolved owners (inactive Property Shell users or uninvited team members) are flagged before migration — their records are assigned to a designated fallback Nutshell user so no record lands without an owner.
Property Shell
Workflow/Sequence/Automation
Nutshell
Not Migrated
1:1Property Shell marketing automation workflows, buyer nurture sequences, and stage-triggered email campaigns do not migrate. These require manual rebuild in Nutshell's automation tools or a separate marketing platform. We provide a workflow export document listing every active workflow with its trigger conditions and action sequence for reference during rebuild.
| Property Shell | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Company | Companies1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Task/Activity | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Attachment/File | Attachment1:1 | Fully supported | |
| Property-Specific Data (listing status, development stage, settlement date) | Custom Fields on Deal1:1 | Fully supported | |
| Custom Property Fields | Custom Fields on People/Companies/Leads/Deals1:1 | Fully supported | |
| User/Owner | User1:1 | Fully supported | |
| Workflow/Sequence/Automation | Not Migrated1: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 Shell gotchas
No documented public API for data export
Highly customised per-customer schema requires pre-migration field audit
Interactive Maps are visualisation-layer only and cannot be migrated
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
Export Property Shell schema and inventory records
We connect to Property Shell's API to extract the full record inventory — contacts, companies, leads, deals, tasks, notes, and attachments — along with the complete custom property schema. We inventory every custom field, pick-list value, and pipeline stage label. This inventory drives the mapping plan and surfaces custom field creation requirements for Nutshell before migration begins. The export includes record counts and data quality flags to guide any pre‑migration cleanup.
Create Nutshell custom fields and prepare field mapping
Based on the Property Shell schema export, we create a custom field creation checklist for your Nutshell admin (Listing_Status__c, Development_Stage__c, Settlement_Date__c, Deposit_Amount__c, Project_Name__c, Source_System_ID__c, Original_Create_Date__c). The checklist itemises field names, data types, and pick‑list options so your admin can create each field in Nutshell's field builder before the migration run. Once these are confirmed created, we finalise the value‑mapping table for lead statuses and deal stages, then lock the mapping plan for the sample migration.
Resolve owners by email match
Property Shell owner IDs are resolved against Nutshell user accounts by matching email addresses. Unresolved owners (inactive Property Shell users or team members not yet invited to Nutshell) are flagged with a pre-migration owner resolution report. Your team either invites them to Nutshell before migration or designates a fallback Nutshell user — no record lands without a valid owner assignment.
Run sample migration with field-level diff
A representative sample — typically 200–500 records spanning contacts, companies, deals, and activities — migrates into a Nutshell sandbox environment. We generate a field‑level diff report comparing source values against destination values so you can verify lead status mapping, deal stage mapping, custom field population, and owner resolution before the full run commits. The report highlights any missing or mismatched values, allowing your team to adjust the mapping before the production migration begins.
Execute full migration with delta-pickup cutover
Full data migration runs against your live Nutshell account using the validated mapping. Using Nutshell's JSON‑RPC API, we write records sequentially — People first, then Companies, then Deals — to respect foreign‑key dependencies and maintain referential integrity. A delta‑pickup window (typically 24–48 hours) captures any records created or modified in Property Shell during the migration run so Nutshell reflects Property Shell's final state at go‑live. Audit logs document every operation, and one‑click rollback is available if reconciliation fails.
Platform deep dives
Property Shell
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 Shell 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 Shell: Not publicly documented.
Data volume sensitivity
Property Shell 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 Property Shell to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Property Shell 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 Shell
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.