Migrate from PropertySimple to Nutshell

PropertySimple person records map directly to Nutshell People. Nutshell People require a linked Company (Account) record — contacts without a primary company in PropertySimple are attached to a default 'Unassigned Company' record in Nutshell, which your admin can split or reassign post-migration.

PropertySimple contact records with a 'lead' status value route to Nutshell's Lead object. Records already marked as active clients or customers in PropertySimple route to Nutshell Person. The routing rule is based on the source status field value — your team confirms the rule during the pre-migration audit.

PropertySimple company records map 1:1 to Nutshell Companies. If the source data includes a parent‑company relationship, the link is recreated using Nutshell's parent‑company field; otherwise the company is created as a flat record. Multi‑contact companies collapse into one Nutshell Company with all related People linked, preserving activity history and any custom fields listed in the pre‑migration checklist.

PropertySimple deal records (representing real estate transactions) map to Nutshell Deals. Each Deal in Nutshell is tied to a Pipeline and a Stage. PropertySimple deal stage values map to Nutshell stage names value-by-value during migration. If PropertySimple has multiple pipelines, each maps to a separate Nutshell Pipeline object.

PropertySimple pipelines (if the account uses more than one) map to separate Nutshell Pipeline objects. Nutshell supports multiple pipelines with distinct stage sets per pipeline. Stage names are mapped value-by-value — HubSpot-style pick-list mapping with explicit value pairs delivered in the migration plan before the run commits.

Stage names mapped value-by-value from PropertySimple to Nutshell. Stage probability and forecast category re-applied based on Nutshell's stage configuration. HubSpot-style probability percentages attached as custom fields if the source data includes them — Nutshell's default stages don't carry probability automatically.

PropertySimple activity history (calls, emails, meetings, notes) migrates as Nutshell Activities with original timestamps and owner assignments preserved. Each activity type maps to a corresponding Nutshell Activity type — calls to Call, emails to Email, meetings to Meeting, notes to Note. Parent-record links (person or deal) are preserved so activity history attaches to the correct record in Nutshell.

PropertySimple custom fields — including ZIP-code marketing data, listing IDs, property status fields, social-media source tags, and automated-ad-campaign metadata — map to Nutshell custom fields on Person, Company, or Deal. Nutshell custom fields must be created before the migration run. We deliver a pre-migration field creation checklist so your Nutshell admin can provision the fields in advance.

PropertySimple drip campaigns, AI follow-up sequences, and social-media automation have no Nutshell equivalent. These are not migrated. We export your PropertySimple automation definitions as a structured reference document and recommend rebuilding email sequences in Nutshell Pro's automation tool using that export as the specification.

PropertySimple owner/agent assignments resolve to Nutshell Users by email match. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts for them first or assigns their records to a fallback owner. No record lands in Nutshell without a resolved owner.

PropertySimple file attachments on contacts, companies, or deals are re‑uploaded to Nutshell's file‑attachment model. Each file is stored with its original name and MIME type; duplicate files are deduplicated by content hash. File size is limited to Nutshell's default 25 MB per attachment, and any oversized files are flagged for manual handling. Inline images in notes are extracted, downloaded, and re‑hosted as Nutshell file attachments linked to the parent record.

PropertySimple tags on contacts and companies are imported as Nutshell Tags, which are free‑form labels attached to People, Companies, Leads, and Deals. Tag names are preserved exactly, including case and any hyphens or underscores, to avoid duplicates. If a PropertySimple record holds multiple tags, each tag creates a separate Nutshell Tag on the same record, ensuring the full tagging history is available for reporting and segmentation in Nutshell.

PropertySimple's ZIP-code marketing data (exclusive ZIP claims, buyer leads per ZIP, ad spend per ZIP) has no native Nutshell equivalent. We map this to a set of Nutshell custom fields — your admin pre-creates these before migration. The data migrates as reference fields rather than as a functional marketing tool.