You can migrate the data using the migration tool and it works fairly well as long as you follow the steps and recommendations.
There are no issues with running 2 versions at the same time. We set a deadline for a month to get everything off the old system before we move the data. If you are looking at using 2 versions indefinitely outside of the migration windows you will need additional agent licenses
1 of 1 people found this helpful
You can migrate data easily if you are using the AMIGO route for your 11.6.x to 12+ transition. But AMIGO has it's own pros and cons to consider.
If you are not/did not use AMIGO for your transition, you can still migrate data, but you must do it manually. This can be time consuming especially if you are not familiar with the back-end database of version 11.6, and to a certain extent, the back-end of version 12+.
Generally, regardless of what products are involved, my recommendation for data migration is you only bring over active data. That is things such as:
- Active users
- Active KB articles
- Active CIs
- Active tickets*
Have a read through this topic for information about the FootPrints 12+ back-end and how you can perform some advanced importing.
Do you have a detail steps and recommendations if I would migrate all existing data, especially the knowledge base information?
Is the data migration is workspace base or I can do one for all?
Each type of data being moved over, assuming a manual data migration, and not via AMIGO, would require it to be built by hand specific to each.
So if you want to move workspace 1 tickets, and workspace 2 tickets, and workspace 3 tickets, that is 3 separate moves. And it could even be more if you start factoring in things like historical data (audit trail/history), linked records, etc.
It's possible. But it's time consuming.
Can you better explain your transition strategy and goals and the driving factor behind moving ticket data.
Do you have a sample of the SQL scripts to migrate 1 workspace or knowledge base?
Not really. Although some parts of scripts can be re purposed, in general everything is custom and specific to your environment.
There are three main parts:
- Exporting from your current system (you'll have different fields from others who use FP)
- manipulating the data to fit your new FP system (you'll have different fields from others also)
- importing into footprints (via FP import and/or SQL import)