Migrate from RAYNET CRM to Nutshell

RAYNET Contact records map to Nutshell Person records. Standard fields (name, email, phone, address) migrate 1:1. RAYNET's auto-derived GPS coordinates from Map Analysis store as two custom number fields (latitude and longitude) in Nutshell since Nutshell has no native GPS derivation. Lifecycle stage from RAYNET migrates as a custom picklist field for reporting continuity.

RAYNET Account records map to Nutshell Company records. The Account name becomes Company name, and the primary contact address migrates as the Company address. Account is created before Contact import so that the Person-Company relationship is resolved at the moment of Person insert.

RAYNET Deal records map to Nutshell Deal with deal name, value, stage, owner, and estimated close date preserved. If the RAYNET source account is on START or PROFESSIONAL tier (single pipeline), we map the pipeline directly to Nutshell's single pipeline. If ENTERPRISE with multiple pipelines, we use the primary pipeline for import and flag excess pipelines for the customer's admin to restructure in Nutshell post-migration.

RAYNET pipeline stage names and probabilities map to Nutshell Deal stage values. Stage order and probability percentages migrate from RAYNET to Nutshell's stage configuration. If the RAYNET account uses deprecated or inactive stages, we flag them during scoping to avoid importing stale pipeline state.

RAYNET call activity records map to Nutshell Call records linked to the migrated Person or Company. Call duration, disposition, and timestamp preserve. We resolve the activity's linked contact and account references using the cross-record ID map built during the parent import phase.

RAYNET email activity records map to Nutshell Email records with subject, body, and timestamp. The email is linked to the migrated Person or Company using the lookup resolution built during scoping. Attachments on email records migrate as file attachments on the corresponding Nutshell record.

RAYNET meeting activity records map to Nutshell Meeting records with start time, end time, location, and attendees preserved. Meeting attendees are resolved against the migrated Person ID map and linked accordingly.

RAYNET Quote records map to Nutshell Quote records with subject, validity dates, line-item pricing, and linked Account preserved. Quote line items migrate as JSON-encoded custom fields or as a structured note attached to the Quote record depending on Nutshell's schema support at the time of migration. We flag this during scoping and confirm the exact storage approach.

RAYNET Sales Order records map to a Nutshell custom object with Subject, Final Price, Status, Estimated Costs, Delivery Date, and address fields preserved. Address fields transform from RAYNET's structured address model to Nutshell's address format. We create the destination custom object schema before import begins.

RAYNET User records with role assignments and deal ownership map to Nutshell Users. We resolve owners by email match against the Nutshell destination account. Any RAYNET Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

RAYNET tags on Contacts and Deals migrate to Nutshell tags. If Nutshell's tag model does not support the full tag taxonomy, we offer to store tags as a custom multi-select field on Person and Deal. The customer chooses the strategy during scoping.

RAYNET custom fields on Contact, Account, Deal, and Activity objects migrate to Nutshell custom fields of equivalent type. We extract the RAYNET custom field schema via list export and map each to a typed Nutshell field. If no direct type match exists, we store the value as a custom text field. Custom fields are deployed to Nutshell before any record import begins.