Use this page before setting up your own maps and systems. Migration moves Hyper content into your project. Integration connects the migrated content to your own GameMode, PlayerController, Character, GameState, PlayerState, data tables, project settings, and example maps.

Related setup: Use the Automatic Integration Tool, Set Up Your Map to Play In, Gameplay Tags, Datamanagement, System Atlas.

Before You Begin

• Back up your project and any important data tables. Use version control.
• Close the target project before migrating content into it.
• Check which plugins are enabled in the Hyper project, especially Common UI and any plugin required by the module you migrate.
• Review config files for gameplay tags, physical surfaces, trace channels, object channels, input, and other project settings.
• Decide whether you are migrating a full system or only a specific component.

Recommended: Use the Automatic Integration Tool

Migration and integration can be tedious, especially when you own multiple Hyper systems. The free Hyper Integration Tool can automatically create an integration project from the Hyper projects you own.

The tool is strongly recommended when it fits your setup. You should still review the generated project, remove logic for systems you do not own, and verify your GameMode, components, data tables, and required world actors.

Get the free Integration Tool

Migration Steps

1. Open the Hyper project that contains the system you want to use.
2. Select the content or actor component you need.
3. Right-click and use Unreal’s Migrate tool. Do not copy files manually, because migration keeps references intact.
4. Migrate into the Content folder of your target project.
5. Do not overwrite existing files unless you are certain. Be especially careful with data tables.
6. Open the target project and let Unreal load, compile, and discover any missing references.

Integration Steps

1. Open the provided Hyper example map in your target project.
2. Press Play and confirm the example map works before changing your own map.
3. Check which components are assigned to the example Pawn, Character, PlayerController, GameMode, GameState, and PlayerState.
4. Add the required components to your own matching classes.
5. Merge or restore data tables only after making a backup. When needed, export as JSON, merge carefully, and re-import.
6. Resolve Blueprint compile errors, missing plugins, missing gameplay tags, and missing collision channels before continuing.

Verify Before Moving On

• Every example map you migrated can be opened.
• Every example map can be played without blocking errors.
• The Output Log does not show missing classes, missing components, or invalid data table rows for the migrated systems.
• Your project has the required plugins enabled.
• Your project settings include the required tags, surfaces, trace channels, and object channels.
• Your core classes compile: GameMode, GameState, PlayerController, PlayerState, and Character.

Common Things to Check

Next Step

After migration and integration, continue with Set Up Your Map to Play In. If you used the Automatic Integration Tool, use that page to verify GM_Hyper, required components, and world actors in your own map.