Migrate from Oncord to Nutshell

Oncord Contacts map 1:1 to Nutshell Contacts. Standard fields (name, email, phone, address) map directly. The Oncord activity feed migrates as Nutshell Activities (calls, emails, meetings, tasks) linked to the Contact record. We preserve original created_date and last_modified timestamps as custom fields for audit. Oncord's Owner field (the user who created or owns the contact) maps to Nutshell User via email match.

Oncord Groups function as static segmentation lists and map to Nutshell Tags or Nutshell Lists depending on usage. Groups used for contact classification (industry tags, account segments) map to Tags. Groups used for campaign targeting (email list segments) map to Nutshell Lists. We export all Groups and let the customer choose the target structure during scoping, or default to Tags if the usage is mixed.

Oncord exposes CustomFields via its internal API component. We extract all custom field definitions (name, type, options) and create matching Nutshell custom fields before migration. Type mapping handles text, number, date, and dropdown fields. Multi-select picklist values in Oncord map to Nutshell dropdown fields; we document any dropdown values that require manual setup in Nutshell before data loads.

Products migrate only when the Commerce add-on ($40/month) is active on Oncord. We export product name, description, price, SKU, inventory count, images, and any custom product fields. Products map to Nutshell Products. If Nutshell Products are not active on the destination account, we flag this during scoping because Products require a feature activation step in Nutshell settings before import.

Oncord Events include RSVP functionality and attendee lists linked to Contacts. Event name, date, location, and capacity migrate to Nutshell Events. Attendee lists migrate as Activity records linked to the attending Contact records, with the Event name stored as a custom field on each Activity for cross-referencing. Events migrate only when the Marketing add-on ($40/month) is active.

Oncord discount rules and coupon codes are not migrated as active records because Nutshell does not have a native discount or coupon object at the CRM layer. We export the discount rules, coupon codes, eligibility conditions, and usage limits as a written inventory document that the customer's admin can use to configure equivalent rules in their e-commerce or payment platform.

Oncord Users map to Nutshell Users via email match. We export name, email, and role for every Oncord user. Oncord's unlimited admin users on base plans maps to Nutshell's user-based licensing. Owner assignment on Contacts and Deals resolves to Nutshell User records at migration time; any Oncord Owner without a matching Nutshell User goes to a reconciliation queue for the admin to provision before record import.

Oncord Automation Workflows trigger on contact activity, group membership, or time-based schedules. We document the full workflow structure (trigger, conditions, actions, delays) as a written inventory with each step described in plain language. The customer uses this inventory to rebuild equivalent rules in Nutshell's workflow rules (available from Pro tier). Workflow documentation is delivered as a structured spreadsheet with trigger type, condition logic, and recommended Nutshell equivalent.