Migrate from Digital Signup to Twenty CRM

Digital Signup registrants map directly to Twenty People records. The mapping carries first name, last name, email, phone, and address fields. Parent/guardian contacts for youth programs are treated as separate People records — your FlitStack plan specifies whether to link them via a custom relation field or keep them as independent records.

Digital Signup organizations (schools, hospitals, community centers) map to Twenty Companies. The mapping preserves organization name, address, domain/website, and industry type. Multi-location organizations with separate Digital Signup accounts map to multiple Company records linked via a ParentId custom field. Each location's company record includes the address, phone, and website, and can be linked to a parent company using the ParentId field to preserve hierarchical reporting structures within Twenty's company graph.

Each Digital Signup program becomes a Twenty Opportunity representing a cohort or session. The Opportunity Name is constructed from Program Name + Offering Start Date for uniqueness. Pipeline stages are mapped from Digital Signup's enrollment status values (Registered, Waitlisted, Cancelled) to Twenty Opportunity Stage values you configure in the workspace.

If your Digital Signup programs carry rich attributes (category, description, capacity, prerequisites) that don't fit Opportunity fields, FlitStack creates a Program custom object in Twenty before migration. This requires Pro ($9/user/mo) or Organization ($19/user/mo) since custom objects are not available on the free tier. The migration plan flags this before data lands.

Digital Signup offerings (scheduled instances of a program with specific date, time slot, and facility) split into two Twenty constructs: an Offering custom object holding the schedule, instructor, and facility references, and Opportunity-level date fields (Expected Close Date) reflecting the offering start date. This split is necessary because Twenty's Opportunity model doesn't natively hold multi-slot scheduling data.

The enrollment record (linking a Registrant to an Offering with payment status) merges into the Opportunity: the People record is the primary contact on the Opportunity, and payment status, enrollment date, and discount applied are stored as custom fields on that Opportunity. One Opportunity per registrant-per-offering tuple — your FlitStack plan documents whether to consolidate multiple family-member enrollments.

Digital Signup instructors map to Twenty People records with a custom select field (Role__c: Instructor, Staff, Administrator) because they may also be registrants in other programs. Staff-only accounts that need Twenty workspace access are flagged — they must be invited as Workspace Members before migration so their userId can be referenced in the OwnerId field on migrated records.

Digital Signup facilities map to Twenty Companies with a Facility_Flag__c custom field set to true, and address fields holding the location. If your facility records carry equipment or capacity attributes not representable on a standard Company, FlitStack creates a Location custom object. The Offering custom object then links to Location records via a relation field.

Digital Signup payment records (amount, status, payment method, transaction date) migrate as custom fields on the corresponding Opportunity: Payment_Status__c, Payment_Method__c, Amount_Paid__c, Transaction_Date__c. Full invoice history requires a separate Invoice custom object — FlitStack's plan specifies this if your use case requires it, since Twenty has no native invoicing module.

Digital Signup discount types (Veteran, Senior, Resident, Custom) map to a Discount_Type__c custom pick-list on the Opportunity. The discount amount or percentage maps to Discount_Value__c. Discount rules configured in Digital Signup's user-definable discount levels do not transfer — those business rules must be rebuilt as Twenty workflow conditions or documented for your admin.

Digital Signup waitlist entries become Opportunities with a Waitlist_Entry__c boolean flag and Waitlist_Position__c number field. The Opportunity Stage maps to a 'Waitlisted' stage you create in Twenty's pipeline configuration. If the waitlist converts to enrollment, the flag is cleared and the stage is updated — this is a manual action or a workflow trigger you configure post-migration.

Digital Signup file attachments (waivers, consent forms, program materials) attached to registrants or programs migrate as Twenty Notes linked to the corresponding People or Opportunity record. File size limits apply per Twenty's storage configuration. The original file name and a link back to the source record ID are preserved in the Note body.