Migrate from Leadrat CRM for Real Estate to Nutshell

Leadrat leads map directly to Nutshell Leads. Both store contact-level data before a deal is associated. Leadrat lead status values (New, Contacted, Qualified, Lost) map to Nutshell's lead status pick-list via value mapping. Any Leadrat lead score stored as a number field migrates to a Nutshell custom number field.

Leadrat's person record (name, email, phone, job title, address) maps directly to Nutshell Person. The Leadrat contact's primary company link maps to Nutshell Person.CompanyId. Multi-company associations from Leadrat collapse to a primary company with a custom field storing secondary company references.

Leadrat companies map to Nutshell Companies. Company name, domain, industry, phone, address, and employee count carry directly. Industry pick-list values from Leadrat require value mapping against Nutshell's industry options — non-matching values are preserved as a custom text field. The Leadrat industry values that do not align with Nutshell's standardized options are flagged for manual review and stored as-is in a custom text field to preserve the original data without alteration.

Leadrat deals map to Nutshell Opportunities. Deal name, amount, and close date carry directly. Leadrat's custom deal stage labels (Enquiry, Site Visit, Negotiation, Closed Won) map value-by-value to Nutshell Opportunity Stage pick-list values. Probability percentages are assigned per Nutshell stage after mapping.

Leadrat's Property object has no Nutshell equivalent. Property name, project name, budget range, property type, and unit number migrate as custom fields on the Nutshell Company record. The property-to-contact association (which Leadrat stores as a relationship) requires a custom text field on the Person record listing associated property IDs.

Leadrat Portfolio Management tracks client property holdings over time. This data migrates to Nutshell Company custom fields (Portfolio_Property_Count__c, Portfolio_Total_Value__c) and a linked custom object if the team has Nutshell Enterprise — otherwise it is stored as a formatted text blob for reference.

Leadrat automated follow-ups and manual tasks map to Nutshell Tasks. Task subject, due date, status, and owner carry directly. A custom field on the Nutshell Task (Leadrat_Followup_ID__c) preserves the original Leadrat follow-up record ID for traceability. The follow-up type label (Call, Site Visit, SMS) maps to Nutshell Task custom fields.

Leadrat notes and activity entries — call logs, meeting summaries, and email correspondence — map to Nutshell Activities. Original timestamps, owner IDs, and the linked record ID are preserved on each migrated activity. Rich-text formatting and embedded media from Leadrat notes are simplified to plain text in Nutshell's activity body to ensure compatibility with Nutshell's activity display.

Leadrat tracks lead source as a property-portal attribution (Property Finder, Bayut, Google Ads, Website). Nutshell does not have a native lead-source field on Leads — we create Lead_Source__c as a custom pick-list on Nutshell Leads and map each portal name to its Nutshell equivalent value.

Leadrat user records are resolved by email match against Nutshell users before migration. Unmatched owners are flagged — teams either invite them to Nutshell first or assign records to a fallback owner. The Leadrat role/team grouping (Agent, Team Lead, Manager) is stored as a custom text field on the Nutshell User record for reporting parity.

Leadrat interaction logs — calls logged, emails tracked, site visit records — migrate as Nutshell Activities. Each activity type gets a custom Activity_Type__c field in Nutshell so reports can filter by call, email, or site visit. Original interaction timestamps and owner IDs are preserved on each activity record.

Leadrat file attachments linked to contacts, companies, or deals re-upload to Nutshell's file storage attached to the corresponding record. File size limits apply — Nutshell's attachment limit is 20MB per file, larger files are split or linked via URL reference.

Any Leadrat custom fields beyond the standard set require a corresponding custom field in Nutshell. FlitStack creates Nutshell custom fields using the same data type (text, number, date, pick-list) and applies value mapping for pick-list fields. Custom field API names in Leadrat are preserved as the custom field name in Nutshell for auditability.

Leadrat's automated follow-up sequences, lead-routing rules, and portal-integration triggers are automation-layer constructs with no Nutshell equivalent. These must be rebuilt in Nutshell's sequence and task tools or via Zapier. FlitStack exports the workflow definitions as a configuration reference document for the team's Nutshell admin.

Leadrat's real-estate-specific reports (lead-source performance, agent metrics, PPC ROI) do not map to Nutshell's report objects. The underlying data (contacts, deals, activities) migrates, so reports can be rebuilt in Nutshell's reporting module using the same source records. FlitStack provides a report-rebuild checklist referencing the migrated data.