I'm Mr. Plastic

Plastic SCM for Perforce teams

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.

Why teams move from Perforce to Plastic SCM

Branching and Merging for DevOps

Branching and Merging for DevOps

Implementing branch per task, trunk based development and the full DevOps cycle requires fast branching and advanced merging. These are the two key concepts why Plastic started. Find more about our merge engine.

Git-like workflows… for huge repos and files

Git-like workflows... for huge repos and files

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.

Distributed development

Distributed development

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.

Performance

Performance

Perforce used to be known as the “fast scm”. Teams can’t migrate away for fear of losing speed or introducing network bottlenecks. We regularly outperform their expectations. Read how we do it.
Find how Telltale gets the best out of their network with Plastic.

Locking for unmergeable files

Locking for unmergeable files

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.

Gluon

Gluon

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

More advanced toolset

More advanced toolset

Together with core needs like branching, distributed or big files, many teams look for an updated toolset. Plastic provides advanced features like the Branch Explorer, Semantic capabilities and diff and merge tools.

Full Git integration

Full Git integration

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.
Learn more

Native Cloud

Native Cloud

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.

How to migrate your Perforce depots to Plastic SCM

We provide full assistance during migration

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.

Gradual migration from Perforce to Plastic SCM is available

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

How to learn more

You can check our features and browse our gallery to see what Plastic SCM can do and what it looks like.
You can request a session with our product experts to solve the questions that you might have.
And you can contact us for migration details or ask any questions.
​You can learn how other customers are using Plastic.
Or learn why companies choose Plastic SCM instead of Git.

Get the latest news