Migrate from Resulticks to Nutshell

Resulticks Contact records map 1:1 to Nutshell Person. Standard fields (name, email, phone, address) migrate directly. Custom contact properties from Resulticks map to Nutshell custom fields on the Person object. We create custom fields in Nutshell (via the Accounts > Custom Fields API endpoint) before import, using type-compatible field types: Text for single-value strings, LongText for paragraphs, Currency for monetary amounts, Date for date values, and Decision (enum) for picklist-style values. Owner assignment on Contacts resolves to Nutshell Users via email lookup.

Resulticks Company records (linked to Contacts) map to Nutshell Company. Company name, phone, website, and address fields migrate directly. The Nutshell API requires that accounts have at least one of name, phone, email, address, or url. We create Company records before Person records so that the Company lookup (accountId) is satisfied at the time of Person insert, avoiding orphaned Person records with no Company association.

Resulticks Users migrate to Nutshell Users by email address match. OwnerId on Resulticks Contact, Company, and Campaign records resolves to the corresponding Nutshell User. Any Resulticks Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Resulticks users map to inactive Nutshell users with their historical assignments preserved as custom fields for audit.

Resulticks Contact-level Tags migrate to Nutshell Person custom fields using Decision (enum) type if tag values are a closed set, or as comma-delimited text in a LongText custom field if tag values are open-ended. We document the full tag vocabulary during scoping so the customer chooses the appropriate Nutshell field type. Tags that represent audience membership (e.g., VIP, Churned) become custom fields; tags used for content categorization become a single tags__c LongText field.

Resulticks audience definitions are based on Contact attributes and event conditions and do not have a direct Nutshell equivalent. We preserve audience membership by applying equivalent filter logic in Nutshell during migration, tagging each Person with the segment name in a custom field (e.g., high_value_buyer, sms_opted_in). For complex event-condition audiences that cannot be expressed as a simple tag, we create a Note record on the Person documenting the original audience criteria for manual reference and rebuild.

Resulticks Campaigns represent the top-level execution unit with channel assignment and scheduling metadata. Nutshell does not have a native Campaign object in the same sense. We migrate campaign metadata as a Note attached to the Person records that were part of the campaign audience, tagging with the campaign name, channel, and date range. Active campaign names and IDs are preserved in a custom field campaign_history__c on Person for reporting reference.

Resulticks custom fields vary by account configuration and may include legacy field types, multi-select values, or date-derived computed fields. We inspect the field schema during scoping and apply type-compatible mappings: Text (225 char max per Nutshell limit), LongText for longer content, Currency for monetary values, Date for date fields, and Decision for dropdown values. Email, location, phone, and URL field types are only applicable to Leads and People in Nutshell, not to Accounts.

Resulticks behavioral events (page views, email opens, purchase events, custom track events) can be extensive in volume and variable in schema. Due to schema variability and the absence of a native event model in Nutshell, we migrate a configurable event window (typically the last 90 days of activity) and normalize high-frequency event types into a Person Note documenting event counts and the most recent event timestamp. Detailed event history that requires granular reporting is out of scope for standard migration and is documented for a separate data warehouse integration.