Fresh TeamSite 6.5 but with 5.5.2 content.

still planning for upgrade from 5.5.2 to 6.5:
i was thinking, is this good idea to do it:

i will get fresh new machine wiht all the conponents to meet TS 6.5 requirements, install teamsite 6.5 and migrate the contents from 5.5.2 "orginal version i dont even think that they have any patchs or Service packs installed"... and from there, link the new teamsite to anything that the old teamsite was linked to?

PS: we only use teamsite to manage the content.. like import files from the machine to be deployed and export them to be edited.
we dont make any DCTs or DCRs, we dont use/create any workflows for teamsite. the entire contentstore is just bunch of static HTML pages and banches/sub-branches.

plz let me know what you think, and any suggestions to make this upgrade as quick and smooth as possible is very appreciated.
thank you.

Find more posts tagged with

Comments

nipper

That is a reasonable approach, provided you do not need any of the history or editions from 5.5.2

BTW, what about the configurations ? Do you have an admin or config branch where you check in all the modifications to files that live in iw-home ? If not, then create one. Start moving the files (workflows, etc) from 5.5.2 to 6.5. Some will require modifications.

Andy

CRB

well, i still dont have access to where the config files are. but i will let you know when i get that info and full access in the next two days.
so you think, in this case, i wont need to migrate? you said "start copying wflows..." or are there certain things that iwill need to migrate like "contentstore", but for other config files i can just copy them?.. i may sound like i m confusing myself. and the info provided here are not very detailed.
but i just want to get as much info as i can before i put the plan together.
thank you for ur input!

nipper

What needs to be moved ? I don't know as I did not build your system. That being said, I have multiple directories under my config branch, they include custom (for custom code), httpd (custom menu items, cgis, etc), iw-perl (new perl modules), local (templates, GUI customization, and WFTs).