Migrate from Inflection.io to Nutshell

Inflection.io Contacts map directly to Nutshell People records. Standard properties (email, first name, last name, phone, address) map to Nutshell's native Person fields. Custom Person fields (text, numeric, date/time, boolean) map to Nutshell custom fields on the Person object. The contact's original creation date and last-modified date migrate as custom date fields to preserve historical context. We resolve duplicate contacts by email dedupe during import using Nutshell's native duplicate detection.

Inflection.io Account records map to Nutshell Companies. HubSpot-style account domain, industry, employee count, and annual revenue map to Nutshell Company fields. Hierarchical parent-child account structures in Inflection map to Nutshell's parent Company lookup if the destination schema includes that relationship. We import Accounts before People so that Company lookups are satisfied at the time of Person insert.

Inflection.io Segments (built on contact properties, product events, and behavioral signals) require decomposition for Nutshell. We export segment rules and membership counts, then map active segments to Nutshell Lists and tag-based classifications. Segments built purely on contact properties map cleanly; segments referencing product events or behavioral thresholds do not map because Nutshell has no event data. For those, we flag the dependency and recommend the customer rebuild the segment logic using Nutshell's filter-based list definitions post-migration.

Inflection.io product event histories (usage events, feature adoption, PQL scores) have no native equivalent in Nutshell. We offer two migration strategies: (1) preserve summary product metrics (last login date, feature adoption counts, usage frequency flags) as custom fields on the Person record, or (2) store raw event counts as JSON in a long-text custom field. Strategy one is preferred because Nutshell's custom field querying supports numeric and date fields. Strategy two preserves raw data for future warehouse export but cannot be used for segmentation without custom reporting work. Event-level granularity (individual feature usage rows) does not migrate.

Inflection.io Journeys cannot migrate to Nutshell. Nutshell's workflow rules use a basic if-this-then-that trigger model that is not equivalent to Inflection's nested Journey builder with branching conditional logic, AI-generated content steps, and multi-step sequence orchestration. We export Journey definitions including step sequences, trigger conditions, action steps, and branch logic as a written document. The customer's admin reviews the inventory and rebuilds high-priority Journeys as Nutshell workflow rules or evaluates third-party sales engagement tools (Outreach, Salesloft) for cadence-style sequences.

Journey membership history (which contacts entered which Journeys and when) can be preserved as custom fields on the Person record (one date field per Journey indicating last entry) or as List membership in Nutshell. We map active Journey memberships to Nutshell Lists named after the source Journey. Historical entry timestamps migrate as custom date fields. This preserves audit context but does not replicate the Journey execution logic.

Inflection.io custom Person fields of type text, numeric, date/time, and boolean map to Nutshell custom fields on the Person object. Multi-select and array-type custom fields require conversion to comma-separated text in Nutshell. We preserve field labels and help text as field descriptions in Nutshell. Field type mapping is validated during the scoping phase before import.

Contact-level tags and labels in Inflection.io map directly to Nutshell's native tagging feature on People records. We preserve tag counts and apply the same tag vocabulary. Tags used for behavioral classification (derived from product events) do not transfer if the underlying event data is not migrated; we flag these as requiring manual re-tagging or a post-migration tagging workflow.