¿Podemos automatizar la migración a SDL Tridion?

We are done migrating a website from old CMS to SDL Tridion. We have thousands of clients out of which fewer than five are migrated. Now let's say we need to automate migrating the rest of the thousands clients, obviously we can not use manual effort. Is there a way to develop automated solution against SDL using any APIs it may provide? If yes where can we find documentation for APIs? Any Books or online tutorials for the same?

preguntado el 10 de marzo de 12 a las 11:03

Consider supporting the Area 51 proposal for Tridion; this is a great question, however it's unfortunately slightly off topic on StackExchange. -

5 Respuestas

all very technical answers. Whatever route you choose you need to weigh up the option of not doing a technical migration (and trying to get that right) versus employing a load of students to copy and paste.

respondido 12 mar '12, 13:03

I think you wanted to say "the option of doing a technical migration" instead of "the option of NOT doing a technical migration". - frank van puffelen

Regardless of the CMS, the complexity of a migration can be measured based on how organized is your content in the system you want to migrate from.

I categorize the migration into 3 types related to the Origin and Destination:

  • 1--> CMS to CMS
  • 2--> Database to CMS
  • 3--> WebSite to CMS

If the original source is a database or another CMS typically the complexity is reduced, as the content is already structured. You have to extract that and map the existing content with the structure that will have in the new system

If the goal is migrate an existing website into a CMS the complexity increases as the content is more disorganized that having that in the CMS. Again, if the content in the site is properly structured is still possible to automate that, but most of the cases are old sites maintained manually. There are commercial tools that crawl the content from the sites and apply patterns to identify common elements, common content, common metadata, structure and are able to massage the original content and apply logic based on rules that allows to structure the content, however even the best tool has a hard work to do when the source is disorganized. Also I have seen migrations that cut the final html in pieces and put that in the CMS. That is an easy approach but of course a wrong one, as you are not taking any advantage of the CMS

And 3 Types related the source type we migrate from and the source type we want to obtain

  • 1--> Content to Content
  • 2--> (HTML + Content All together) into (HTML) + (Content) separated
  • 3--> (HTML + Content + Code All together) into (HTML) + (Content) + (Code) separated

Content to Content Migration is less complex

Second option is of course more complex, as you have to Separate Content and HTML that will become templates

Third option is even more complex, as if you are extracting the html of the page (using an http client for instance as most of the commercial tools do), you are not capturing the logic of the page. For this case you need to work at the file level

Try to do a very depth analysis before you enter in a migration, as things can turn complex. Only if you have a very good knowledge of the original system and solid patterns to apply you can think in an automation

respondido 30 mar '12, 03:03

Tridion has extensive APIs and these are thoroughly documented. Your starting point for SDL Tridion 2011 is https://www.sdltridionworld.com/downloads/documentation/SDLTridion2011SP1/index.aspx

Automated migrations are perfectly possible, however API support is not the limiting factor here. Understanding your data in your source and target scenarios is much more important.

respondido 10 mar '12, 12:03

Automated migrations are good for when you can map your dataset 1:1 with Tridion, for example, when migrating a DB to Tridion. However, for normal web pages, and especially pages with handwritten HTML, it is best to include a manual migration for these items. Also - if you can give your content a haircut and not migrate 100% of it - that would be the best. - robrtc

I wouldn't agree that you necessarily need to map everything 1:1. Obviously, for automation to be reasonably manageable, you need algo structure in the source data, so sure, handwritten HTML isn't very helpful, but you can still do a meaningful automatic migration of most of a site, and leave the rest for manual work. - dominic cronin

I would consider contacting Kapow or Vamosa who both specialize in crawling sites and then importing them to a CMS. They both have connectors for SDL Tridion. This may save your clients both time and money.

respondido 11 mar '12, 19:03

Every migration is different, unless you are migrating "thousands of" sites (assuming a client is a site) from same source type to same destination (SDL Tridion in this case) with extremely close data models. Several SDL Tridion partners are already solving this problem and built/building assisted migration automation tools. Get in touch with us if you need more information.

respondido 10 mar '12, 11:03

The offer may be helpful but this doesn't answer the question on API and resources. - alvin reyes

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.