Migrate from Amwork to Nutshell

Amwork Contacts map directly to Nutshell People. We preserve name, email, phone, address, lifecycle stage, and owner assignment. Custom contact fields map to Nutshell custom fields on People, which we pre-create via Nutshell's custom field API before migration. Owner resolution runs by email match against Nutshell Users. Any owner with no matching Nutshell User enters a reconciliation queue for admin provisioning before contact import.

Amwork Companies map to Nutshell Companies with domain, industry, address, and linked contact relationships preserved. The Amwork company domain becomes the Nutshell Company website field and serves as the dedupe key during import. Nutshell Company is created before any Person import so the lookup relationship is satisfied at Person insert time.

Amwork Deals map to Nutshell Deals. The dealstage property maps to Nutshell pipeline stage names, and the pipeline assignment maps to a Nutshell pipeline that we configure before migration. If the source Amwork pipeline has stages that do not exist in the target Nutshell workspace, we create them before deal import so stage reassignment is not needed post-migration. Deal value, closed date, and loss reason migrate directly.

Amwork Leads in the Deals and Leads section map to Nutshell Leads. Lead status field from Amwork maps to Nutshell Lead status with any scoring or source data preserved as custom fields on the Nutshell Lead. If the customer prefers to work in Nutshell People only, Leads can be merged into the Person object during scoping.

Amwork time entries log against Projects and Tasks, not directly against Contacts or Companies. Since Nutshell has no native time-tracking object, we preserve Amwork time-entry data as Activity records (as Notes) on the related Nutshell Company or Person. Each migrated time entry records the duration, date, description, and billable flag. We flag this model change during scoping so the customer's team knows that time logging workflow must be adopted within Nutshell's Activity model post-migration.

Amwork Projects are top-level workspace containers with no direct Nutshell equivalent. We evaluate whether Projects represent client accounts (mapped to Nutshell Company), internal initiatives (discarded with a written record), or project-based revenue tracking (documented as a Deal-naming convention or tag structure in Nutshell). The customer chooses the strategy during scoping.

Amwork Tasks migrate as Nutshell Activities of type Task. Assignee, due date, priority, and description transfer. Parent-child task hierarchy does not map natively since Nutshell does not support sub-task nesting. We flatten hierarchy into individual Activities and flag the structural change so the customer's team can adopt Nutshell's Activity model for task tracking.

Amwork User records map to Nutshell User accounts by email match. Active status, role, and name transfer. Any Amwork User referenced on Deals, Tasks, or Projects without a matching Nutshell User is held in a reconciliation queue. The customer provisions missing Nutshell Users before migration resumes. Automation rules referencing inactive users are documented separately in the automation inventory handoff.