Design Migration strategy

maddy

We have 3 options to migrate the content from old system to Teamsite 6.5.
1. Using Source files ( flat file for webpages)
2. Using Intermediate XMLs generated by application. XSLTs are applied on these XMLs to get the final web pages.
3. From Database.

Can somebody help me in deciding the best strategy supported with Pros and cons for every option?
Thanks in advance

Adam Stoller

We have 3 options to migrate the content from old system to Teamsite 6.5. 1. Using Source files ( flat file for webpages) 2. Using Intermediate XMLs generated by application. XSLTs are applied on these XMLs to get the final web pages. 3. From Database. Can somebody help me in deciding the best strategy supported with Pros and cons for every option? Thanks in advance

Is it safe to assume that by "old system" you are not talking about and older version of TeamSite?

Does the old system contain versions of files, or just the latest version of the file? Does the answer depend on your choices of 1, 2, and 3? If so, please explain.

In general, it shouldn't really matter which route you go - as long as you fully develop the process through which you want the content to pass before it's stored in TeamSite.

Transferring the files as static HTML pages is fine as a first pass - the assumption being that you want to eventually change these into DCRs to be processed by PTs - which can be phased in.

On the other hand, if all the content is stored in a DB in a structurally defined manner - then developing a script to extract that information and store it into DCR format (assumes you develop the DCTs first, and then your process includes setting EAs on the results to make them truly DCRs) that might give you a bigger bang-for-the-buck because not only will you have migrated the content / data, but you will have also maintained (hopefully) the distinction between content and presentation.

Without knowing more details, it's hard to make more suggestions.