Migrate from Tubular CRM to Nutshell

Export preparation and dependency sequencing

We coordinate with the customer to schedule Tubular CSV exports in dependency order: Organizations (Companies) first, then People (Contacts), then Leads, then Opportunities (Deals), then Activity logs last. This order preserves referential integrity because Nutshell requires the Organization to exist before the Person can be linked to it. For Enterprise-tier customers, we test API connectivity, enumerate available endpoints, and map field names before relying on API-based extraction. Pro-tier customers receive a detailed export guide with screenshots and a checklist to ensure all relevant fields are included in each CSV download.

Schema discovery and field mapping

We audit the Tubular export for all objects, custom fields, pipeline stages, tags, and owner assignments. We then design the Nutshell destination schema, including custom fields on Person, Organization, Opportunity, and Lead objects (subject to the customer's Nutshell plan limits). We map Tubular field names to Nutshell field API names, flag any Tubular fields with no Nutshell equivalent, and decide with the customer whether those fields are recreated as custom fields or dropped. Stage names and probabilities are mapped to the customer's chosen Nutshell pipeline configuration.

Custom field and pipeline configuration in Nutshell

We create all required custom fields in Nutshell before any data import begins. Pipeline stages are configured with the customer's chosen names and probability percentages. Tags are initialized as a flat taxonomy that will be applied during the Opportunity and Person import phases. Nutshell plan limits on custom field counts are verified against the destination tier; if the customer's plan constrains custom fields, we prioritize the highest-value fields and document any that require an upgrade to include.

Sandbox import validation

We run a test import into a Nutshell trial or sandbox environment using a representative sample of the exported data (typically 50-100 records per object). The customer reviews the imported records against the source, validates field mappings, confirms that Organization-Person links are resolved correctly, and signs off before production migration begins. Any mapping corrections happen here. For Enterprise Tubular customers with API access, we also test the API export against the documented Nutshell API import endpoints at this stage.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (validated from owner email list), Organizations (from Tubular Companies), People (from Tubular Contacts, linked to Organizations), Leads (from Tubular Leads), Opportunities (from Tubular Deals, linked to People and Organizations), Tags (applied to Opportunities and People), Tasks (linked to the appropriate parent record), and Activity logs (emails, calls, notes linked to Person or Organization). Each phase emits a row-count reconciliation report before the next phase begins. Pro-tier exports that produce malformed activity CSVs are cleaned and retried before proceeding.

Cutover, validation, and automation handoff

We freeze Tubular writes during cutover, run a final delta import of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a reconciliation report comparing Tubular record counts to Nutshell record counts for every object. We also deliver the Tubular Deal Stage Trigger and Email Template inventory (if applicable) for the customer's admin to rebuild as Nutshell automation. We do not rebuild automations or rebuild Nutshell reports from Tubular's view-only report data; those are manual post-migration tasks documented in the handoff package.