Forum Discussion
igssv
Cirrus
CirrusUnable to migrate using F5 journeys
Hello everyone, I hope you're all doing well. I've come across an issue during my migration process using "journeys" and would really appreciate any insights or solutions you might have. Here's a b...
Jeffrey_Granier
Employee
EmployeeHello,
I dont believe JOurneys will convert from TMOS 12.1 to 17.1 Please see the migration path below:
One option to consider an upgrade to v13 on your original system and then jump to 15 on rSeries tenant then upgrade that to 17.x.
In order to get to 17.x you will need to be on 15.x or higher.
igssvJeffrey, thank you for your input.
I successfully managed the migration using journeys by following these steps:
- Migrated from the existing UCS (v12) to the r2600 tenant (v15).
- Then migrated from the r2600 tenant (v15) to the r2600 tenant (v17).
Initially, I was attempting the following procedure:
- Migrated from the existing UCS (v12) to a UCS (v15).
- Then from UCS (v15) to r2600 tenant (v17).
I realize now that the mistake in my initial approach was trying to migrate in two steps while the UCS content remained at v12. Your advice was a great help!