Migrate from ActiveTrail to Nutshell

ActiveTrail Contact maps directly to Nutshell Person. Each contact's email address, first name, last name, phone number, and custom field values migrate to the corresponding Nutshell Person fields. We use email as the dedupe key. The original ActiveTrail contact ID is preserved in a custom field at_nutshell_source_id__c for audit and reconciliation.

ActiveTrail contacts store an optional company name rather than a structured account relationship. We derive Nutshell Company records from all distinct company_name values across the contact base, then link each Person back to the resolved Company using the company field as a lookup key. If a contact has no company name, it is imported as a Person with no Account link and flagged for manual review.

ActiveTrail behavioral tags migrate as flat string labels applied to the corresponding Nutshell Person records. Nutshell natively supports tagging on People and Companies. Tags used for segmentation are also exported as a standalone tag inventory so the customer's admin can rebuild ActiveTrail segments as Nutshell static lists or dynamic People searches.

ActiveTrail segments are dynamic contact groups built on filter conditions. Segment definitions (rule sets and filter logic) are exported as a written rule inventory. Nutshell does not have a dynamic segment equivalent, so we rebuild segments as static Nutshell People Lists using the exported contact IDs or rebuild them as saved People searches using Nutshell's filtering UI post-migration.

ActiveTrail contact custom fields (text, number, date, dropdown) are mapped to Nutshell custom fields on the Person object. Dropdown fields in ActiveTrail require value mapping to Nutshell custom field picklist options. We create all destination custom fields in Nutshell before any contact import to ensure the import file maps cleanly to the defined schema.

ActiveTrail email campaign metadata (campaign name, send date, audience size, subject line) migrates as Nutshell Campaign records. Campaign engagement history (open events, click events) migrates as Task notes on each Person record with a reference to the related Campaign. This preserves the record of who engaged with which campaign without requiring Nutshell's native campaign reporting.

ActiveTrail SMS campaign metadata migrates to Nutshell Campaign records with SMS noted in the campaign description. Individual SMS send events and delivery confirmations migrate as Task notes on each Person. Nutshell has no native SMS object, so SMS engagement records appear as contact notes rather than a structured SMS log.

ActiveTrail email engagement records (subject, body, timestamp, open/click status) migrate to Nutshell Task records linked to the corresponding Person. Task.Subject carries the email subject, Task.description carries the body, and custom fields track open and click status as free text. Activity ordering is preserved by setting Task.due_date to the original engagement timestamp.

ActiveTrail automation journeys are exported as dormant workflow blueprints documenting the trigger, conditions, delay timers, and channel actions (email, SMS, WhatsApp). Nutshell has no native workflow builder, so we deliver a written reconstruction guide per journey and advise the customer's admin to rebuild them using an integration tool (Zapier, Make, or a native Nutshell integration) post-migration. Running state, enrolled contacts, and timer positions do not transfer.