Migrate from PAWS to Nutshell

PAWS contacts map directly to Nutshell People records. The People object in Nutshell serves both lead and contact roles — FlitStack routes PAWS leads to the same object and relies on Nutshell's status field to distinguish them. The mapping preserves the original contact ID for later reference and audit.

PAWS company records map 1:1 to Nutshell Companies. Nutshell's Companies object supports a parent-company field that handles PAWS hierarchical company structures where parent-child relationships exist. During migration, each company's parent reference is resolved against the already-migrated company list, ensuring that the hierarchy is correctly represented in Nutshell's parent_company field.

PAWS deals migrate as Nutshell Deals with pipeline and stage mapping. Nutshell Deal records store the deal name, value, stage, expected close date, and owner — all of which map directly from PAWS deal fields. FlitStack also maps any deal-specific custom fields to the corresponding Nutshell custom fields on the Deal object.

PAWS pipelines map to Nutshell Pipelines by name. If the PAWS pipeline does not exist in Nutshell, FlitStack creates it during the migration setup phase using the Nutshell API before records are loaded. The new pipeline inherits the same stage order and names from PAWS, ensuring a consistent pipeline view for users after cutover.

PAWS stage names map to Nutshell stage names value-by-value per pipeline. Probability weights associated with each PAWS stage are stored as custom numeric fields on the Nutshell Deal record since Nutshell calculates probability at the automation level rather than the field level.

PAWS lifecycle-stage and lead-status properties have no direct Nutshell equivalent. FlitStack creates a custom pick-list field (Lifecycle_Stage__c or Lead_Status__c) on the People object and populates it from PAWS values. Admins can filter People by this field after migration for reporting.

PAWS email, call, meeting, and note records migrate as Nutshell Activities attached to the corresponding People or Companies record. Original timestamps, owner, and body content are preserved. Attachments are re-uploaded to Nutshell's file storage and linked by URL and audit trails.

PAWS deal-contact associations with role labels (e.g., Decision Maker, Influencer) map to Nutshell's peopleDeal association. Role labels that have no Nutshell equivalent are stored as a custom text field on the association record. This preserves the original contact’s role in the deal context for reporting and follow-up.

PAWS custom fields that do not share a name and type with Nutshell's standard fields are created as Nutshell custom fields on the matching object before migration runs. FlitStack uses the Nutshell custom fields API to create the field definition and then populates values during the data load.

PAWS file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to Nutshell's file storage. File size limits apply — files exceeding Nutshell's 25MB per-file limit are flagged for chunked upload or alternative delivery. FlitStack retains original file names, attaches each file to its People, Company, or Deal record via Nutshell's file API, and logs the URL for audit. Files over 25 MB are flagged for manual handling.

PAWS owner IDs are resolved by matching the owner's email address against existing Nutshell user accounts. Unmatched owners are flagged before migration — teams either create Nutshell accounts for them or assign their records to a designated fallback user for review.

PAWS tags and labels applied to contacts or companies have no native Nutshell equivalent. FlitStack consolidates tags into a custom text field (Tag_List__c) or appends them to a dedicated note on the record for reference. This allows straightforward searching and segmentation after migration.