Can I move a level sequence between projects

Development Cinematics & Media
, ,
1

The question says it all. I have a level sequence I created in one 4.25 project and I would very much like to migrate/copy it to another 4.25 project I’m working on. I tried migrating the level sequence (Right click on level sequence icon in content browser, choose Asset Actions, then Migrate). Lots of stuff migrated over, but not the camera or rig rail or related components.

So, does anyone know if this is even possible to do? Or do I have to (ugh!) redo the whole level sequence in my other project? (double ugh!!!)

2

I see no one answered you. Did you ever figure this out? I’m trying to do the same and ‘Migrate’ is not working well. :slight_smile:

3

Is the camera spawned or an existing object in level??
Is the camera track completely gone or just lacking keyframes?
Is it unlinked from the camera track in the sequencer?

4

I faced same thing, and after trying a few different approaches, the following steps worked well for me.

1. Prepare Your Source Project

  • Make sure your Level Sequence and any required sub-sequences are the only assets being used.
  • Remove any unused tracks or unnecessary references from the sequence to avoid pulling in extra assets.

2. Migrate the Level Sequence

  • In the Content Browser, right-click on the Level Sequence.
    → Select Asset Actions > Migrate.

3. Filter the Assets to Be Migrated

  • Unreal will show a list of all dependent assets.
  • Deselect everything except the Level Sequence and its required sub-sequences.
    → Uncheck any meshes, materials, sounds, or other assets you don’t want to include.

4. Choose the Destination Project

  • When prompted, browse to the Content folder of your target project.
  • Click OK to start the migration.

5. Check in the Destination Project

  • Open the migrated Level Sequence in the destination project.
  • Make sure there are no missing references or broken bindings.
  • If anything’s missing, you can reconnect or replace assets manually.

:memo: Tips for Cleaner Migrations

Tip Why It Helps
Use placeholder (dummy) actors Keeps your sequence lightweight and avoids pulling in heavy dependencies
Break logic into sub-sequences Makes it easier to manage and migrate only what you need
Include a minimal test map Useful for quickly verifying that your sequence works in the new project