Migrate from Rechat to Nutshell

Rechat Person maps to Nutshell Contact (the API-side noun; Nutshell UI calls this People). Standard fields (name, email, phone, address) migrate directly without transformation. The primary company association on a Rechat Person resolves via Account mapping before Contact migration begins so that the AccountId foreign key on each Nutshell Contact is valid and points to the correct Account record.

Rechat Company maps to Nutshell Account (API-side noun; UI uses Companies). Standard fields including company name, domain/website, physical address, industry classification, and employee count migrate directly as Account fields. Parent-company hierarchies in Rechat map to Nutshell's parent account field when that field is available in the target Nutshell instance. Any industry values without a direct Nutshell equivalent are stored as Legacy_Industry__c for reporting continuity.

Rechat Deal maps to Nutshell Deal directly — both platforms use a Deal object with name, amount, stage, close date, and owner. Pipeline names in Rechat that don't have a direct Nutshell equivalent are stored as a custom field (Pipeline_Name__c) and the deal is placed in Nutshell's default pipeline.

Rechat deal pipelines map to Nutshell pipeline stage values. Each Rechat pipeline name is mapped to a Nutshell stage value in a 1:1 value-mapping table. If Nutshell's default stages (New Lead, Presentation Scheduled, Decision Maker Bought-In, etc.) don't match Rechat stage names, new stage values are created in Nutshell before migration.

Rechat's email metadata, calls, meetings, and notes map to Nutshell Activity records. The activity type (email, call, meeting, note) maps to Nutshell's Activity type field. Original timestamps and activity owners (resolved by email) are preserved. The full email body is re-synced from the connected email account post-migration.

Rechat stores MLS listing IDs and listing-specific data as custom properties on Deals and Companies. Nutshell has no native MLS object, so we create custom fields (MLS_ID__c, Listing_Status__c, etc.) on the relevant Nutshell record type and attach listing documents as files. This preserves the data as reference fields without attempting a structural translation that doesn't exist.

Rechat's Marketing Center campaigns, email templates, and social media posts have no direct Nutshell equivalent. Nutshell has its own email marketing module but the content doesn't migrate. We export campaign definitions, template HTML, and audience segment logic as JSON files so your Nutshell admin can rebuild them in Nutshell's Campaign and Template tools.

Rechat transactions (deal-adjacent closing data) are stored as custom objects or custom fields in Rechat. Nutshell has no native transaction object. We map these to a custom field set on the associated Deal record (Transaction_Amount__c, Closing_Date__c, etc.) and attach closing documents as Nutshell Files.

Rechat owner IDs resolve to Nutshell users by email address match. A pre-flight user resolution report identifies any Rechat owner without a corresponding Nutshell user. Your team either creates the Nutshell user account first or assigns those records to a designated fallback owner before the full migration runs.

Rechat's tag system on People and Companies maps directly to Nutshell Tags. Tags are plain text labels that attach to records in both systems. Multi-value tags (a person has multiple tags) are preserved as a comma-separated tag string in Nutshell.

Files attached to Rechat People, Companies, or Deals are downloaded and re-uploaded as Nutshell Files associated with the equivalent record. File size limits follow Nutshell's attachment constraints. We verify each file uploads correctly in the sample migration before committing to the full run.

Rechat custom properties on People that have no direct Nutshell equivalent become Contact-level custom fields in Nutshell. We create the field (using the property name as the field label, slugifying to Nutshell's naming conventions), set the appropriate data type (text, number, date, picklist), and migrate values during the sample migration so the field appears in Nutshell's Contact record.

Rechat custom properties on Companies map to Account-level custom fields in Nutshell. Similar to Contact custom fields, we create the field in Nutshell before migration, verify it appears in the Account record during the sample phase, and populate values from Rechat during the full migration run.

If Rechat tracks lead status or lifecycle stage as a custom property on People, we map those values to Nutshell's Lead Status pick-list (New, Contacted, Qualified, etc.) via a value-mapping table. Values with no Nutshell equivalent are stored as a custom field (Legacy_Status__c) for reference and reporting continuity.

Rechat Flows (automated touch reminders, follow-up sequences, celebration automations) do not migrate to Nutshell. They must be rebuilt in Nutshell's automation tools (personal email sequences, task triggers). We export Rechat Flow definitions as a JSON blueprint during discovery so your Nutshell admin has a reference document for the rebuild.