Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    9
  • Subscribers subscribers
    7
  • Views views
    1699
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Serena Changeman Dimension 9.1 to GIT Migration

MigrationDeletedUser
How to migrate the data's from Serena Changeman Dimension 9.1 to GIT.
Parents
  • 0
    1) Identify "What" you want to migrate...
    a) All Versions/Baselines/Types/Comments/History etc etc
    b) All Item-Item relationships?
    c) All Change/Problem/Release/Bugs etc - History/Comments etc etc

    Or possibly "just" Production-ised Item Revisions (Items @ final lifecycle state? or possibly Items contained in Baselines that have been deployed to Production?)

    Once you know exactly what you want to migrate............... then we can set about solving that (rather than the rather open ended query)

    As examples......
    20 years of Development will almost certainly have an awful lot of Item revisions that never made it past (early stage) testing.... Do you really want to keep them?
    Plus (if you are using full Dimensions functionality) records of bug fix cycles/change cycles etc from 20 years ago might not be worth migration.
    Most (if not all) of your technology from 20years ago could well be totally "un-usable" now.....
    Obviously Dimensions 9 (while not 20 years old) isn't really compatible with current Dimensions - Any triggers/interfaces etc set up then probably wouldn't "directly" work now.... So it'd be the same for lots of your other stuff....
    20 years ago it could be coded for Windows 98 (even 95) - not even XP...... and I doubt any of it would even run....

    Obviously the GIT part is irrelevant until you know what is worth migrating....
Reply
  • 0
    1) Identify "What" you want to migrate...
    a) All Versions/Baselines/Types/Comments/History etc etc
    b) All Item-Item relationships?
    c) All Change/Problem/Release/Bugs etc - History/Comments etc etc

    Or possibly "just" Production-ised Item Revisions (Items @ final lifecycle state? or possibly Items contained in Baselines that have been deployed to Production?)

    Once you know exactly what you want to migrate............... then we can set about solving that (rather than the rather open ended query)

    As examples......
    20 years of Development will almost certainly have an awful lot of Item revisions that never made it past (early stage) testing.... Do you really want to keep them?
    Plus (if you are using full Dimensions functionality) records of bug fix cycles/change cycles etc from 20 years ago might not be worth migration.
    Most (if not all) of your technology from 20years ago could well be totally "un-usable" now.....
    Obviously Dimensions 9 (while not 20 years old) isn't really compatible with current Dimensions - Any triggers/interfaces etc set up then probably wouldn't "directly" work now.... So it'd be the same for lots of your other stuff....
    20 years ago it could be coded for Windows 98 (even 95) - not even XP...... and I doubt any of it would even run....

    Obviously the GIT part is irrelevant until you know what is worth migrating....
Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.