Migrate from Ready_ to Nutshell

Ready_ Contact records map to Nutshell Person. Standard fields (name, email, phone, address, job title) map directly. Custom properties on contacts migrate as custom fields in Nutshell, which we pre-create per object type before import. Ready_ contact-to-company association links via the Company ID field, which we resolve to the Nutshell Company record created in the preceding phase.

Ready_ Company records map to Nutshell Company with direct field mapping for name, domain, industry, and size. The company domain becomes the Nutshell Company domain field and is used as the dedupe key. Related contacts are linked via association records after both objects are present in Nutshell. We create Companies first to satisfy the lookup dependency when importing Persons.

Ready_ Deals attach to a named Pipeline and Stage. We map deal value, expected close date, owner, and stage name. Nutshell treats Deals as Leads or Person-level records depending on pipeline configuration. We resolve the target Nutshell pipeline and stage during scoping, then attach the deal to the matching Person record or create a Lead from the deal during migration. Closed-won and closed-lost reasons map to Nutshell status fields.

Ready_ allows custom-named pipelines and stages with no enforced naming convention. We extract the full pipeline configuration from Ready_ during discovery, then create matching Nutshell pipelines and stage definitions before migrating any deal records. Without this step, deals land in a default pipeline or are orphaned. The stage sequence order from Ready_ is preserved in Nutshell stage ordering.

Ready_ Activities (calls, emails, tasks) map to Nutshell Tasks linked to the corresponding Person record. We map activity type, timestamp, notes, and owner. Ready_ activity types may not map 1:1 to Nutshell's task schema, so we preserve the original Ready_ activity type in a custom field on the Nutshell Task for audit and reporting continuity.

Ready_ Notes are standalone records attached to Contacts or Deals. We map the note body, linked record type, and linked record ID to Nutshell Note records. The note is linked to the corresponding Person record in Nutshell using the association metadata extracted from Ready_. Long-text note bodies migrate as-is; notes exceeding Nutshell's display limits are preserved in full and accessible via record detail.

Ready_ custom fields on Contacts, Companies, and Deals (text, number, date, picklist types) migrate to Nutshell custom fields of equivalent type. We extract the full custom field definition during discovery, create matching Nutshell custom fields per object before the data migration phase, and then import values. Picklist values from Ready_ become Nutshell drop-down option sets. Custom fields that do not have a direct Nutshell equivalent are preserved as text fields with a note in the migration log.

Ready_ Team Members represent users, and deal and activity ownership references Team Member IDs internally. These IDs have no meaning in Nutshell. We resolve Team Member IDs to email addresses during extraction, then match those emails against existing Nutshell user records. Unmatched owners are flagged in a reconciliation queue; the customer's Nutshell admin provisions any missing users before record import resumes. This two-step resolution prevents silent ownership gaps where migrated records have no assigned owner.