CRM migration

Migrate from Property Shell to Nutshell

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

Property Shell logo

Property Shell

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Property Shell and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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 Shell logo

Property Shell

What's pushing teams away

  • Limited publicly documented API or export mechanisms, making it difficult to extract data for reporting, backups, or migrations to another platform.
  • Smaller review base (29 verified reviews on Capterra) and thin community resources compared to established CRM platforms, making peer support harder to find.
  • As a niche platform targeting property developers in Australia and New Zealand, teams operating in other regions or industries may find the feature set too specialised for broader CRM needs.

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

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

maps to

Nutshell

People

1:1
Fully supported

Property 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

maps to

Nutshell

Companies

1:1
Fully supported

Property 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

maps to

Nutshell

Lead

1:1
Fully supported

Property 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

maps to

Nutshell

Deal

1:1
Fully supported

Property 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Property 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

maps to

Nutshell

Task

1:1
Fully supported

Property 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

maps to

Nutshell

Note

1:1
Fully supported

Property 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

maps to

Nutshell

Attachment

1:1
Fully supported

Property 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)

maps to

Nutshell

Custom Fields on Deal

1:1
Fully supported

Property 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

maps to

Nutshell

Custom Fields on People/Companies/Leads/Deals

1:1
Fully supported

Property 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

maps to

Nutshell

User

1:1
Fully supported

Property 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Property 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.

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 Shell logo

Property Shell gotchas

High

No documented public API for data export

High

Highly customised per-customer schema requires pre-migration field audit

Medium

Interactive Maps are visualisation-layer only and cannot be migrated

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

  • Property Shell's property-listing data has no native Nutshell home

    Property Shell tracks listing status, development stages, settlement milestones, deposit amounts, and floor plan references as native fields on deals. Nutshell has no property-specific object or standard fields for these data points. We migrate these values into custom fields on Nutshell Deals (Listing_Status__c, Development_Stage__c, Settlement_Date__c, Deposit_Amount__c), but this requires your team to create these custom fields in Nutshell before migration. Without pre-created custom fields, the values land in a staging table for post-migration review. Plan for 1–2 hours of Nutshell admin work to create the custom fields before data lands.

  • Deal pipeline collapse changes pipeline visibility

    Property Shell supports multiple parallel deal pipelines — teams running separate pipelines for different development projects or buyer segments can see all pipelines simultaneously. Nutshell uses a single unified pipeline view with stage-based grouping. Multiple Property Shell pipelines collapse into Nutshell's single pipeline model with project attribution preserved as a custom field on each Deal. Teams that relied on Property Shell's multi-pipeline dashboard view will need to recreate that visibility using Nutshell's reporting filters on the Project_Name__c custom field after migration.

  • Lead status value mapping requires manual setup before migration

    Property Shell uses custom lead status labels tied to real estate buyer qualification (Inquired, Qualified Buyer, VIP, Off-Market Enquiry). Nutshell's default Lead Status values are Unqualified, New, Working, Nurturing, and Closed — converted. The migration runs value-by-value mapping between these pick-lists. If your Property Shell lead statuses don't map cleanly to Nutshell's defaults, your Nutshell admin needs to add custom status values before migration or accept that some buyer-qualification context is mapped to the nearest Nutshell default. Mis-mapped statuses can affect lead routing and reporting segments post-migration.

  • Marketing automation workflows cannot migrate and must be rebuilt

    Property Shell's buyer nurture journeys, property-alert automations, and stage-triggered email campaigns are platform-native workflows that do not export in a transferable format. These must be rebuilt manually in Nutshell's sequence and automation tools or in a dedicated marketing automation platform. Nutshell's automation capabilities are more limited than Property Shell's dedicated marketing automation — particularly around granular stage-based triggers and property-listing event triggers. We provide a workflow audit export listing every active Property Shell workflow so your team has a reference inventory for the rebuild effort.

  • File attachment size limits may require manual re-upload

    Property Shell stores file attachments on contacts, companies, and deals — floor plans, contracts, deposit receipts, and property brochures. Nutshell's attachment model has size limits per file. Files exceeding Nutshell's attachment cap are flagged during the migration and held in a staging location for manual re-upload by your team after migration. Property Shell's contract documents and high-resolution floor plans are the most likely candidates to exceed these limits. We provide a manifest of flagged files with their original record associations so nothing is lost.

Migration approach

Six steps for a successful Property Shell to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Property Shell logo

Property Shell

Source

Strengths

  • Purpose-built for property development projects with native concepts for lots, stages, releases, and settlements.
  • Real-time interactive mapping for display suites and project websites showing stock status and lot availability.
  • AI-powered lead scoring and automated nurture journeys from first enquiry through to settlement.
  • Comprehensive contract management with variation and upgrade tracking across the settlement lifecycle.
  • Integrates development, marketing, sales, and finance team collaboration within a single platform.

Weaknesses

  • No publicly documented API or developer portal — export and migration rely on ad-hoc data extraction.
  • Small review cohort and limited third-party community resources for troubleshooting or peer support.
  • Interactive Map geometry and visual stock statuses are UI-layer data not exposed for migration or backup.
  • Highly custom implementations per customer mean no standard schema — every migration requires a full field audit.
  • Platform is primarily oriented to the Australian property development market, limiting applicability for teams in other regions.
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 Shell 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 Shell: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Property Shell to Nutshell migrations complete in 48–72 hours for under 25,000 records. Larger setups with 100,000+ records or complex custom property schemas extend to 5–10 days. The longest planning step is creating Nutshell custom fields for property-specific data (listing status, development stage, settlement date) and mapping Property Shell lead status values to Nutshell's lead status pick-list. We provide a custom field creation checklist before migration so this setup doesn't block the data movement.

Adjacent paths

Related migrations to explore

Ready when you are

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