The document discusses the challenges organizations face with legacy version control systems and emphasizes the need for modern accelerated development practices. It outlines the importance of adopting efficient version control solutions to improve productivity and reduce time wasted on merging and managing code. Perforce offers tips for successful migration away from legacy systems, highlighting the benefits of a scalable, collaborative infrastructure for continuous delivery.

1. The Acceleration
of Everything
Is your legacy SCM
holding you back?

2. Who are we?
Sven Erik Knop
Technical Marketing Engineer
Tom Tyler
Senior Consultant
With Perforce since 2007, originally
as a Senior Consultant, Sven has
helped many organizations migrate off
of their legacy version control systems.
Known to colleagues as “The
ClearCase Guy” before he discovered
Perforce in 1999, Tom consults with
Perforce customers large and small.

3. Agenda
• Challenges in modern development
• Role of the version control system
• Considerations for acceleration

4. Analysts: Accelerate Now
4
Waterfall
Agile
Continuous
• Annual releases
• Mostly manual
• Release more than
once a year
• Some automation
• Weekly/daily updates
• Massive automation
The days when a
successful
organization could
release software
once every 12 to 18
months are over.
Forrester, “Continuous Delivery is
reshaping the Future of ALM,”
Kurt Bittner, July 22, 2013
“
”

5. Developers Want Choice
Git Workspaces
Repo
Manager

6. IT Requires Manageability
• Complex release management
• Single hook for CI
• IP security and compliance
• Future-proof for growth and scale

7. Budget Demands Consolidation

8. Is your SCM holding you back?
• Developers wasting time waiting?
• Long code freezes to merge changes
between branches?
• Regressions in multiple releases,
customer-variants and custom drops?
• Unresponsive remote locations?

9. Legacy SCM Issues
• Subversion
“120GB and 5-6 Million files took 2 hours to sync”
“We spent one day a week merging changes”
• ClearCase
"Activities that take up to 20 minutes with Rational ClearCase
should only take 2 minutes or less, while utilizing a less expensive
infrastructure.”
“We have development centers throughout the world, and trying to
support that with ClearCase would have been a nightmare”

10. The Risk of Status Quo
10
Size
Load
Sites
1000’s users
Millions of xact/day
10+ sites
• Lower Productivity
• Poor Quality
• Weak Collaboration
• Slower to Market
Terabytes of data
Business Impact

11. Considerations for Success
• Move away from legacy
• Adopt a hybrid approach
• Consolidate to a future-proof foundation
• You are not alone!

12. Perforce Overview
• Fastest, most scalable, version management and collaboration
• Versions everything
12

13. Migration
Planning
Tips
• Engage experts early
• Be aware of options
• Drive the project hard

14. History
Conversion
Options
• Get Latest
• Detail History Import (DHI)
Part 1
Mechanical Conversion (Deterministic)
Part 2
Transforms – Visualize Life in Perforce
• Baseline & Branch Import (BBI)
The “BBI Now, DHI Later” Option

15. BBI
Basics
Capture Baselines and high-level Branching operations.
A Histogram defines interesting history to capture. Captures
file sets with correct contents at various points in time,
enough to build from.

16. General
Migration
Advice
• Get buy-in on acceptance
Criteria early
• Dry runs are critical
• Dry run deep!
• Expect iteration!

17. Other Things to Consider
Migrations are more than just source code
conversion …
Version Everything for Continuous Delivery!

18. Other Things to Consider
Migration for Builds,
Docs & Digital Assets
Server Deployment
Architecture
Build Tools, Defect
Trackers, Workflow
Managers
Systems Integrations
for Continuous
Delivery Pipeline
Cutover: Phased or
Grand Opening?
User and Admin
Training on new
system
Branching
Strategy
Developer Desktop
Tool Integrations
Continuous Delivery
Toolchain
Bridges for
Parallel
Operation?

19. THANK YOU!
• Please contact us for details
we didn’t address here!
• info@perforce.com
• info.perforce.com/migration