Migrate from Reach to Nutshell

Reach Contact records map to Nutshell Person records. We extract all visible columns from the Reach CSV export at discovery time and match each to a typed Nutshell Person field (First Name, Last Name, Email, Phone, Address). Any column not matching a standard Nutshell field is treated as a custom Person field and provisioned in the destination before import. The Reach contact's primary identifier is preserved as an external ID field for dedupe and reconciliation.

Reach's custom property model is not publicly documented, so we discover the full column set by comparing the export against a baseline Reach contact export. Each custom column maps to a Nutshell custom Person field created with the matching data type (text, number, date, dropdown). Where Reach stores company data as contact properties (a common pattern given Reach's lack of a documented Company object), we extract those values and create Nutshell Organization records, linking each Person to its Organization via the standard People-Organizations relationship.

Reach supports playlist and screen content tied to contacts or accounts. We extract media assets as attachment-like records and associate them with the nearest Nutshell Person or Organization via file attachment. Where Reach stores media as URLs or references rather than binary files, we store the URL as a custom text field on the related Person record. Nutshell's file attachment support handles document-style media; video or playlist content that requires specific playback infrastructure does not migrate as a functional equivalent.

Labels or tagging functionality is implied by Reach's content management workflows. We extract any tag-equivalent column from Reach exports and apply them as Nutshell Tags on the related Person record. Tags are stored as a comma-separated text column in Reach; we split them and create individual Tag records in Nutshell, associating each tag with the migrated Person.

Reach Enterprise tier documents seat-based licensing with reassignable admin accounts. We extract User records with name, email, and role status from the Enterprise portal and map them to Nutshell Users. Owner assignment on migrated Person records resolves by matching the Reach user email to the Nutshell User email. Any Reach user without a matching Nutshell User is held in a reconciliation queue for the customer to provision before record import resumes.

No distinct Company or Account object was found in Reach's documented schema. If the customer has structured organization data in Reach, it is stored as contact-level properties (company name field, domain, billing address). We extract these into Nutshell Organization records during the Person migration, creating the Organization before the Person so that the link is satisfied at insert time. This prevents orphaned Person records in Nutshell.

The Reach export documentation makes no mention of activity history, call logs, meeting records, or engagement timestamps. We do not migrate activity data unless a full column export confirms its presence. Where customers report engagement history in Reach's interface, we treat it as discovered evidence and attempt extraction; if no export column surfaces it, we document it as not migratable and flag it in the scope document for the customer's awareness.

No integration endpoints, webhook documentation, or third-party connector schema were found for Reach in available research. We treat existing integrations as out of scope. We deliver a written inventory of any third-party tools the customer has connected to Reach (identified during scoping) and recommend the equivalent Nutshell integration path. Nutshell's native AppConnect and Zapier ecosystem typically covers the replacement integrations.