Teams are switching from Perforce to Diversion because they want a modern, scalable version control system without the heavy server management, complex admin work, and high infrastructure costs often associated with legacy Perforce setups. Diversion supports the workflows game studios need, including large files, binary assets, exclusive file locks, branching, code and asset reviews, and conflict-prevention alerts. It also offers a modern UI that is easier for both developers and artists to use, dedicated Unreal Engine and Unity integrations, and flexible deployment options including cloud, private cloud, on-premises, and hybrid. Diversion can help teams reduce total version control costs by up to 70 percent compared to Perforce, while supporting large repositories and complex creative projects at scale.

Yes. Diversion supports exclusive file locks (hard locks) for binary assets, the same workflow Unreal Engine and creative teams use in Perforce. Locks are surfaced in the Unreal Engine plugin and the web UI. Diversion also adds Conflict Prevention Alerts with instant cross-branch checks, helping teams prevent asset conflicts before they reach the repository, reduce broken builds, and keep collaboration smoother across branches.

Yes. Diversion is designed for AAA-scale projects with massive binary asset libraries. Commits of 400,000 or more files complete in under a minute, and there are no practical limits on repository size.

Performance varies by workflow, but the most-cited improvements are: branch creation in seconds versus minutes on large Perforce streams, real-time sync of file changes across team members, and commit operations that scale to 400,000 or more files per minute.

Yes, and it's officially recommended by Epic Games. The Diversion Unreal Engine plugin is available on FAB, supports commit, sync, and history directly from the editor, and is the highest-rated VCS plugin in the marketplace. Native Unreal Game Sync and Horde integration are also supported.

Diversion provides automated migration tools to help teams move from Perforce, including importing depot history, supporting existing workflows, and offering bi-directional sync for a safer, gradual migration. This allows teams to run Diversion alongside Perforce during the transition, reduce risk, and avoid switching everything at once. Hands-on migration support is available to help teams move confidently, with many teams completing the move in days, not weeks.