Migrate your CE Manager data
Specialized compliance-tracking HRMS for CLE, CPE, and CPD credits across 400+ jurisdictions. Designed for licensed professionals at firms that must prove continuing education to regulators.
In its favor
Why people choose CE Manager
The signal that keeps CE Manager on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Jurisdiction coverage across 400+ regulatory environments means legal, accounting, and healthcare firms can track CLE, CPE, and CPD compliance in one system without managing spreadsheets by state or specialty.
Built-in compliance reporting produces jurisdiction-ready summaries that firms can submit to bar associations, boards of accountancy, and medical licensing bodies without manual consolidation.
REST API with CORS support enables firms to programmatically sync user rosters, course data, and attendance records with downstream HR or billing systems.
Modular architecture lets firms activate only the modules they need—courses, attendance, compliance, scheduling—rather than deploying a full suite upfront.
HR Export and Employee User Import tools provide a repeatable CSV-based workflow for syncing employee data from external HRIS systems into CE Manager.
Title merging and user record consolidation is reportedly difficult when firms restructure departments or change professional designations, leading to duplicate or stale user profiles.
Smaller firms report that the platform's feature depth exceeds their needs and that pricing scales steeply as they add users beyond the basic tier.
Limited self-service reporting flexibility means firms with non-standard compliance cycles must request custom exports rather than configure reports independently.
Integration with non-standard LMS platforms outside the documented API endpoints requires custom development, which smaller IT teams find burdensome.
Reasons to switch
Why people leave CE Manager
The recurring reasons buyers give for replacing CE Manager. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where CE Manager fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
CE Manager pricing overview
CE Manager uses a per-user-per-month subscription model. Basic plan starts at $10/user/month with Essential features. Professional and Enterprise tiers are not publicly priced; Enterprise quotes are tailored to organization size, jurisdiction count, and feature scope. Custom pricing is available for global enterprise clients.
Basic
Tier 1 of 3
$10/user/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on CE Manager's schedule — see our quote-based pricing →
What gets migrated
CE Manager object support
Object-by-object support for CE Manager migrations. Per-pair details surface during scoping.
Users
Fully supportedUsers are the core employee records in CE Manager. The HR Export - Employees report generates a CSV matching the Employee User Import tool format, making bulk export and re-import straightforward. We extract all user fields including role assignments and organizational affiliations.
Licenses
Fully supportedLicenses represent a user's professional license in a specific jurisdiction. Each License tracks compliance status, due dates, renewal dates, and credits needed. We preserve all license records including prior-period compliance flags and the jurisdiction name.
Courses
Fully supportedCourses are the CE training units offered or attended. Each Course carries credit amounts, format type, provider, and practice-area tags. We extract full course definitions including any custom fields before migrating to the destination system.
Attendance
Mapping requiredAttendance records link a User to a Course and record the credits earned. When the destination system uses a different relationship model (e.g., Enrollment objects), we map the attendance data into the target's equivalent object and preserve the credit value per record.
Compliance
Mapping requiredCompliance is a computed state per License, not a standalone object. It aggregates credits earned against credits needed for a reporting period. We reconstruct the compliance picture from License and Attendance data during migration rather than trying to export a Compliance record directly.
LearningTracks
Mapping requiredLearningTracks group multiple Courses into a curriculum path. Where the destination HRMS does not support LearningTracks natively, we flatten the track into individual Course enrollments and preserve the track assignment as a custom property on each enrollment.
Providers
Fully supportedProviders are the entities that deliver CE courses. Each Provider may be associated with multiple courses and may carry state-specific accreditation. We export Provider records with their accreditation metadata intact.
PracticeAreas
Mapping requiredPracticeAreas tag courses and sometimes user preferences to a legal, accounting, or clinical specialty. We preserve practice-area tags as custom fields on course and user records when the destination does not have a native PracticeArea object.
Affiliations
Mapping requiredAffiliations link Users to Firms, Departments, or Offices. When the destination HRMS uses a different organizational hierarchy model, we map the affiliation structure to match the target's org-unit model.
Schedules
Fully supportedSchedules define when and where a Course is offered. We export Schedule records including date, time, timezone, and location fields so that enrollment calendars can be rebuilt in the destination system.
Custom Objects (Firm System Tables)
Mapping requiredCE Manager allows firms to define custom system tables beyond the standard objects. We discover any custom tables during scoping, extract their schema and data, and map them to the destination's custom object model. This requires explicit schema discovery since custom objects vary by firm.
Materials
Mapping requiredCourse materials are associated files or documents. We export available Material records and their links to Courses. Binary file migration is handled separately from record migration, with material URLs preserved where accessible.
| Object | Support | Notes |
|---|---|---|
| Users | Fully supported | Users are the core employee records in CE Manager. The HR Export - Employees report generates a CSV matching the Employee User Import tool format, making bulk export and re-import straightforward. We extract all user fields including role assignments and organizational affiliations. |
| Licenses | Fully supported | Licenses represent a user's professional license in a specific jurisdiction. Each License tracks compliance status, due dates, renewal dates, and credits needed. We preserve all license records including prior-period compliance flags and the jurisdiction name. |
| Courses | Fully supported | Courses are the CE training units offered or attended. Each Course carries credit amounts, format type, provider, and practice-area tags. We extract full course definitions including any custom fields before migrating to the destination system. |
| Attendance | Mapping required | Attendance records link a User to a Course and record the credits earned. When the destination system uses a different relationship model (e.g., Enrollment objects), we map the attendance data into the target's equivalent object and preserve the credit value per record. |
| Compliance | Mapping required | Compliance is a computed state per License, not a standalone object. It aggregates credits earned against credits needed for a reporting period. We reconstruct the compliance picture from License and Attendance data during migration rather than trying to export a Compliance record directly. |
| LearningTracks | Mapping required | LearningTracks group multiple Courses into a curriculum path. Where the destination HRMS does not support LearningTracks natively, we flatten the track into individual Course enrollments and preserve the track assignment as a custom property on each enrollment. |
| Providers | Fully supported | Providers are the entities that deliver CE courses. Each Provider may be associated with multiple courses and may carry state-specific accreditation. We export Provider records with their accreditation metadata intact. |
| PracticeAreas | Mapping required | PracticeAreas tag courses and sometimes user preferences to a legal, accounting, or clinical specialty. We preserve practice-area tags as custom fields on course and user records when the destination does not have a native PracticeArea object. |
| Affiliations | Mapping required | Affiliations link Users to Firms, Departments, or Offices. When the destination HRMS uses a different organizational hierarchy model, we map the affiliation structure to match the target's org-unit model. |
| Schedules | Fully supported | Schedules define when and where a Course is offered. We export Schedule records including date, time, timezone, and location fields so that enrollment calendars can be rebuilt in the destination system. |
| Custom Objects (Firm System Tables) | Mapping required | CE Manager allows firms to define custom system tables beyond the standard objects. We discover any custom tables during scoping, extract their schema and data, and map them to the destination's custom object model. This requires explicit schema discovery since custom objects vary by firm. |
| Materials | Mapping required | Course materials are associated files or documents. We export available Material records and their links to Courses. Binary file migration is handled separately from record migration, with material URLs preserved where accessible. |
Gotchas
What to watch for in CE Manager migrations
Issues we've hit on past CE Manager migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Custom Firm System Tables are not publicly documented
Compliance is computed, not stored as a record
API rate limits are not publicly documented
Title merging creates duplicate user records
| Severity | Issue |
|---|---|
| High | Custom Firm System Tables are not publicly documented |
| Medium | Compliance is computed, not stored as a record |
| Medium | API rate limits are not publicly documented |
| Medium | Title merging creates duplicate user records |
Leaving CE Manager?
Where CE Manager customers move next
5 destinations CE Manager can migrate to.
How a CE Manager migration works
Four steps, CE Manager-specific
Connect
API key (via CEM Data API) into CE Manager. Scopes limited to read-only on the data we move.
Map
We translate CE Manager-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate CE Manager quirks before production.
Migrate
Full migration with CE Manager rate-limit handling. Rollback available throughout.
FAQ
CE Manager migration FAQ
Answers to the questions buyers ask most during CE Manager migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your CE Manager migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate CE Manager.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your CE Manager setup and destination — written quote back within a business day.