Migrate from Digital Signup to Odoo CRM

Digital Signup registrants map directly to Odoo res.partner records. The registrant type (individual vs. organization) sets the partner's is_company flag. Email, phone, and address fields translate using Odoo's standard contact field conventions. Original registrant IDs are preserved as an external ID field for traceability.

Digital Signup emergency contacts attach as secondary res.partner records linked via a many2one relationship to the primary registrant partner. The relationship type (parent, guardian, emergency) maps to a custom contact_description field on the related partner record so Odoo users can distinguish contact roles at a glance.

When a Digital Signup registrant is linked to an organization or site (e.g., a school or hospital department), that entity becomes a res.partner record with is_company=True. The registrant's relationship to the organization is preserved using res.partner relation records (category-based or custom) in Odoo.

Each Digital Signup class or program maps to a crm.lead opportunity in Odoo. The class name becomes the opportunity name, and the session's capacity and enrollment counts translate to expected_revenue and priority fields. Pipeline stages are configured per program type so program directors see enrollment funnels in Odoo's kanban view.

Registration status (enrolled, wait-listed, cancelled, no-show) merges into a combination of crm.lead stage plus a custom selection field (registration_status) on the opportunity. Paid vs. pending vs. refunded payment status appears as a separate field when Odoo Accounting is present; otherwise it is noted in the opportunity description for manual reconciliation.

Digital Signup time slots and session schedules translate to Odoo project.task records when the Project module is active. Start and end datetime map to date_deadline and planned_hours fields. Recurring sessions generate task templates linked to the parent opportunity (class). If Project is not active, sessions appear as calendar.event records on the opportunity.

Digital Signup payment transactions map to Odoo account.move invoices or payments depending on whether the transaction represents a one-time enrollment fee or a recurring billing cycle. The registrant's res.partner record is set as the move partner. When Odoo Accounting is not active, payment data is preserved as attachment-linked JSON with the transaction ID and amount for reference.

Digital Signup's user-defined discount levels (veteran, senior, resident, custom) and scholarship flags have no native Odoo equivalent. We create selection fields on crm.lead (x_discount_type, x_scholarship_flag) and migrate the original values so program staff can report on discount utilization in Odoo pivots.

Signed waivers and policy acceptance records store as binary attachments linked to the res.partner or crm.lead record via ir.attachment. Odoo has no native waiver tracking — the attachment preserves the original record for compliance but requires a manual process to verify acceptance status.

Digital Signup staff and instructor records map to res.users in Odoo. Email-based matching links staff to existing Odoo users; unlinked staff are flagged for your admin to create accounts before migration. Staff assignments to classes become task assignments or opportunity followers in Odoo depending on the module configuration.

Digital Signup user-defined fields per program type (e.g., dietary restriction for a summer camp, certification level for a training program) migrate to custom fields on crm.lead. Each unique field name generates a new x_ field; pick-list values map via value_mapping. Fields are created via Odoo's ir.model.fields API before data loads.

Digital Signup gift card balances and store credit have no native Odoo equivalent. We preserve the balance as a custom decimal field on res.partner (x_gift_card_balance) and create a note record explaining the source value. Your team recreates the gift card issuance process in Odoo using a dedicated product and sales order workflow if needed.