Migrate from OptifiNow to Nutshell

OptifiNow Contact records map directly to Nutshell Person. Standard fields (name, email, phone, address) migrate 1:1. Activity history (calls, emails, meetings, tasks) attached to the Contact migrates as Nutshell Activity records linked to the Person. Any custom fields on the OptifiNow Contact object are enumerated during discovery and mapped to Nutshell custom fields on the Person record; Nutshell supports Text, Long Text, Currency, Date, Number, Dropdown, and Checkbox custom field types per its Help Center documentation.

OptifiNow Account records map to Nutshell Company. HubSpot-style Account hierarchy (parent-child) maps to Nutshell's Company parent field if present. The Account-to-Company mapping must complete before Contact import because Nutshell Person records optionally link to a Company via a lookup field. We resolve the Company reference at migration time using account name or domain as the dedupe key.

OptifiNow's Lead Management module maps to Nutshell Lead. Lead source, status, assignment rules, and any custom status fields migrate to Nutshell's Lead object. Nutshell Leads have a separate lifecycle from Person/Company; we flag any OptifiNow contacts that were sourced as marketing leads versus sales-qualified contacts so the customer can decide whether to import them as Leads or People in Nutshell.

OptifiNow Opportunity records map to Nutshell Deal. Deal value, probability, expected close date, and pipeline stage name migrate directly. Nutshell Deal pipelines are configurable; we create the destination pipeline stages during migration setup and map OptifiNow stage names to Nutshell stage names using the customer's stage mapping document produced during discovery.

OptifiNow lead assignment and routing rules are tenant-specific workflow definitions that do not export as runnable logic. We document the routing logic (criteria, round-robin groups, territory assignments) during discovery and produce a written description of the OptifiNow routing rule structure. Nutshell's lead assignment rules are configured in Settings; the customer's admin rebuilds them post-migration using our documented rule map as the specification.

OptifiNow stores email sequences, triggers, and delays as internal workflow definitions that cannot be extracted as runnable automation packages. We export sequence templates as plain-text documentation including trigger conditions, step order, delay durations, and conditional branches. The customer rebuilds sequences in Nutshell's Workflow Rules or uses a dedicated sales engagement tool (Outreach, Salesloft) if continuous cadence is required. This limitation is disclosed upfront so planning effort is accounted for.

OptifiNow's content management module stores marketing collateral, social media materials, blogs, and images. Binary file assets migrate as Attachments on the relevant OptifiNow Contact, Account, or Opportunity record. Approval workflow associations and scheduling metadata are not exportable and are not migrated. We document which content library assets have associated engagement data (emails sent with attachments, collateral linked to deals) so the customer can assess what needs to be re-uploaded to a new content management system.

OptifiNow exposes custom object support via API, but the schema is not publicly documented. We perform a pre-migration schema discovery pass during the scoping phase to enumerate all custom object types and their field definitions. Each discovered OptifiNow custom object is then mapped to Nutshell either as additional custom fields on the nearest standard object (Person, Company, Deal, Lead) or as a separate related record structure if the cardinality requires it. Nutshell's custom field API supports the same data types as its UI-configured fields. Schema discovery is required before final mapping decisions are made.

OptifiNow activity logs (calls, emails, meetings, social interactions) linked to Contacts and Accounts migrate to Nutshell Activity records. Each Activity record is linked to the migrated Person or Company by resolving the source contact or account reference. Call duration, disposition, and recording URL from VOIP-integrated calls migrate to Nutshell Activity custom fields. Note: Nutshell's API does not support searching by custom field values (Stack Overflow documentation, 2014), so any custom field lookups during migration use the primary key reference rather than a custom field match. Engagement history is migrated as a chronological activity list ordered by the original OptifiNow timestamp.

OptifiNow User records with role assignments and territory assignments map to Nutshell User accounts. We resolve OptifiNow owners by email match against Nutshell User email addresses. Any OptifiNow Owner without a matching Nutshell User is placed in a reconciliation queue for the customer's admin to provision the User in Nutshell before record import resumes. Territory and role assignments are documented as text notes on the User mapping record for the customer to configure post-migration.