Migrate from Digital Signup to Nutshell

Digital Signup registrants are person records with name, email, phone, and address fields. These map directly to Nutshell People. A registrant's emergency contacts or secondary guardian information migrates as custom fields on the People record since Nutshell People support a flat contact-record structure.

When a Digital Signup registrant is associated with a school, hospital department, or corporate group, the organization name becomes a Nutshell Company record. If no organization is present, the People record stands alone. Companies in Nutshell link to People via the people-per-company relationship, and we preserve the original relationship type as a Company custom field.

Each Digital Signup class enrollment becomes a Nutshell Deal. The class name becomes the Deal name. The enrollment date maps to Deal.create_date, and the class start date maps to the CloseDate field repurposed as program start date. Deal.Amount reflects the registration fee paid. The Nutshell pipeline's default stages (New, Contacted, Qualified, Proposal, Won, Lost) are repurposed to match enrollment funnel stages: Registered, Waitlisted, Confirmed, Attended, Cancelled.

Digital Signup programs are structured objects with instructor, capacity, schedule, and location. In Nutshell, we create a custom text field (Program_Name__c) on Deals to store the class or program name. The Nutshell Pipeline itself represents the overall enrollment pipeline. Multiple Nutshell Pipelines can be used if the organization runs separate enrollment funnels (e.g., one for childcare, one for adult education) — each Pipeline maps to a distinct Digital Signup program category.

Waitlist entries in Digital Signup map to Nutshell Deals with a dedicated stage value (e.g., Waitlisted) that is added to the pipeline stage pick-list. The waitlist position and waitlist-joined timestamp migrate as custom fields (Waitlist_Position__c, Waitlist_Joined_Date__c) on the Deal. Converting from waitlist to confirmed enrollment is a Deal stage transition, not a record creation.

Digital Signup instructor records migrate as Nutshell People with a custom role pick-list (Person_Role__c) set to 'Instructor'. Instructors are linked to Deals (class enrollments) via the People-on-Deal relationship. Nutshell's built-in association between People and Deals supports this linking without a custom junction object.

Digital Signup facilities are structured location records with address and room information. Nutshell has no native Locations object, so we map facility data to Deal custom fields: Facility_Name__c (text), Facility_Address__c (text), Room__c (text). If the organization uses facilities as a reporting dimension, we alternatively map them to Companies with type='Facility' — your team decides the reporting structure during the mapping review.

Digital Signup payment records (amount, method, status, date) migrate as Nutshell Notes attached to the corresponding Deal (class enrollment). The Note body contains a structured summary: payment method, amount, status, and transaction ID. For partial payments or installment plans, we create one Note per payment event and preserve the payment status as a Deal custom field (Payment_Status__c).

Digital Signup attendance logs are complex (per-session attendance for multi-day programs). We map attendance as a Deal custom field (Attendance_Rate__c) for summary reporting and create a Nutshell Activity (type=Note) per session with a structured body summarizing attendance status. The original per-session check-in times are preserved as Activity timestamps for audit continuity.

Digital Signup custom form fields (e.g., dietary restrictions, t-shirt size, emergency contact) do not have a standard Nutshell equivalent. We create custom fields on the People object for each unique custom form field, naming them to match the source field label. Fields with pick-list values in Digital Signup become Nutshell pick-list custom fields.

We store the Digital Signup internal record ID on every migrated Nutshell record as a custom text field. This enables delta-run reconciliation (detecting records modified in Digital Signup after the initial migration) and provides a traceability anchor for post-migration audit.