Migrate from RedEye to Nutshell

RedEye contacts map directly to Nutshell People. The primary contact identifier (email address) serves as the dedupe key during import. We preserve RedEye contact properties as custom fields on the People record, including any behavioural attributes, source channel, and lifecycle stage data. If the customer uses RedEye's contact deduplication logic, we apply equivalent deduplication rules in Nutshell during import to prevent duplicate People records.

RedEye's lightweight company association (where it exists in the contact model) maps to Nutshell Account. The mapping is loose because RedEye is B2C-first and company linkage is secondary; many RedEye contacts may not have a company record. We flag records missing a company association and offer two approaches: create placeholder Accounts from contact domain data, or link People to a single master Account. The customer selects during scoping.

RedEye campaigns do not have a direct Nutshell equivalent because Nutshell campaigns are part of the integrated Marketing suite (separate from the core CRM objects). We map RedEye campaigns to Nutshell Leads with a custom field redeye_campaign__c carrying the original campaign name, so the customer's sales team can trace a Lead back to the originating RedEye campaign source. If Nutshell Marketing is active, campaign records migrate to Nutshell Campaign objects.

RedEye product catalogue records (SKU, name, pricing, category) migrate to Nutshell Products if the destination Nutshell account includes the Quoting tool. Products require the customer to confirm that Quoting is active on their Nutshell plan before migration. If Quoting is not active, we preserve product data as a custom field on the relevant People or Deal record for manual reference.

RedEye behavioural events (website actions, email opens, purchase triggers) migrate as Nutshell Activity records (Tasks and Notes) attached to the People record. We preserve the original event type and timestamp as custom Activity fields so that the enrichment signal from RedEye is visible in Nutshell without requiring the original platform. High-volume event logs may require chunking; we flag this during scoping.

RedEye custom contact and event fields require explicit field-to-field mapping during scoping. We extract the full RedEye field schema, classify each field by data type (text, date, number, multi-select), and map to equivalent Nutshell custom field types. Multi-select and checkbox fields in RedEye map to Nutshell multi-select picklist or tag arrays depending on field cardinality. Custom field schema is pre-created in Nutshell before record import begins.

RedEye dynamic segments (behavioural rule sets) do not have a live Nutshell equivalent because Nutshell segments are manual tag-based groups rather than rule-driven dynamic lists. We export segment definitions as written rule documents, map segment membership to Nutshell Tags on the People record, and note which RedEye behavioural triggers (purchase, page view, email open) require manual Nutshell tagging or the Nutshell Workflow equivalent for future rebuild.

Contact and campaign tags migrate as a flat tag array on the People record in Nutshell. We map tag names exactly and flag any characters unsupported by Nutshell's tag schema (special characters beyond alphanumerics, hyphens, and underscores). Tag count is preserved to support any segmentation logic the customer rebuilds in Nutshell manually.

Campaign assets (images, documents attached to emails or campaigns) and contact attachments migrate via file export and re-upload to Nutshell. We preserve the file hierarchy and naming conventions, and link attachments to the relevant People record using Nutshell's attachment model. URL-based assets (hosted images in RedEye email templates) require the customer to re-host or upload to Nutshell's file storage manually.