Migrate from Bolten CRM to Nutshell

Bolten Contact records map to Nutshell People. The contact's name, primary email, phone numbers, address, and assigned tags transfer directly. Custom fields on the Contact object map to Nutshell custom fields on People; we pre-create Nutshell custom fields with matching types (text, number, date, dropdown, multi-select) before import so field mapping is type-compatible from the first load.

Bolten Lead records (separate from Contacts in Bolten) map directly to Nutshell Leads with lifecycle status, source campaign attribution, and owner assignment preserved. Lead source and owner email resolve to the Nutshell user by email match during import. Leads and People are managed separately in both platforms, so no split logic is required.

Bolten Kanban Deals map to Nutshell Opportunities. The most migration-critical step is stage ordering: Bolten uses free-text stage names with no enforced ordinal in the API, while Nutshell uses a configured stage picker with explicit ordering. We ask the customer to confirm the intended stage sequence during scoping, write the ordinal position explicitly into Nutshell during schema setup, and map Bolten stage names to Nutshell stage values by that confirmed order. Deal value, close date, and owner assignment transfer directly.

Each Bolten Kanban pipeline becomes a Nutshell pipeline with ordered stage values. We configure Nutshell stages before migration with the customer's confirmed stage names and sequence. Stage probability percentages (if configured in Bolten) transfer to Nutshell's stage probability settings.

Bolten Tasks migrate to Nutshell Tasks with assignee, due date, status, and linked contact or deal preserved. Recurring task rules in Bolten do not transfer; we flag them in the handoff document for the customer's admin to rebuild in Nutshell's task automation.

Bolten activity audit logs (every record change, assignment, and stage move) transfer as Nutshell Activity records attached to the relevant People, Company, or Opportunity. Each activity carries the timestamp and operator from Bolten's audit trail so the full change history is preserved in the destination timeline.

Bolten custom fields per object (text, number, date, dropdown, multi-select) map to Nutshell custom fields on the equivalent object. We pre-create the destination custom fields before import, converting Bolten field types to Nutshell-supported types. Any Bolten custom field with no direct Nutshell equivalent is flagged during scoping with a recommended handling approach.

Bolten users are identified by email and name. We map Bolten user emails to Nutshell user emails during import. Suspended or inactive Bolten users are flagged for remapping to active Nutshell users so that no record is assigned to a deactivated destination user.

Bolten flat-label tags applied to contacts and deals transfer as Nutshell tags with the tagging relationship per record preserved. Tags are string values in both platforms, so no type conversion is required.