Migrate from APTANIA CRM to Nutshell

Scoping and export preparation

We audit the APTANIA portal for record counts across Contacts, Companies, Deals, and Activities. We check the Basic plan record ceiling and flag any customer whose total record count exceeds 1,000. We provide the customer with a written export guide specifying the exact in-platform export paths, file format (CSV or JSON), and field selection required to capture all relevant data. We ask the customer to confirm that the exported files include all required fields before upload. Any custom properties visible in the APTANIA UI but absent from the export are flagged for manual field recreation in Nutshell.

Nutshell account provisioning and schema setup

We work with the customer to provision the target Nutshell account on the appropriate plan (Foundation, Growth, Pro, Business, or Enterprise). During this step we create all required Nutshell custom fields on Person, Account, and Deal to receive APTANIA data that does not map to standard fields, including the B2C/B2B flag, original APTANIA record IDs, and any custom properties exported from APTANIA. We configure the pipeline and stage structure in Nutshell based on the pipeline data inferred from APTANIA's deal export. Pipeline configuration happens in Nutshell's UI before any data import begins.

Export file validation and transform design

We receive the exported CSV or JSON files from the customer and validate record counts, field headers, and data completeness. We design the field-level transform map (APTANIA field to Nutshell field) and run a small sample import (typically 50-100 records) into Nutshell to verify field mapping accuracy, deduplication behavior, and parent-record linkage. Sample import results are shared with the customer for sign-off before the full migration run. Corrections to the transform map happen at this stage.

Parent record import (Accounts and Persons)

We import APTANIA Companies into Nutshell as Accounts first, establishing the Account records that Person records will link to. We then import APTANIA Contacts into Nutshell as Persons, resolving the Account-Person linkage by matching the APTANIA contact's associated company name to the Nutshell Account created in the previous step. APTANIA user records are mapped to Nutshell Users by email match. Any APTANIA owner without a matching Nutshell User is placed in a reconciliation queue for the customer's admin to provision. Only after Account and Person imports are validated do we proceed to child records.

Deal and activity import

We import APTANIA Deals into Nutshell Deals, mapping stage names to the Nutshell pipeline stages configured in step two. Deal-Account linking is resolved by matching the APTANIA deal's associated company name to the Nutshell Account. Activity records (calls, emails, meetings, tasks, notes) are imported last, with each activity linked to its parent Person or Account by resolved ID. We handle rate limiting on Nutshell's API with exponential backoff and batch chunking to avoid throttling on larger activity volumes.

Cutover, reconciliation, and automation rebuild handoff

We freeze new APTANIA writes during the cutover window and run a final delta import of any records modified during the migration window. We deliver a row-count reconciliation report comparing APTANIA export totals to Nutshell import totals for each object. We provide a written automation inventory documenting all APTANIA email automation rules captured from customer screenshots, mapped to Nutshell's sales automation equivalents (Pro and above). We do not rebuild automation rules as Nutshell workflows; that work is handled by the customer's admin using the inventory document as a rebuild guide.