Migrate from ActiveDEMAND to Nutshell

ActiveDEMAND Contacts map directly to Nutshell People (Contact equivalent). Standard fields (firstname, lastname, email, phone, mobilephone, jobtitle) migrate 1:1. Brand Custom Fields require schema translation first—see gotchas on Brand Custom Field schemas. Community assignment from ActiveDEMAND's multi-tenant structure migrates as a tag on the Nutshell Contact record if no custom field alternative is configured.

ActiveDEMAND Companies map to Nutshell Accounts. Company name becomes Account name; address fields map to the Account address block. Nutshell Accounts do not support separate billing and shipping addresses, so ActiveDEMAND's address maps to the primary Account address.

ActiveDEMAND Call Tracking records (source number, destination number, duration, recording URL, disposition) migrate to Nutshell Activity records of type Call linked to the Contact. Recording URLs migrate as a link field on the Activity. Duration in seconds maps to a custom Activity duration field or the notes field.

ActiveDEMAND website chat conversations migrate as Nutshell Notes or Activity records linked to the Contact. Message timestamps, direction (inbound/outbound), and content body transfer. Nutshell does not have a native conversation thread object, so chat history appears as a chronological note entry.

ActiveDEMAND Appointments and Tour bookings migrate to Nutshell Activities with the original date, time, status (scheduled, completed, cancelled), and linked Contact preserved. If the appointment has a community reference, that value migrates as a tag or custom activity field.

ActiveDEMAND Campaigns migrate to Nutshell Campaigns with campaign name, status, and start/end dates preserved. Campaign membership (which contacts are in which campaigns) migrates as Nutshell Campaign Members. Campaign type distinction (email vs funnel vs event) is preserved in a custom Campaign field because Nutshell uses a single Campaign object type.

ActiveDEMAND Contact Lists and Segments are preserved as Nutshell Tags. We export each list's contact ID membership, then assign the corresponding tag to each Contact record in Nutshell. Static lists become direct tag assignments; dynamic segments are documented for manual rebuild as Nutshell static groups.

ActiveDEMAND Brand Custom Fields require schema translation before Contact import. We export the custom field definition (name, type, picklist values if applicable) from the source account, then create equivalent Nutshell custom fields using Nutshell's custom field management UI. Field types map (ActiveDEMAND text to Nutshell Text, picklist to Nutshell Dropdown, date to Nutshell Date, checkbox to Nutshell Checkbox).

ActiveDEMAND Automated Workflows do not migrate as automation code. We export workflow names, step counts, trigger conditions, and action summaries as a written inventory document. Nutshell does not have a native workflow builder on its base plans; the customer's admin rebuilds triggers as Nutshell Tasks or documents them for a future automation layer (e.g., Zapier, Make).

ActiveDEMAND Funnels map to Nutshell Pipelines and Stages conceptually. We export funnel names, stage definitions, and Contact-stage assignments as a written inventory. Stage labels map to Nutshell pipeline stage names during scoping. Nutshell Pipelines and Stages are configured by the admin post-migration.