Migrate from Real Estate CRM to Nutshell

Real Estate CRM contacts map directly to Nutshell People. Nutshell requires a name (first + last or organization name) and supports email, phone, address, and custom fields on the Person record. Contacts without a last name (e.g., company-only records) map to the Nutshell Company object instead.

Real Estate CRM company or brokerage records map to Nutshell Companies. Nutshell Company records store business name, domain/website, industry, employee count, address, phone, and description fields. If the source CRM includes a parent-company hierarchy, we map that relationship to Nutshell's Parent Company field, preserving hierarchy depth. Custom fields on the source company record (e.g., brokerage license number) are created in Nutshell before migration and attached to the Company record.

Unqualified leads from Real Estate CRM map to Nutshell Leads. Nutshell Lead records hold name, contact info, lead status, source, and owner. The lead status pick-list values from Real Estate CRM map to Nutshell's lead status field via value mapping — custom lead statuses require pre-creation in Nutshell before migration.

Real Estate CRM deals or transactions map to Nutshell Deals. Nutshell Deal records hold deal name, amount, stage, expected close date, owner, and associated company/person links. Deal pipelines in the source CRM map to Nutshell's Deal pipeline — Nutshell supports one default pipeline with customizable stages.

Real Estate CRM property or listing objects have no direct Nutshell equivalent. We map property fields (address, MLS number, listing price, property type, listing status, square footage) to custom fields on the related Nutshell Company (for brokerage-owned listings) or Deal (for active transactions). Nutshell Enterprise allows creating these custom fields before migration; Starter plans require manual field creation post-migration.

Real Estate CRM pipeline stage names (Active, Under Contract, Pending, Closed Won, Lost) map to Nutshell Deal stage values via value-by-value mapping. Nutshell's stage probability and forecast category re-applied per your specifications. Stage-entered timestamps preserved as custom datetime fields in Nutshell for reporting continuity.

Real Estate CRM owner assignments map to Nutshell's owner field on each record type. Owner resolution happens by email match — Real Estate CRM owner email addresses matched against Nutshell user emails. Unmatched owners flagged before migration; your team either invites them to Nutshell or assigns their records to a fallback owner.

Real Estate CRM tasks and activities map to Nutshell Tasks. Task subject, due date, completion status, and owner preserved. Real estate-specific activity types (showing, inspection, offer review) migrate as custom Task fields since Nutshell's standard Task types are limited to Call, Email, and Other.

Real Estate CRM notes map to Nutshell Notes attached to the corresponding Person, Company, Lead, or Deal record. Rich-text formatting in source notes preserved where the destination supports it. Notes with @-mentions or thread context stored as plain text with a reference tag.

File attachments from Real Estate CRM—such as listings, contracts, and disclosures—are re‑uploaded to Nutshell as file attachments on the matching Person, Company, Lead, or Deal record. The original file name and creation date are preserved where possible. Nutshell imposes per‑file size limits; any file exceeding the limit is flagged for manual handling, or we split the upload into smaller chunks using Nutshell's chunked upload API.

Real Estate CRM custom objects (listing agent roles, property type classifications, referral source tracking) map to Nutshell custom fields on the appropriate module (Person, Company, Lead, or Deal). Nutshell's Enterprise plan is required for custom fields on all modules; lower tiers limit custom fields to specific modules.

Real Estate CRM association labels for multi-agent transactions have no Nutshell equivalent. We map these roles to custom fields on the Deal record (e.g., Listing_Agent_Email__c, Buyer_Agent_Email__c) or store them as tagged notes. Teams requiring a full role-based association model need a custom junction object rebuilt in Nutshell.