Skip to main content
This guide covers migrating your Unreal Engine projects from Perforce to Diversion, including feature comparison and a step-by-step migration process.

Why Consider Migration?

Diversion offers the same core version control functionality as Perforce with key improvements:
  • Smaller installation footprint (for the client, no need to set up any server)
  • Significantly faster commit speeds
    (Diversion continuously uploads in the background; committing is the moment you save a snapshot into your history)
  • Simplified UI focused on essential workflows
  • Better user experience for artists and non-technical team members

Feature Comparison

Soft Locking vs. Hard Locking

Diversion automatically indicates when a file is being edited (soft lock)—no one needs to explicitly take authorship. You’re not blocked: you can confirm editing via the prompt and proceed. If a teammate’s version was committed, you can merge it into your branch (auto-merge on same branch when there’s no conflict). Some teams require hard locks; see Hard Locks for details on configuring exclusive file locking. Why this matters:
In Perforce, you must explicitly take authorship of a file (check-out). If someone else has it locked and is unavailable to release it (vacation, sick, etc.), you’re deadlocked.
In Diversion, the backend automatically and implicitly signals active edits without blocking your work.
What this means in practice: two people can edit the same file at once, and the difference is settled afterwards rather than prevented up front. For a step-by-step walkthrough of that scenario — who sees what, when the conflict appears, and how it is resolved — see Soft Locks.

Migration Options

You can move a Perforce project to Diversion in two ways. Both start from the dashboard (click the Diversion logo at the top left). Option 1: Import from P4 – Brings over your full Perforce history. Choose Import from Perforce on the dashboard. If it isn’t there, click New repository at the top right and select Import from P4. Then follow Import from Perforce. If you’d rather we run the import for you, choose Request a managed import at the bottom of that page. Your +S retention rules can be carried over as Diversion revision limits. Option 2: Create New Repository – Starts with a clean slate, without history. Setup is faster, so you can start working right away. This guide uses Option 2:
1

Create the repository from your Perforce project folder

Choose Create a repository on the dashboard. If it isn’t there, click New repository at the top right and select Create New Repository. Choose Create from Existing Folder, click Browse…, and select the root folder of the project you used with Perforce. For an Unreal project, that is the folder with the .uproject file. Click Create. See Start using Diversion in your project for the full dialog.If you’re using Unreal, Godot, or Unity, Diversion sets up the .dvignore file for you, skipping folders that are temporary or rebuilt by the engine.
2

Invite your team

Open the repository’s … menu and select Collaborators. Enter a teammate’s email, choose an access level, and click Send invite. See Manage project access.
3

Make the first commit

Open the repository. Select the files to commit, enter a commit message, and click Commit. See Commit your changes.

Starting from an existing Perforce workspace

Perforce keeps files read-only until you check them out. When you create a Diversion workspace from a folder that Perforce managed, those files stay read-only. Diversion can’t sync your teammates’ changes into read-only files, and Unreal Engine treats them as checked out. When a sync is blocked this way, Diversion reports:
To fix this, clear the read-only flag on every file and folder in the project:
In File Explorer, right-click the project folder and select Properties. Clear Read-only, click Apply, and choose Apply changes to this folder, subfolders and files.Or run this from the project folder:
Stop using the folder with Perforce once you move it to Diversion. Every Perforce sync makes the files read-only again. If you still need the Perforce workspace, create your Diversion workspace from a copy of the folder.

Commit Time

With Diversion, your workspace is continuously synced to the cloud. Committing is the moment you choose to save a snapshot into history. Because the files are already uploaded, commits are fast, even for large Unreal Engine projects. Once the first commit is done, your project lives both on your machine and in the cloud, ready for collaborative work.

Unreal Engine Integration

To work with Diversion inside the Unreal editor, add the Diversion plugin to your library on Fab, install it to your engine from the Epic Games Launcher, and select Diversion as the revision control provider. Unreal Engine Plugin walks through each step.

Perforce actions in Unreal Engine

Most of the revision control actions you used with Perforce are in the same places in the editor. Right-click an asset in the Content Browser and open Revision Control:

View and commit pending changes

Click Revision Control at the right end of the status bar, at the bottom of the editor, and select View Changes. The View Changes window lists every modified asset under the Workspace Changes changelist. Double-click an asset to locate it in the Content Browser. From the Workspace Changes changelist you can edit its description, validate it, or commit it. When you commit, enter a Commit Message and click Commit. Click Save instead to keep the description and commit later. To commit without opening View Changes, click Revision Control in the status bar and select Commit Changes.