Migrate from CE Manager to Bullhorn ATS & CRM

CE Manager Users map to Bullhorn Candidate records. The Candidate record stores firstName, lastName, email, phone, and address fields directly. We resolve duplicate candidates by matching on email and name, preferring the record with the most recent compliance activity. Any CE Manager user without an email address is flagged for manual review before migration because Bullhorn requires a unique email per Candidate for duplicate detection.

Each License in CE Manager (jurisdiction, license type, status, renewal date, credits needed, credits earned) maps to custom fields on the Bullhorn Candidate record (e.g., customText1 for jurisdiction, customDate1 for renewal date) or to a dedicated customObject linked to the Candidate. Bullhorn Support must provision the custom object before migration begins. Where CE Manager tracks multiple active licenses per user, we create one customObject record per license and link each to the same Candidate via the custom object's Candidate lookup field.

Bullhorn has no native course or curriculum object. We create a Bullhorn customObject for Course that captures courseName, courseDescription, creditAmount, practiceArea, providerName, and deliveryFormat. Bullhorn Support provisions customObject1 for the Course entity before import. Course records are created first in the migration sequence so that Attendance records can reference them via lookup.

Attendance records in CE Manager link a User to a Course and record completionDate, creditsEarned, and score. We map these to a Bullhorn customObject Enrollment with lookups to the Candidate (from the mapped User) and the customObject Course. Bullhorn's native Application and JobSubmission objects do not map to Attendance because they represent candidate-to-job relationships, not user-to-course enrollment.

CE Manager computes compliance dynamically from License and Attendance data per reporting period. There is no standalone Compliance object to export. We reconstruct it by querying all License records and their linked Attendance records for each CE Manager user, summing creditsEarned against the jurisdiction-specific creditsRequired threshold, and writing the computed result to a Bullhorn customObject ComplianceStatus linked to the Candidate. The reconstructed compliance state includes isCompliant (boolean), compliancePeriod (date range), creditsEarned, creditsRequired, and complianceGap (numeric). This is the most critical computed field for regulatory audit readiness.

CE Manager LearningTracks group multiple Courses into a curriculum path. Bullhorn has no native learning track object. We flatten each LearningTrack into individual Enrollment records (customObject Enrollment, per the Attendance mapping) and preserve the track name, track description, and course sequence order in a customObject Curriculum linked to each Enrollment so that curriculum structure is reconstructable in Bullhorn reporting.

CE Manager Providers carry name, accreditation details, and state-specific accreditation status. Bullhorn has no native Provider object. We create a Bullhorn customObject Provider and map providerName, accreditationBody, and accreditationStatus to custom fields. Provider records are created before Courses so that the Course customObject can reference the Provider via a lookup relationship.

CE Manager PracticeAreas tag courses and user preferences to legal, accounting, or clinical specialties. Bullhorn has no native practice area object. We store practiceArea as a customText field on the customObject Course and as a customText field on the Candidate record. Bullhorn's customText fields support up to 255 characters, sufficient for practice area names.

CE Manager Affiliations link a User to a Firm, Department, or Office. Bullhorn Candidate records include a department field, but it is scoped to internal staffing use. For CE Manager affiliations carrying firm-level, department-level, and office-level hierarchy, we map to Bullhorn Candidate custom fields (customText for firm, customText for department, customText for office) or a dedicated customObject Affiliation if the affiliation data includes dates and roles.

CE Manager Schedules define when and where a Course is offered, with date, time, timezone, and location. Bullhorn Event records store date and time but have no native timezone field. We map schedule date and time to Bullhorn Event start/end and store the original timezone as a customText field (e.g., 'America/Chicago'). Location maps to Event location. For multi-session courses, we create one Event per session and link all events to the customObject Course.

CE Manager Materials are files and documents linked to Courses. Bullhorn ContentDocument supports binary file storage linked to any entity via ContentDocumentLink. We export available Material records from CE Manager, map file metadata to Bullhorn ContentVersion and ContentDocument, and link each to the associated customObject Course record. File binaries are handled separately from record migration with a different transfer mechanism and are validated post-migration by the customer's admin.

CE Manager allows firms to extend the schema with custom Firm System Tables that are not publicly documented. During scoping, we run explicit schema discovery against the CE Manager REST API to enumerate all custom tables, their fields, and their relationships. Each discovered custom table is mapped to a Bullhorn customObject of the same name or a sanitized equivalent, with fields typed to the nearest Bullhorn-supported field type. Bullhorn Support must provision each custom object before import. Custom tables with lookup relationships to standard CE Manager objects (User, License, Course) are mapped to Bullhorn customObjects with corresponding lookups to Candidate or other provisioned custom objects.