Skip to main content
This page covers migrating existing Altoura content into the current authoring environment: trainings (using Prodigy) and asset bundles (using the Unity migration export tool).

​
Training Migration

Use Prodigy to bring an older Altoura training into the current authoring environment. Open Prodigy at prodigy.altoura.com.
The migration creates an editable draft. It does not change the original training or publish the new training automatically. Review and test the draft before you publish it.

​
What you need before you start

Make sure that:
  • You can open Prodigy and access the organization that contains the training.
  • The older training appears in the Legacy Training list.
  • A current target scene has already been created in the same organization.
  • The target scene contains the current versions of the equipment or 3D models used by the training.
  • Your administrator has enabled access to the older training’s images, videos, audio, and 3D files, if the training uses them.
If the training does not use 3D equipment, you can still migrate its instructional content. A target scene is required before the finished training can display its 3D environment.

​
Start a migration

  1. Select the appropriate Organization from the Org dropdown.
  2. It is recommended to create a New Session for each Training migration.
  3. Open the Documents panel in Prodigy.
  4. Select Add, then select Legacy Training.
  5. Search for the training by name, product, or training family.
  6. Select the training you want to migrate.
  7. Under Target scene, select the current scene that contains the training’s equipment or 3D models.
  8. Select Import and migrate.
Prodigy retrieves the older training and starts the migration in the chat panel. You do not need to download or upload a training file yourself. Selecting a target scene before you start is the easiest option. If you leave Target scene empty, Prodigy asks you to choose one in chat. You can create an initial draft without a scene, but you must select a scene and review the equipment links before the training is ready to run.

​
Choose the target scene

Think of the target scene as the current 3D environment in which the training will run. Choose the scene that:
  • Contains the correct equipment or facility.
  • Contains the current versions of the models used in the older training.
  • Is available in the organization you are currently using.
The scene name does not have to match the training name. If several scenes have similar names, choose the one with the correct equipment and model placement. If the scene is not listed, ask your administrator to confirm that it has been created and that you have access to it.

​
Review the draft

When the migration finishes, Prodigy creates a working draft and summarizes the result in chat. The summary may tell you that some items were imported automatically and that other items need review. Ask Prodigy questions such as:
When Prodigy asks you to choose between equipment or model parts, select the item that matches the older training. It will not guess when two objects have the same or a similar name. Before publishing, review at least:
  • The order of the steps.
  • Step instructions and panel placement.
  • Branching choices and where each choice leads.
  • Equipment or model parts used in tap, move, rotate, visibility, animation, or transform instructions.
  • Images, videos, audio, and any 3D objects that appear in the training.

​
Validate, test, and publish

When you are satisfied with the draft:
  1. Ask Prodigy to validate the training.
  2. Fix the errors it reports. You can ask Prodigy to correct safe formatting problems, but you must make decisions about missing equipment, incomplete choices, or changed behavior.
  3. Open the training in the authoring or player experience and test the important steps.
  4. Ask Prodigy to finalize and publish the training.
Validation checks that the draft is complete and that its steps, transitions, choices, and actions are connected correctly. A successful validation does not replace testing: it confirms that the training is structurally correct, not that every instruction looks or behaves exactly as intended. If the training name is already in use, provide a different name when you ask Prodigy to publish it.

​
What carries over

The migration carries over the older training content that has an equivalent in the current platform, including:
  • Training steps and their order.
  • Step instructions, text panels, and panel positions.
  • Tap, move, and rotate interactions.
  • Branching choices when the older training contains enough information to identify each destination.
  • References to equipment, model parts, and 3D objects.
  • Supported visibility, transform, teleport, and animation actions.
  • Images, videos, and audio when the source files are available.
  • 3D objects that are created when a step starts and removed when the step ends, when their source files are available.
  • Input fields and their validation rules when they were defined in the older training.
  • Supported navigation actions such as returning home, logging out, or reloading an experience.

​
When you may need to make changes

Some older behaviors do not have a direct equivalent in the current platform. Prodigy preserves as much information as possible and flags the item for review. You may need to make changes when the training contains:
  • A missing or duplicate equipment reference: The current scene does not contain the referenced object, or more than one object could match it.
  • Missing media: An image, video, audio file, or 3D object could not be read from the older media store.
  • Incomplete choices: A choice has text but no reliable destination in the older training.
  • Randomizer steps: Older randomizer behavior is not reproduced as a probability-based branch and may need to be redesigned.
  • UI Control actions: These older actions need to be rebuilt using the current interaction tools.
  • ReloadSpace navigation: This older navigation behavior has no direct current equivalent and needs review.
  • DID: Steps with Delayed Instruction Display (DID) enabled will be migrated as regular steps, as DID is not yet supported in the current system.
  • Linked Steps: Linked Experiences are not yet supported in the current system.
Media that has already been imported is reused when the same source file is encountered again. Re-running a migration should not create a new catalog copy of the same media file.

​
Troubleshooting

​
No legacy trainings are listed

Confirm that you selected the correct organization and that the older training is available to your account. If the list is still empty, ask an administrator to verify access to the older Altoura training system.

​
The target scene cannot be found

Search using a shorter or exact part of the scene name. If it is still missing, confirm that the scene exists in the current organization and that you have permission to use it.

​
Prodigy cannot find an equipment or model part

Confirm that the target scene contains the current version of the equipment or model. If several objects have similar names, tell Prodigy which one is correct.

​
Images, videos, or audio are missing

Ask an administrator to verify access to the older media store and the current asset catalog. After access is fixed, rerun the migration or import the missing files into the current catalog and repair the affected steps.

​
Validation reports errors

Ask Prodigy to show the exact step or transition associated with each error. Fix the reported items, validate again, and only then publish the training.

​
Terminology

​
Asset Bundle Migration

Asset bundles are migrated with the Altoura Migration Export Unity tool, which exports prefabs and scenes into .altpkg.zip packages for import into the Altoura Scene Editor. For setup and usage instructions, see the unity-migration-export repository.