Migrate from Digital Signup to Microsoft Dynamics 365 Sales

Digital Signup registrants map directly to Dynamics 365 Sales Contact records. The primary registrant name, email, phone, and address fields translate 1:1. Registrants who represent organizations (rather than individuals) may route to Account instead — your team decides during schema planning which registrants are individuals vs. organizational contacts.

When a Digital Signup registrant includes an organization name, FlitStack AI creates a corresponding Account record in Dynamics 365 Sales and links the Contact via the AccountId lookup. This preserves the organization context that Digital Signup stores as a registrant property.

Digital Signup supports household groupings for family-based registrations (common in childcare and community education). Dynamics 365 Sales has Account-level household modeling via the Accounts table; we map household members as Contacts under a single Account, with the household name as Account.Name.

Enrollment records are the core data object in Digital Signup but have no direct equivalent in Dynamics 365 Sales. We create a Registration custom table in Dynamics 365 Sales (Dataverse) linked to Contact and Account. Fields include program name, enrollment date, status, waitlist position, and payment reference.

Program and class names from Digital Signup become custom fields on the Registration table or as a pick-list (Option Set) on Contact. If programs recur across years, we recommend an Option Set so Dynamics 365 Sales Sales Insights can analyze enrollment by program category. Multi-session programs may require separate Enrollment records per session.

Digital Signup facility and room assignments map to a custom text or Option Set field on the Registration table. Dynamics 365 Sales has no native resource management; facility names are stored as data, not as managed resources. If facility utilization reporting is critical, we recommend a separate Facility custom table linked to Registration.

Payment status (paid, refunded, pending), payment method, and transaction ID from Digital Signup migrate as custom fields on the Registration table. Full payment history and invoice data requires a custom Payment History custom table if granular reporting is needed in Dynamics 365 Sales.

Digital Signup waitlist records carry a numeric position and timestamp. We map these as integer and datetime fields on the Registration custom table. A blank or null waitlist position indicates the registrant is confirmed; a value indicates their queue position.

Digital Signup collects emergency contact name and phone for childcare and community programs. These data points are migrated as custom text fields (Emergency_Contact_Name__c and Emergency_Contact_Phone__c) attached to the Contact record in Dynamics 365 Sales. They are stored outside the standard Contact schema, enabling staff to retrieve backup contact information for safety notifications or program communications without altering the native Contact entity.

Digital Signup staff assigned as program coordinators map to Dynamics 365 Sales SystemUser records by email address match. If a Digital Signup staff member has no corresponding Dynamics 365 Sales license, their records are assigned to a designated fallback owner before migration.

Digital Signup notes attached to registrants or enrollments migrate as Dynamics 365 Sales Notes (Annotation entity). Original creation timestamps and note authors are preserved. File attachments are downloaded and re-uploaded to Dynamics 365 Sales SharePoint integration or Dataverse file storage.

Digital Signup custom fields added by your organization (e.g., dietary restrictions, membership tier, referral source) map to equivalent custom fields in Dynamics 365 Sales. Custom objects require a custom table in Dataverse. We surface all custom field definitions during the discovery phase before mapping.