Migrate from RETAINUSER CRM to Nutshell

RETAINUSER Contacts map to Nutshell People (the unified Contact and Lead object). Standard fields (name, email, phone, address) migrate 1:1. The RETAINUSER contact-to-company linkage is preserved by resolving the company external ID on the Person record during import. Custom properties on Contacts require field-level type mapping and field name alignment against Nutshell's allowed custom field names.

RETAINUSER Leads from Facebook Forms, WhatsApp, and manual entry split into Nutshell's Lead object (for unqualified prospects) or directly into the Person object (if the lead is already vetted). We apply a split rule based on the lead status and source fields at migration time. Lead status, lead source, and owner assignment migrate as custom or standard fields on the destination record.

RETAINUSER Company records map directly to Nutshell Company. The company domain, industry, size, and address fields migrate 1:1. Nutshell Company records must exist before the Person import so that the person-to-company association is satisfied at the time of Person insert. We export the association table from RETAINUSER and reconstruct it in Nutshell using the company external ID.

RETAINUSER Deals map to Nutshell Deals. Pipeline stages from RETAINUSER map to Nutshell pipeline stage values that we configure before migration. Deal value, currency, expected close date, owner, and any custom properties migrate directly. Deals without an owner are flagged for the customer's admin to assign after migration.

RETAINUSER pipelines with configurable stages map to Nutshell Pipelines with stage names and order preserved. Nutshell Foundation is limited to one pipeline; Pro and above support unlimited pipelines. We configure the destination pipeline structure during schema setup and map RETAINUSER stage names to Nutshell stage keys before the Deal import begins.

RETAINUSER Activities (calls, emails, meetings, notes) logged against a Contact, Company, or Deal migrate to Nutshell Tasks with activity type preserved. Timestamps, owner attribution, and note body content transfer directly. Call duration and disposition migrate as custom fields on the Task. Activity linkage to the parent Person or Deal is resolved by external ID lookup at migration time.

RETAINUSER email templates migrate as text assets with subject line and body preserved. Merge field placeholders (RETAINUSER's proprietary syntax) are flagged and mapped to Nutshell's merge field format during the template import. We do not preserve template-to-contact associations; these are documented separately for the admin to reassign.

RETAINUSER SMS and WhatsApp templates migrate as text content with character limits noted. Nutshell's Engagement Suite SMS templates use a different placeholder syntax; we transform the template bodies during import and flag any personalization tokens that require remapping. Template associations to workflows are not preserved.

RETAINUSER custom fields on Contacts, Companies, and Deals require field-level type mapping against Nutshell's custom field schema. We extract the full custom field definition including field type, picklist values, and default values, then pre-create the equivalent Nutshell custom fields before record migration. Picklist values are mapped explicitly; free-text fields map directly.

RETAINUSER Users and Deal owners map to Nutshell Users by email match. We extract the full user list with name, email, role, and active/inactive status. Inactive RETAINUSER users are flagged to be archived in Nutshell rather than migrated as active seats. Any owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before the Deal import resumes.