Migrate from Digital Signup to HighLevel

Digital Signup registrants map directly to HighLevel Contacts. Name, email, phone, and address fields transfer as standard Contact fields. A unique Email address is required for HighLevel contact creation; registrants without email require a custom field flag for manual follow-up.

Digital Signup class sections (e.g., 'Fall Yoga 2026 – Mon 9am') have no native HighLevel equivalent. FlitStack creates a Class custom object with fields for section name, scheduled dates, instructor, and capacity. Class custom objects link to HighLevel Contacts via a relationship field to track enrollment.

Each Digital Signup enrollment record (registrant + class section combination) becomes a HighLevel Opportunity. The Opportunity Name uses the format 'Registrant Name – Class Section'. Pipeline stages represent enrollment status: Registered, Waitlisted, Attended, Cancelled. Additionally, the Opportunity amount field may be populated with the enrollment fee if available, and custom fields capture payment status, waitlist position, and any enrollment notes to preserve the full registration context.

Digital Signup enrollment statuses (Registered, Waitlisted, Cancelled, No-Show) map to HighLevel Opportunity stage values. Each pipeline stage carries probability percentages for attendance forecasting. Stage names and probabilities are configurable per pipeline. These stage probabilities inform sales forecasts and help managers allocate resources, such as instructor hours and room capacity, based on expected enrollment levels.

Digital Signup facilities and rooms have no HighLevel equivalent. A Facility custom object captures facility name, address, room count, and equipment notes. Facilities link to Class custom objects via a relationship field for location tracking. This setup allows staff to see which classes are held at which locations and helps with scheduling conflicts across multiple venues.

Payment status (Paid, Pending, Refunded) and amount from Digital Signup merge into two destinations: a payment_status__c custom field on the Contact record and payment_amount__c on the related Opportunity. Payment history log stored as a JSON-formatted text custom field on the Opportunity for audit continuity.

Digital Signup waiver acceptance (yes/no + waiver name + acceptance date) migrates as a waiver_accepted__c custom field (checkbox) and waiver_name__c (text) on the Contact. The signed waiver PDF, if exported from Digital Signup, reattaches to the HighLevel Contact record as a HighLevel File.

When Digital Signup records show multiple registrants under one transaction (family enrollment), FlitStack creates a Family custom object and links all related Contact records via a Family custom relationship. This preserves the household grouping without requiring a native group-contact model in HighLevel.

Digital Signup class categories and tags (e.g., 'Youth Soccer', 'Senior Fitness', 'After-School Care') transfer as HighLevel Tags on each Contact. Tags drive workflow segmentation for enrollment reminders and future campaign targeting. These tags also enable filtering in pipeline reports, helping managers identify enrollment trends by program type and adjust marketing efforts accordingly.

Digital Signup instructor and staff records map to HighLevel Contacts with an is_instructor__c checkbox custom field and a contact_type__c pick-list set to 'Instructor'. Instructor contacts link to Class custom objects via the instructor relationship field. This designation allows managers to assign instructors to specific class sessions and to filter contact lists for staff-only communications or reporting.

Digital Signup waitlist position (integer rank per class) has no native HighLevel equivalent. A waitlist_position__c custom number field on the Opportunity captures the rank. When a spot opens, workflows in HighLevel can trigger outreach to the contact in waitlist position 1.

Past class attendance data from Digital Signup migrates as completed Task records on the HighLevel Contact, with Subject='Attended: [Class Section Name]' and Activity Date matching the original class date. This preserves attendance history for reporting continuity. The tasks are linked to the related Opportunity and Class records, allowing users to view attendance history in context and to trigger follow-up actions based on participation patterns.