Migrate from Contlo to Nutshell

Contlo Contacts map 1:1 to Nutshell Person records. Standard properties (name, email, phone, address) map directly to Person fields. The Contlo contact's current status (subscriber, lead, customer) migrates as a custom field nut_contlo_status__c so the destination system retains the original state for segmentation and reporting. If the Contlo contact is associated with a company name, we create a corresponding Nutshell Account first and link the Person to it via the accountId reference.

Contlo Segments are behavioral groupings (abandoned cart, lifecycle stage, purchase history) stored as membership tags on each Contact. We extract segment membership and write each segment name as a Nutshell custom field on the Person record. Multi-select custom fields in Nutshell can represent contacts that belong to multiple segments simultaneously. Segment rule logic (AND/OR filter conditions) is documented separately as a written reference for the customer's admin to rebuild in Nutshell as static lists or filter views.

Contlo campaign metadata (name, type, scheduled date, send status) and aggregated engagement metrics (opens, clicks, conversions) migrate as structured data linked to the Person record via custom fields and activity notes. We export campaign templates as content records for the customer to republish in Nutshell's email templates. Native Nutshell Marketing (Marketing Pro plan at $49/month) can then use these templates for outbound campaigns. Delivery logs and open/click event counts are preserved as a CSV time-series export linked to Contact IDs for reimport into reporting if needed.

Contlo automations are event-triggered workflow sequences with conditional branching, time delays, and multi-step actions. Nutshell does not have an equivalent event-driven automation engine for marketing. We extract the full automation graph (trigger type, conditions, action steps, branch logic) and deliver it as a written inventory document. The customer's admin rebuilds automations in Nutshell's sales automation rules (available on Pro and above) or documents the rebuild scope for a Nutshell partner. This is not a data gap; it is an action item.

Contlo's brand-owned generative AI Model is a proprietary artifact trained on the customer's brand content, campaign history, and customer interaction data. It lives in Contlo's infrastructure and cannot be exported as a portable data artifact. When migrating out of Contlo, the customer must re-train or re-create the AI model in the destination system from scratch. We document this as a required manual step and note that Nutshell's AI feature (Nutshell IQ) is a prospecting intelligence tool, not a brand-trainable generative model. This is not a data gap; it is an exclusion from migration scope.

Contlo custom fields on Contacts migrate to Nutshell custom fields on Person. Nutshell supports text, long text, currency, date, and other field types for custom fields on Person, Account, and Lead. We map field types from Contlo to the nearest Nutshell type and create the custom fields in Nutshell before the Person import. Nutshell places custom fields inside a customFields dictionary in its API, which we reference during import. Note that Nutshell's API does not support searching by custom field values directly, which may limit post-migration programmatic segmentation compared to Contlo's native filter model.

Contlo Voice Agents are AI-driven phone agents built from Contlo's library with agent configuration, voice settings, and routing logic. Nutshell has no native voice agent capability. Voice Agent configuration migrates as structured data in the written inventory for the customer to evaluate Nutshell-compatible alternatives (third-party phone integrations via Nutshell's API). The agent logic itself does not map to a Nutshell artifact and requires reconfiguration in the destination system.

Event-level data (opens, clicks, conversions, purchases) exports from Contlo as a time-series CSV linked to Contact IDs. We preserve this as a structured export with Contact email as the join key, enabling the customer to import engagement history into Nutshell as custom activity records or as a linked analytics dataset. Nutshell's activity timeline on Person and Account records can display engagement history if the customer imports event data as Note records with a standardized date and description format.