MII Migration Tool - Hidden Dangers

[Former Member]

Greetings All

We are moving from a 4 server 11.5 MII arena into a 1 Server 12.2 MII enviroment.

Trying out the Migration Tool on our early Testing (Tech) box we've migrated a project over and started tweeking it.  Later came back and realizing we had migrated from a less updated version we migrated again from the better source.

Looking at some of the tweeking we did earlier we realize that the Migration tool overwrote some of our transactions and other objects.

We discussed Migrating projects and then moving them to new Uniquely named final Projects in 12.2, but realize doing so would require tweeking each child object to show the new unique final project. 

Asking if there are best practices about this process if multiple migrations need to happen.

OR is there a way to do a find and replace within a project folder.  Also realizing that this could be just as dangerious.

Thank You,

Dennis W

[jcgood25]

Hi Dennis,

Understanding how your 11.5 file system folder structure becomes a 'project' should help you in determining your best plan of attack.  There is no question that there will be cases with folder names and project names (things like 'Common') where it could get some overlap.  Isolating things and refactoring your folders in the 11.5 environment is one approach, and may be your preferred option if you are learning the 12.2 environment at the same time. 

I assume you've been able to leverage the SCN migration guide and some of the tricks/tips it includes for planning and further study of your environment.  If not, please have a look - you can probably find it easily by searching for Erik Schrampf.

For search and replacing, I find that a good text editor like EditPlus works well if you need to do search and replaces across multiple files, but the newer versions of windows explorer also have some search option restrictions that tend to ignore file extensions that aren't office or basic format (like irpt, etc).

Obviously a bit hard to have all the answers, but my recommendation is to do your migration tests in small chunks, and you can always create a folder with the desired content (doesn't have to be the root source folders).  Learning how it works and what happens to the folder structures will probably help you better plan what to do in the 11.5 file structure, and then ideally it will lead to less new changes to be made in the new project structure, where your focus can then be on things that don't work like they used to, instead of finding what is a casualty of the jump forward.

Regards,

Jeremy