Perforce is the industrial-strength version control system that leading companies used for 20 years, especially in the gaming industry.
Here we explain why nowadays teams are moving away from Perforce to Plastic SCM. It can help you find out whether Plastic will work for you too.
We find many teams willing to adopt distributed development and choose Plastic because they handle large binaries and their repos are big.
Lately, teams going for mono repo strategies call us too.
Plastic SCM is a DVCS by design. Clone entire repos, just a few branches, or anything in between. Teams with distant offices and members working remotely find this feature a must.
Locking might be a thing of the past for code, but assets, images, videos, and documents are still largely unmergeable. Many teams find our optional locking a must.
Our super-simple workflow for all things not-code. Team members used to simple checkin workflows feel at home with it.
Learn more about Gluon
Plastic SCM speaks the Git protocol. This means you can run Plastic as a GitServer or connect push/pull to any Git service (like GitHub Enterprise) as if it was a Git Client.
We provide our own Plastic Cloud service to work both centralized and distributed. When teams don’t want to continue hosting their own infrastructure, they rely on Plastic Cloud to host their projects, with full encryption.
We have an ad-hoc importer to move depots from Perforce to Plastic SCM. Very often Perforce depots are huge (something especially true for game studios, where gigabytes of data are not uncommon), so we prefer to provide full assistance.
It is very simple: you contact us and we help you with the process.
Our P4 exporter works in two directions: it can import from Perforce to Plastic, and export from Plastic to Perforce.
Very often teams need to migrate gradually. They move part of the project to Plastic while the rest of the team still stays in P4. Normally, they use a branch as the rendezvous point for this; they can checkin changes to this branch in P4 to deliver changes, pull it to Plastic, and vice-versa - make changes in Plastic and push them to the P4 "sync" branch