When an exported file contains the wrong animation or no usable clip, begin with a one-clip test. A large file with many actions makes it harder to distinguish an exporter-selection problem from an importer-configuration problem.
Identify the exact source action
Record the action name, intended target and frame range. Play it on the intended rig in Blender before exporting. Confirm that you are not inspecting a different action or an unintended NLA combination.
Keep the original file. Use a duplicate with the unrelated animation temporarily removed from the test rather than deleting production actions to simplify the export.
Read the exporter animation settings
Check which animation sources the chosen exporter includes in your installed version. Action and NLA handling can depend on the format and settings, so avoid a universal checkbox recipe.
Export one short, clearly named clip with an obvious pose change. Inspect the destination’s imported animation list and range. If that works, add the remaining clips in small groups and check their names and boundaries.
Compare evaluated motion, not just clip names
A listed clip can still contain the wrong skeleton or incomplete constraint-driven motion. Play it on the intended character and check the beginning, middle and end.
Save the successful exporter configuration together with a tiny diagnostic file. This gives the team a known-good example when a later character appears to lose an action.
For the bigger picture, use our free Rigify migration workflow and three-engine import test plan.
Official references and scope
Sources checked October 18, 2026. Interface names and capabilities can change; use the documentation for your installed version. The workflow above is an editorial checklist, not a published hands-on benchmark.

