Migrate from Delivra to Nutshell

Delivra Contact records migrate directly to Nutshell Person records. The email address is the primary key and dedupe field. Standard properties including first name, last name, phone, address, and custom fields map to equivalent Nutshell Person custom fields. Subscription status and GDPR consent flags migrate to Nutshell's email consent fields. Owner assignment migrates by resolving the Delivra owner email against Nutshell team member accounts.

Delivra Company records map to Nutshell Organization. The company name is the Organization name field and serves as the dedupe key. Website, address, and industry properties migrate directly. We create Organizations first in the migration sequence so that the Person-Organization relationship is satisfied at the time of Person insert.

Delivra Deals map to Nutshell Deals. The deal name, value, stage, and close date migrate directly. Delivra's pipeline assignment maps to Nutshell's Deal pipeline configuration. If Delivra uses multiple deal pipelines, we map each to a separate Nutshell pipeline or document the configuration requirement for Nutshell admin setup. Owner assignment resolves via email matching to Nutshell team members.

Delivra Custom Tables with 1:1, 1:many, and many:many relationship types do not map directly to Nutshell because Nutshell does not support relational custom objects except on Enterprise ($79/user/month). We flatten Custom Table schemas into Nutshell custom fields. For 1:1 tables, each column becomes a custom field on the related Person or Organization record. For 1:many and many:many tables, we denormalize the foreign key relationships into comma-separated or multi-value custom fields, or we document the restructure as a post-migration data architecture recommendation. If the customer licenses Nutshell Enterprise, custom objects are available for more faithful relational migration.

Delivra Campaign records are documented as a written inventory during migration scoping. Nutshell does not have a native campaign record equivalent in its base CRM tiers. We export campaign names, targeting criteria, associated content, and status. The customer admin rebuilds campaigns in Nutshell Engagement (available as an add-on) or documents a third-party marketing automation tool for ongoing campaign execution. We do not migrate campaign email content as a functional record.

Delivra Automated Workflows are documented as a written inventory including triggers, conditions, time delays, decision branches, and action sequences. Nutshell does not have a native visual workflow builder in its base CRM. Automation capabilities are available through Nutshell Engagement (an add-on suite) or via Zapier and API integrations. We deliver a structured workflow map with recommended Nutshell Engagement equivalents for each active workflow. The admin rebuilds them post-migration; this is not included in the migration scope.

Delivra email templates built with the drag-and-drop editor are exported as HTML and stored as Note records attached to the related Person or Organization in Nutshell. Complex templates with conditional content blocks, dynamic personalizations, and multi-column layouts may require re-creation in Nutshell's template editor or a third-party tool. We flag templates with advanced formatting for manual review during the handoff phase.

Delivra User accounts migrate as a role-inventory document. Nutshell team members are provisioned directly by the customer admin from the Settings > Team section. We export user names, emails, and role assignments from Delivra and deliver a role mapping table. Role structures differ between platforms so the admin recreates permissions in Nutshell based on the inventory.

Click tracking, open tracking, and engagement history from Delivra migrate as Activity records in Nutshell linked to the corresponding Person. Individual contact-level engagement metrics (total opens, total clicks, last engagement date) migrate as custom fields on the Person record for reporting and segmentation use in Nutshell. Full engagement timestamps are preserved as Activity records ordered by the original Delivra timestamp.