Moving Off Captivate Classic – Planning the Migration
For many training teams, Captivate has been the workhorse for years: software simulations, quizzes, branching scenarios and a library of projects built up one release at a time. Then Adobe launched an all-new version of Captivate, and the old product became Captivate Classic. The files still open and the courses still publish, but everyone can see that the road ahead leads somewhere else. How do you plan a Captivate Classic migration without breaking the courses your people rely on?
Plan a Captivate Classic migration by inventorying every project, identifying the features each one depends on, choosing a target tool and piloting a few representative courses before moving the rest in batches. The all-new Adobe Captivate is a different product, not a simple upgrade, so you should not assume Classic projects will carry over cleanly. Some teams move to the new Captivate, some move to another authoring tool and some keep low-priority courses in Classic for a while. Whatever you choose, the projects with advanced actions, software simulations and custom widgets will need the most work, so find them early.
What Is Captivate Classic, and Why Plan a Move?
Captivate Classic is the name for Adobe's long-running Captivate product line, the one most developers learned and used for years. When Adobe released a rebuilt Captivate with a new interface and a different way of building courses, the older line took on the "Classic" label. Adobe's Captivate product page focuses on the newer product. Adobe has said that Classic .cptx projects aren't directly compatible with the new Captivate and has promised an import path, so check exactly what the current release can bring across before you plan around it.
You don't have to move tomorrow, but planning now beats a scramble later. Operating systems update, security teams ask about older software, and staff who understand Classic's quirks move on, so a migration done on your own schedule, a few courses at a time, is far calmer than one forced by a deadline.
Where Can You Migrate To?
You have three realistic paths. Most teams end up using more than one.
| Path | Good fit when... | Things to weigh |
|---|---|---|
| Move to the all-new Captivate | Your team likes Adobe's tools and your courses are mostly slides, media and quizzes | Classic projects may need rebuilding rather than opening; check feature support for what you use |
| Move to a different authoring tool | You want a tool your wider team already knows, or your courses need features another tool handles better | Every course is a rebuild; new licenses and training |
| Stay on Classic for now | Courses are stable, rarely updated and low risk | Plan an exit date; keep an installer and license records safe |
Before choosing, have one developer build a short sample course in each candidate tool, using a real piece of your content. A week of hands-on testing tells you more than any feature list.
Planning the Captivate Classic Migration, Phase by Phase
Phase 1: Inventory
List every Classic project you own, and for each one, record the title, the LMS course it feeds, how often it is updated, who owns it and where the .cptx source file is stored. Missing source files are common, so identify them now.
Phase 2: Feature Check
Open each project and document which features it uses. Advanced actions, shared actions, variables, software simulations, widgets, fluid boxes, quiz pools, branching and custom JavaScript all increase the effort. A plain course with slides, audio and a ten-question quiz is easy, while a software simulation with assessment mode and branching is not.
Phase 3: Triage
Sort projects into move now, move later, rebuild differently or retire. Old courses with low use are good candidates for retirement. Courses with frequent updates are good candidates to move first, because they gain the most from a tool your team will keep using.
Phase 4: Pilot
Choose three projects: one simple, one medium and one complex. Rebuild them in the target tool, publish them, load them into your LMS and test tracking, timing each one, because those three numbers form the basis for your estimate.
Phase 5: Migrate in Batches
Group similar courses and work through them in waves, reusing templates and fixes from the pilot. Retest every course in the LMS before switching learners over.
Which Classic Features Need the Most Attention?
Some features translate cleanly to almost any modern tool. Others rarely do, so pay close attention to these:
- Advanced and shared actions. These hold logic, such as conditional branching and scoring. Document what each action does in plain language before rebuilding.
- Software simulations. Classic's demo, training and assessment modes are a big reason many teams used it. Confirm how your target tool handles screen-recorded simulations, or plan to re-record.
- Widgets and custom JavaScript. These often need to be rebuilt by hand or replaced with built-in features.
- Fluid box layouts. Responsive projects may need their layouts redesigned rather than recreated.
- Quiz settings and reporting. Pass marks, attempts and how results are reported to the LMS should match the original unless you decide to change them.
Adobe's Captivate user guide is the place to confirm what the current version supports and how, since features continue to change.
Should You Migrate Everything at Once?
Usually not. A big-bang move puts every course at risk at the same time and ties up your whole team, while moving in waves lets you learn from the first batch and fix your process before you reach the hard projects.
If you have a large library, treat it like a production line rather than a series of one-off projects. The approach in our guide to batch course conversion applies directly: standard templates, a repeatable checklist, clear roles and a QA step that catches the same errors before they spread.
How Long Will the Migration Take?
Your pilot answers that question, which is why the pilot matters so much, since effort depends on the features each course uses far more than on its length.
To see how pilot results become a plan, consider a worked example with invented numbers. Say your simple pilot course took 8 hours to rebuild and test, the medium one took 20 and the complex one took 45. If your inventory shows 30 simple, 15 medium and 5 complex courses, the rough total is 240 + 300 + 225, or 765 hours. Add a buffer for SME reviews and LMS testing, then divide by the hours your team can realistically spare each week, and you have a timeline you can defend, built on your own numbers instead of a guess.
Protect What You Already Have
While the migration runs, keep Classic working for the courses that haven't moved yet. A few simple habits help:
- Store every .cptx source file, plus its linked media, in one shared location with a clear folder structure.
- Keep a record of your Classic licenses and installers so you can set up a machine if one fails.
- Publish a fresh copy of each course before you start, so you have a known-good version to compare against.
- Freeze content changes on courses in active migration, or you will end up making the same edit twice.
Train your developers on the target tool before the first wave, too. A team learning a new tool while also racing a deadline makes slow progress and avoidable mistakes.
What About Learners in the Middle of a Course?
Plan the switchover carefully, because when a migrated course replaces the old version in the LMS, anyone partway through the old one may lose their place. Choose a quiet period for the swap, notify learners in advance and keep the old completion records intact. For required training, check with whoever handles compliance before changing a course ID, since some audits look for an unbroken record.
Leaving Classic Without Leaving Learners Behind
A good Captivate Classic migration is a planned move, not a rescue. Inventory your projects, check which features each one uses, pick a target tool after real testing, pilot three courses and then migrate in batches. Retire what nobody needs, and keep stable low-risk courses in Classic only until you have a date to move them.
Your first task is a short one: list your ten most-used Captivate courses and note which ones use advanced actions or software simulations, because that short list will reveal where the real work is.