We have extensive experience in PLM data migrations, having successfully migrated major companies like John Deere, Dell, and Raytheon. Data migration is difficult due to unpredictable data quality issues that could disrupt operations. Thorough planning including testing and validating the data in increments is recommended over attempting a "big bang" approach. While full history migration is challenging, most companies do not need versions older than the latest.

1. data migration.

2. We believe customers should be assisted in making
informed decisions about Product Lifecycle
Management
o Learn more about us and how we can help you implement a Product
Lifecycle Management (PLM) Platform tailored to support your business
model and focused on your business initiatives.
At zerowait-state.com
“PLM is in our DNA”
Zero Wait-State.

3. our company.

4. our customers.

5. core competencies.

6. implementation products.

7. integration products.

8. We have extensive
research in PLM and data
migration.
– Major migrations at John
Deere, Dell, Raytheon
and Maxtor
– Successful migrations
from Intralink and
PDMLink to Enterprise
PDM
the experience.

9. Data migration is
hard...very very
hard.
Data condition is a
variable hard to
predict which must
be done without
disrupting current
production
environment
the facts.

10. • It’s a critical process.
• Product data is the
lifeblood of a
company
• Bad data can render
a PLM or PDM
system useless
the process.

11. the big bang bad idea.
• Moving it all is
problematic
• Moving increments is
more manageable
• Eliminates time
constraints
• Reduces Risks

12. • Extracting and
transferring history to
a new PLM is
challenging
• Most companies
rarely access earlier
versions of data
• Using a “latest only”
dramatically reduces
costs and complexity
history is best forgotten.

13. • Just because you can
migrate all your data,
doesn’t mean you should.
• Take a hard look at legacy
data and be selective
• Do not pollute your new
system with corrupt or
inaccurate data
• Don’t “under provision”
hardware
• Identify needs and have
analysis of data cleansing
solutions ready
• Clean up data as much as
possible
garbage in, garbage out.

14. • Two test passes and a
production pass are
minimum
recommendations for
most migrations
• Have a specific test
plan to evaluate data in
the test system
• Resist the urge to
truncate testing
test. validate. repeat.

15. mission accomplished.
• Moving Intralink 3.4 to enterprise PDM
• Joint project with GoEngineer
• Extracted meta data and binary files from Pro/Engineer
from Intralink
• Used drag and drop to load the CAD files and an import
tool for GoEngineer for the meta data
• Customer was successful and shut down two servers

16. mission accomplished.
• Moving from PDMlink 9.0
• Joint project with GoEngineer
• Using drag and drop to load the CAD files and
sent meta data to Agile PLM
• Customer successfully transitioned from PDMLink
to Agile PLM and EPDM

17. conclusion.
1. Data migration is tricky
2. Data migration is
important
3. Preparation and planning
can alleviate issues
4. Incremental migration
without history is best
5. Beware of undermining
the difficulty of migration

18. zero wait-state.
follow us!!
www.facebook.com/zerowaitstate http://linkd.in/VqVdda twitter.com/zerowaitstate