Migrate from Atendare to Nutshell

API access confirmation with Atendare vendor

We contact Atendare directly to confirm whether the customer's account has API access, what authentication method is used (API key, OAuth, or session-based), which endpoints are available, and what rate limits apply. If API access is confirmed, we proceed to discovery. If API access is unavailable or restricted, we fall back to CSV export where the account plan supports it and flag manual export requirements for any objects not exportable via CSV. This step typically adds one to two weeks to the timeline and must complete before we can finalize the migration scope or pricing.

Discovery and record volume audit

We audit the Atendare account for record volumes across all objects (Contacts, Companies, Deals, Activities, custom properties, lists, and any Enterprise-tier Proposals or Contracts). We identify which Atendare tier the customer is on to determine available objects. We also review the current pipeline configuration, stage names, owner assignments, and any custom property definitions. The output is a written discovery summary and migration scope document that the customer approves before we begin schema design.

Nutshell schema configuration

We configure the destination Nutshell account before any data import. This includes creating custom fields in Nutshell's customFields format for all Atendare custom properties (mapped by type: text, long text, currency, date), setting up Record Types on Opportunity for each Atendare pipeline, configuring stage values with probability percentages from Atendare, and creating saved filters that map to Atendare contact segments. We also provision any missing Nutshell user accounts by email match against Atendare team members so that owner lookups are valid at migration time.

Sandbox migration and reconciliation

We run a full migration into a Nutshell trial or sandbox environment using production-like record volumes to validate the mapping. The customer reviews a reconciliation report comparing record counts and spot-checks a sample of records against the Atendare source. Any field mapping corrections, custom field type adjustments, or pipeline configuration changes happen at this stage before production migration begins. This step is critical because Nutshell's rev-based API requires the correct revision value before any update, and schema corrections after production migration are more costly.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users are validated first (no migration, just confirmation), then Accounts (from Atendare Companies), then People (from Atendare Contacts with AccountId resolved), then Opportunities (with RecordTypeId, owner, and stage resolved), then Activity history (Tasks with TaskSubtype and ActivityDate preserved via batched API calls with retry on rev conflicts). Custom properties migrate during each phase as part of the record upsert using Nutshell's customFields dictionary. Each phase emits a reconciliation count before the next phase begins.

Cutover, validation, and automation inventory delivery

We freeze Atendare writes during the cutover window, run a final delta migration of any records modified during the migration, then enable Nutshell as the system of record. We deliver a written inventory of all Atendare marketing automation workflows, email campaign definitions, contact segment logic, and landing pages that do not migrate, with recommended rebuild steps in Nutshell Marketing Pro or an equivalent external platform. We support a three-day hypercare window where we resolve reconciliation issues. We do not rebuild Atendare automations, workflows, or sequences inside the migration scope.