Migrate from Pawa to Nutshell

Discovery and API surface validation

We request Pawa API credentials and connect to a live instance to enumerate the actual schema: object types, field names, field types, relationship fields (foreign keys), and custom field definitions. We also check for any bulk export capability, report generation, or CSV download options available within the Pawa interface. The discovery output is a provisional migration scope with a full field map and a list of records that contain attachments. If the API surface is smaller than expected, we update the scope and pricing before proceeding.

Nutshell sandbox setup and schema design

We create a Nutshell trial or sandbox environment and design the destination schema: custom fields on People, Organizations, and Deals; pipeline stages matching Pawa's pipeline structure; and any custom field types required to receive Pawa's data. We agree on the field map with the customer's admin before deploying any schema changes to the production Nutshell org.

Owner and User reconciliation

We extract every distinct Pawa User referenced on Contact, Company, and Deal records and match by email against the Nutshell destination User table. Any Pawa User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import begins. Owner assignments on migrating records cannot be resolved until this step is complete.

Data extraction and transformation

If Pawa exposes a bulk export endpoint, we use it with pagination and rate-limit handling to extract all Contacts, Companies, Deals, and custom field data. If only record-by-record API access is available, we paginate through the endpoint with exponential backoff. We transform the extracted records using the agreed field map, parse tag arrays, resolve foreign key references, and prepare CSV-formatted import files for Nutshell. Attachments are listed and excluded from the import file.

Production migration in dependency order

We run production migration in record-dependency order: Organizations first (from Pawa Companies), then People (with Organization lookup resolved), then Deals (with People lookup and Owner resolved), then custom field data. Each phase emits a row-count reconciliation report showing records inserted, skipped, and errored before the next phase begins. Errors are investigated and corrected before retrying the phase.

Cutover, validation, and automation inventory delivery

We freeze Pawa write access during cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We deliver the attachment list with record references for manual re-upload. We deliver the automation inventory document listing every Pawa workflow or sequence with its trigger, conditions, and actions for the customer's admin to rebuild in Nutshell. We support a five-business-day post-cutover window to resolve reconciliation issues raised by the customer's team.