The brief sounds simple: the client changed the character, so move the animation onto the new rig. Then you open both files and discover the new rig names its controls differently, parents the arms under a different node, and uses a rotation order nobody documented. The "quick" transfer eats your afternoon.

Copying animation between rigs is one of those tasks that is trivial when the two rigs match and genuinely difficult when they do not. Knowing which situation you are in before you start is most of the battle.

Why the transfer usually fails

Four things break animation transfers, and they are almost always structural rather than artistic:

  • Different control names. L_arm_ctrl on one rig and arm_l_CTRL on the other means nothing matches automatically. Every tool that transfers by name stops here.
  • Different hierarchies. If a control sits under a different parent, the same local values produce a different world result. The pose looks right in the channel box and wrong in the viewport.
  • Mismatched rotation orders. Identical rotation values in XYZ and ZXY are not the same rotation. This is the source of most mysterious flipping after a transfer.
  • Different proportions. Longer arms or a taller spine mean translation values that were correct on the source rig now over- or under-reach on the target.

Notice that only the last one is really about the character. The first three are naming and setup problems, which is why they are solvable in a repeatable way.

The order that actually works

  1. Compare the two control sets first. Before transferring anything, list the controls on both rigs and see how many names match exactly. That number tells you whether this is a five-minute job or a mapping job.
  2. Build a mapping for the names that differ. Source control to target control, once. Every subsequent transfer between these two rigs reuses it.
  3. Check rotation orders on the main limbs. Shoulders, wrists, hips, ankles. If they differ, fix the target to match the source before transferring rather than debugging flips afterwards.
  4. Transfer rotations first, translations second. Rotations usually carry over cleanly regardless of proportion. Translations are the ones that need scaling when the characters are different sizes.
  5. Fix contacts by hand. Feet sliding, hands passing through props, hips floating β€” these need an animator, not a script. Budget time for it.
  6. Clean the curves. A transfer often leaves redundant keys and small noise. A cleanup pass keeps the graph editor workable, as covered in cleaning animation curves in Maya.

Copying versus retargeting β€” not the same job

It is worth separating two things people call by the same name:

Copying moves keys between rigs that share a similar structure. The controls correspond, so the work is mapping names and matching rotation orders.

Retargeting moves motion between fundamentally different skeletons β€” most commonly library motion capture onto a production rig. That needs a skeleton mapping and usually some re-proportioning, which is a different process; we walk through that case in getting Mixamo animation into Maya.

Using a copy workflow on a retarget problem is why some transfers produce a character that looks broadly right but wrong in every joint.

Doing it repeatedly without losing your afternoon

If you transfer between the same two rigs regularly β€” a hero and a stand-in, a game rig and a cinematic rig β€” the mapping is worth saving rather than rebuilding. That is the difference between a task you dread and a button you press.

AnimKit handles this side of the job: transferring animation between rigs and saving the setup so the second and third transfer take seconds rather than repeating the whole mapping exercise. If you also reuse individual poses across shots rather than whole performances, that belongs in a pose library instead β€” the trade-offs are in the Studio Library alternative guide.

Frequently asked questions

Can I copy animation between rigs with different proportions? Rotations transfer fine. Translations do not, because a longer arm reaching the same local distance ends up somewhere else in the world. Expect to adjust translated controls and fix all contact points by hand.

Why does my character flip after transferring? Almost always a rotation-order mismatch between the source and target control. Check the rotation order on the flipping control first β€” it is faster than re-keying.

Should I bake the animation before transferring? Only if you must. Baking flattens the curves into a key on every frame, which transfers reliably but is painful to edit afterwards. Transfer the keys themselves when the rigs allow it.

Is there a way to avoid remapping names every time? Yes β€” save the mapping between those two specific rigs and reuse it. That is the single biggest time saver when a project involves repeated transfers.

The bottom line

Copying animation between rigs fails for structural reasons β€” names, hierarchies, rotation orders, proportions β€” not artistic ones. Check those four before you transfer anything, do rotations before translations, and expect to fix contacts by hand. If it is a job you repeat, save the mapping once with a toolkit like AnimKit instead of rebuilding it every time. For the wider set of animator tools, see our roundup of the best Maya animation plugins.