Few projects make a certification team more anxious than a data migration, and for good reason. Your data—every application, exam result, and renewal—is the history of your program and your people, often reaching back decades. When that history moves to a new platform, it has to arrive complete, accurate and ready to use.
Accomplishing that means choosing the right migration partner and the right certification platform. Your partner should know how to decide which records to bring over, protect the rules behind your records, and keep your history organized. Your platform should be able to put those records to work, apply the right rules to each one, and make your history easy to find when a verification, report or audit calls for it.
ROC-P has migrated decades of historical records for certification programs across industries, giving us unique insight into the ways this process typically goes wrong. Here are the three mistakes we see most, and how to avoid each one.
Mistake 1: Trying to Bring Everything With You
Whether your certification program runs on Microsoft Access, spreadsheets, a homegrown database or a system you’ve long outgrown, the instinct is to move every bit of historical data. That’s likely unnecessary, and a good way to add cost, complexity, or time to your transition.
Most data migration plans start with the certificant record, which shows who holds the credential and since when. That’s perhaps the most important record in your system, but it also represents the smallest share of your dataset, likely around a single-digit percentage of your organization’s credentialing-related data, according to ROC-P’s migration experience.
Most of your data involves tracking continuing education records, followed by renewals and exam registrations. That data may be decades old, however, and have no bearing on a certificant’s current certification status; because every record you move to your new system has to be mapped, cleaned, and checked, these files can easily balloon the time and effort needed for your transition to a new certification management system.
How to avoid it: Sort every record into one of three places before you migrate.
- Take it: Records your team works with or your certificants depend on. These move into your new platform as active, usable data.
- Archive it: Records you’re required or wise to keep but rarely touch. They stay secure, readable and searchable outside your day-to-day system.
- Let it go: Records that are redundant, obsolete or trivial, and past any retention requirement. These are handled according to your records retention policy.
Many programs find a sizable portion of records belong in the middle category. Closed, older records often matter for an audit or an occasional lookup, yet they rarely need to sit in your active system.
4 Questions for Sorting Your Certification Records
To sort them, work through these four questions in order. The first “yes” decides where a record goes.
- Is it still open? In-progress applications, scheduled exams, accommodation requests, current CE cycles and unresolved appeals all come with you. Take it.
- Does anyone need it to confirm someone’s status? Verification is one of a program’s core obligations, and the National Commission for Certifying Agencies (NCCA) requires accredited programs to verify current certificants on request. Take it.
- Does your team use it to do its job? If staff pull it for renewal outreach, CE audits, annual reporting or board updates, it belongs in your active system. Take it.
- Does your retention policy, accreditor or the law require you to keep it? NCCA-accredited programs must have a retention policy covering applicants, candidates, and current and former certificants. ISO/IEC 17024 sets a minimum of one full certification cycle for keeping these types of records. Archive it.
If the answer to all four is no, the record is a candidate to let go. Retention requirements vary by program and jurisdiction, so confirm yours with counsel before anything is removed.
Mistake 2: Leaving the Rules Behind
A record only makes sense alongside the rules it was created under. Every era of your program has had its own policies, such as lifetime certifications, earlier CE requirements and pathways you’ve since retired.
In older systems, those rules often live in workarounds, custom code and staff memory. If your new certification management platform reads a 1987 record by 2026 rules, it could flag a lifetime diplomate as lapsed.
The same gap can send renewal notices to people who don’t need them, flag CE shortfalls that don’t exist, or return the wrong answer to a verification request. Each one costs your team time to fix and costs your certificants confidence in your program.
Rules that often hide in legacy data:
- Lifetime and grandfathered status: certifications that never expire, or that were granted under earlier criteria.
- Retired pathways: eligibility routes your program no longer offers.
- Past CE requirements: different hour totals, categories or cycle lengths from earlier eras.
- Status codes only staff understand: abbreviations and custom fields whose meaning was never written down.
- One-off exceptions: extensions, deferrals and waivers granted case by case.
How to avoid it: Treat the rules as part of the data you’re moving.
- Build a rules timeline. For each era, record the eligibility, CE and renewal policies that applied and when they took effect. Old handbooks, board minutes and past policy changes are good sources.
- Interview the people who remember. Long-tenured staff often know the exceptions no document captures.
- Define every status code and custom field before it’s mapped to your new system.
- Test the edge cases. Before go-live, pull a sample of lifetime, grandfathered and extended records and confirm your new platform reads each one correctly.
Bring program and policy staff into the process alongside IT, and ask any partner you’re evaluating how it handles records created under retired rules. Your rules will keep changing, which is why configurable software matters more than custom code.
Mistake 3: Treating the Archive as an Afterthought
Archiving lightens your active system, but it only works if your history stays within reach. When the archive gets planned last, records end up in files no one owns, identifiers stop matching the new system, and the old platform gets shut off before anyone checks that the history can be found.
How to avoid it: Plan your archive with the same care as the migration.
- Name an owner. Decide where the archive lives and who is responsible for it.
- Keep the identifiers. Use the same certificate numbers and candidate IDs in your archive and your new system, so records stay linked.
- Keep the context. Dates, decisions and approvals should travel with each record.
- Set a review schedule. Check the archive against your retention policy, and let go of records once they’re past it.
- Test retrieval before you shut anything off. Run a few real requests against the archive while the old system is still available.
Before you sign off on your plan, ask each platform you’re evaluating how it handles very old records and what migrating them involves. Their answers will show you how each platform would bring your history forward, and what it will take to get there.
Plan for a Smoother Data Migration with ROC-P
Data migration takes care, a dedicated plan, and the right partner. Done right, it can be the moment your program gets a cleaner, more useful picture of its data.
ROC-P supports certification programs through the implementation process, from planning what to take, archive or let go, to moving your data and rules into a configurable platform and getting your team ready to use it.
We work alongside your program and policy staff as well as IT, so the rules behind your records come with them.
Bring your answers to a conversation with our team, and start finding your fit with ROC-P.