Migrate from Data Team DDS to Nutshell

N:N contact-company associations require a primary-company resolution rule

Data Team DDS supports N:N contact-to-company associations — a single contact can link to multiple organizations. Nutshell Person records link to one primary Company. FlitStack AI applies a configurable primary-company rule (most-recently-modified company by default, or your specified ranking) and surfaces secondary company associations in a custom field on the Person record so no association data is silently dropped during migration. If your team uses multi-company association labels (e.g., Primary Account, Partner), those labels migrate as custom field values.

Multiple Data Team DDS pipelines map to a single Nutshell pipeline with a segmentation field

Data Team DDS setups with two or more independent deal pipelines do not have a native equivalent in Nutshell's single-pipeline model. FlitStack AI maps each Data Team DDS pipeline to Nutshell stage names within one pipeline, and creates a Source_Pipeline__c custom field on the Deal record to preserve the original pipeline name. This lets your sales team filter by the original pipeline in Nutshell's reporting views without needing a custom object or multi-pipeline extension. Pre-create your target Nutshell pipeline stages with matching stage names before migration validation runs.

Workflows and automation rules do not migrate and must be rebuilt in Nutshell

Data Team DDS workflow rules, triggers, assignment rules, and approval processes are platform-specific configurations that have no equivalent in Nutshell's data model. FlitStack AI does not migrate automations — this is a platform-level limitation that applies to every migration. We export your Data Team DDS workflow definitions as a reference document (including trigger conditions, rule criteria, and action definitions) so your Nutshell admin can rebuild them using Nutshell's automation tools. Schedule the rebuild as a separate workstream from the data migration to avoid go-live delays.

Custom fields with formula or rollup types become static values in Nutshell

Data Team DDS custom fields may include formula fields, rollup summary fields, and lookup relationships that calculate values dynamically. Nutshell custom fields are static field types — a formula field in Data Team DDS cannot function as a formula in Nutshell and must be evaluated at migration time. FlitStack AI evaluates formula field values from the source record at migration time and writes the resulting value as a static Nutshell custom field. Lookup fields map to a text representation of the referenced record ID. Both transformations are documented in the field-level diff before the full run commits.

Email body content migrates as Activity records; inline attachments follow a separate upload path

Data Team DDS stores email body content and inline attachments linked to contact activity records. Nutshell's email integration captures subject, timestamp, and owner, but inline attachments require a separate re-upload to Nutshell Files after the contact records are in place. FlitStack AI migrates the email Activity record with subject, timestamp, and owner preserved, and queues inline attachments for a second-pass file upload that attaches each file to the parent Activity record in Nutshell. File size limits and supported formats follow Nutshell's file upload specifications.