Migrate from CE Manager to Recruit CRM & ATS

CE Manager User records map to Recruit CRM Candidate records as the primary record type since these represent the licensed professionals being tracked. The user's professional title, jurisdiction, and contact information map to standard Candidate fields. Staff users within the CE Manager firm map to Recruit CRM Users. We deduplicate by email address and flag any title-merge duplicates for manual review before writing to Recruit CRM. The CE Manager HR Export employee CSV format maps cleanly to Candidate import templates.

CE Manager License records track jurisdiction, license type, renewal dates, due dates, and credits needed. Each License maps to a set of custom Associated Fields on the Candidate record in Recruit CRM. We create field definitions for license_number, license_state, license_type, renewal_date, credits_needed, and any jurisdiction-specific custom fields before import. Compliance status is computed and written as a text field. Each distinct jurisdiction combination becomes its own field group on the Candidate.

CE Manager Course records map to Skills or Qualifications on the Candidate in Recruit CRM. Course name, credit amount, format type (CLE, CPE, CPD), provider, and practice-area tags migrate as individual qualification records or as associated fields. We flatten the course catalog into a qualification structure that Recruit CRM's candidate profile can display. Course definitions that are not yet linked to a specific user are stored as a reference dataset for enrollment mapping.

CE Manager Attendance records link a User to a Course and record credits earned and completion date. Each Attendance record maps to a Candidate Activity or a note entry on the Candidate record in Recruit CRM, preserving the course name, credits earned, completion date, and provider. If the destination uses a specific Activity type for training completion, we configure that type during migration setup. Attendance data that represents verified completion migrates as a structured record; incomplete enrollments migrate as pending activities.

CE Manager Compliance is a computed state per License, not a standalone object. We reconstruct the compliance picture by pulling all License records and their associated Attendance records, computing credit totals against each jurisdiction's required credit threshold for the current reporting period. The computed compliance result (compliant, non-compliant, pending) and credit totals write to custom Associated Fields on the Candidate record. We do not migrate compliance rules as executable logic; we deliver a written inventory of each jurisdiction's credit thresholds for the customer to configure as custom fields or validation rules in Recruit CRM.

CE Manager LearningTracks group multiple Courses into a curriculum path. Where Recruit CRM does not support a native LearningTrack object, we flatten the track into individual Course enrollments (Attendance records) and preserve the track membership as a tag or custom field on the Candidate record. The track name and required course sequence are documented for the customer to rebuild as a Recruit CRM pipeline stage or workflow if needed.

CE Manager Providers deliver CE courses and carry state-specific accreditation. Provider records map to Recruit CRM Client records, with accreditation details and jurisdiction coverage stored as notes or custom fields on the Client. Provider-to-course associations migrate as notes on the course qualification records. If the firm also uses Recruit CRM for placement services, Providers may alternatively map to a separate lookup table if the customer requires accreditation tracking separate from client management.

CE Manager PracticeAreas tag courses and user preferences to legal, accounting, or clinical specialties. Practice area tags migrate as Tags on Candidate records in Recruit CRM, enabling candidate filtering by specialty. Course-level practice areas migrate as tags on the qualification records. We preserve the practice-area hierarchy as a flat tag list compatible with Recruit CRM's tagging model.

CE Manager Affiliations link Users to Firms, Departments, or Offices. Where Recruit CRM uses a client-department hierarchy, we map affiliations to either Department records on the Client object or to a custom organizational hierarchy structure. If the destination uses a flat client model, affiliations flatten to tags or notes on the Candidate record indicating firm and department membership at the time of migration.

CE Manager Schedule records define when and where a Course is offered. Schedule records migrate as calendar events linked to the relevant Course qualification records or to the Candidate's activity timeline in Recruit CRM. Date, time, timezone, and location fields are preserved. We flag any schedule records that represent mandatory compliance deadlines as reminder tasks on the Candidate record. Recruit CRM does not have a native scheduling module for course delivery, so schedules map to candidate activity history.

CE Manager allows firms to extend the schema with custom firm system tables beyond standard objects. We discover any custom tables during scoping by running explicit schema discovery against the API, enumerating all custom tables, their fields, and their relationships. We then create equivalent custom Associated Fields in Recruit CRM (field_id and value pairs per candidate or client), mapping each CE Manager custom field to a typed Recruit CRM associated field. Binary attachments from custom tables are handled separately with URI mapping. We surface the full custom schema to the customer before extraction begins and document any fields that cannot be represented in Recruit CRM's associated field model.

CE Manager Materials are course-related files or documents. We export available Material records and their links to Courses. Binary file migration is handled separately from record migration, with material URIs preserved as external links on the relevant course qualification or candidate record in Recruit CRM. If Recruit CRM's document management is used, we create ContentDocument records and link them via ContentDocumentLink to the parent Candidate or Client record.