Migrate from Digital Signup to Salesforce Sales Cloud

Digital Signup programs map directly to Salesforce Products. The Product Name becomes the program title, with Description carrying program details. Program capacity and scheduling metadata migrates to custom fields on the Product record. Products are created first so that Session records can reference them via ProductId.

Digital Signup program instances or sessions become a custom Session__c object in Salesforce. Each Session__c record links to its parent Product via a ProductId lookup (custom field). Start date, end date, capacity, and waitlist count migrate as custom fields on Session__c. Junction object ProgramSessionJunction__c is created when sessions can belong to multiple programs.

Digital Signup registrants and attendees map directly to Salesforce Contacts. Each Contact requires an AccountId lookup to the registrant's organization Account. Registrants without an organization land on a default 'Unassigned Accounts' record. The Contact's email, phone, and address fields map directly from Digital Signup's registrant contact properties.

When Digital Signup stores an organization or household name alongside a registrant, that name becomes a Salesforce Account. Parent-child organization hierarchies in Digital Signup map to Account.ParentId in Salesforce. Multi-contact organizations in Digital Signup collapse to one primary Account per organization with additional Contact relationships as Account Contact Relations.

Registration records carrying payment or revenue data map to Salesforce Opportunities, with Program__c (lookup to Product2) and Session__c (lookup to custom Session__c) linking to the program and session context. Registrations without payment data map to a custom Registration__c object that references both the Contact and the Session, preserving status, waiver, and session count fields as custom fields.

Digital Signup payment amounts and status map to custom fields on the Salesforce Opportunity when registrations carry revenue (e.g., PaymentAmount__c, PaymentStatus__c). For partial payments or multi-installment records, a custom Payment__c object is created with a lookup to the Opportunity. Payment method and transaction ID are preserved as text custom fields.

Digital Signup facility and room data migrates to a custom Facility__c object in Salesforce. Facility name, address, and capacity become custom text and number fields. Sessions reference their hosting facility via a Facility__c lookup custom field. If facilities are used across multiple program types, a junction object associates sessions with facilities in a many-to-many relationship.

Digital Signup custom properties on any object become Salesforce custom fields using the __c suffix convention. Pick-list custom properties require value-by-value mapping when Digital Signup uses a defined set of values. Multi-select fields in Digital Signup map to Salesforce multi-select picklists. All migrated custom fields retain the original Digital Signup field label and API name for traceability.

Signed waiver documents and program documents from Digital Signup are downloaded and re-uploaded as Salesforce Files (ContentVersion). Each file is linked to the relevant Contact or Registration record via ContentDocumentLink. If Digital Signup stores documents as URLs rather than file binaries, the URL is preserved in a custom text field (WaiverURL__c) for manual retrieval.

Digital Signup waitlist data can be handled two ways depending on volume: low-volume waitlists migrate as a custom pick-list field on the Registration record (WaitlistStatus__c with values Enrolled, Waitlisted, Not Attended). High-volume waitlists or separate waitlist records create a WaitlistEntry__c custom object linked to the Session and Contact, preserving original waitlist position and timestamp.

Digital Signup file attachments on registrations, facilities, or programs re-upload to Salesforce Files. Files are associated with the relevant Salesforce record via ContentDocumentLink. Salesforce's 25MB per-file limit applies; files exceeding this threshold are flagged for manual re-upload by your team during reconciliation.