Migration from 5.3 to 6.5 version

Hi Experts,

we have 2 repositories one of them is ABC which was rolled out in 2002 (now ABC repository is no longer using) it is in the version 0f 5.3

then our customer has created a new repo XYZ which is being used from 2002 to tilldate of version 6.5 Now our requirement is to migrate the following item from 5.3 version to 6.5, Please let me know your suggestions to achieve this

ACLs	1000
Groups	300
custom Object Types	6
Document Lifecycles	2
Workflows	17,300
Annotations	90,000
Documents and Renditions	120,000
Folders	160,000
Registered Tables	2
Total Content size	140G

Please let me know if you required more information

Thanks,

Prasad

Find more posts tagged with

Comments

Hartmut_Clausen

Hi Prasad,

do you plan to move the contents of ABC to XYZ? Or do you plan to upgrade ABC and leave everything there?

In case that you plan to move the content to the new repository there are several tools on the market (one of them from my company, in case you are interested see my profile). You could also do this via a custom script. In that case you need to create the object types, ACLs, folder structures etc. of the originating repository in the target repository. Maybe you also want to map some documents to existing object types in the target repository. You should definitely write down the user requirements. What information is expected to be available in the target repository, Where do the users want to find their documents, What happens if a document with the same name already exists in the target repository, How to handle conflicts, etc.

If you only want to upgrade the 5.3 repository to 6.5 and leave everything else in place, its a straight forward upgrade process as described in the manuals.

Kind regards,

Hartmut

XdctmX

Like Hartmut Clausen said there are many options.

One way to do this is to do an inplace upgrade to 5.3 ABC repository to 6.5 ABC then migrate content from the upgraded 6.5 ABC repository to 6.5 XYZ. You can use dump and load method to do this. You can also use Docapp Builder/ Composer but since you have so many objects thsi wont be a easy solution.

Another method is using a custom program which you can create in a week or two to connect to both the repositories and do the import export using threads. There are few sample programs available in the support forum or you can utilize teh DeepExport Deep Import components available in the Developer exchange. You have to make some modifications to this component to include all versions.

Another method is to use product available in the market. For e.g Migration workbench, Buildozer, Open Migrate etc...

XdctmX

Here are some 3rd Party tools

Go to http://software.emc.com/microsites/application_portfolio/#
Click on Solution Category >> Content Migration

You will get a list of products

Dixi

http://www.bluefishgroup.com/products/dixi.html

Migration Workbench

http://www.bluefishgroup.com/content-migrations/migration-workbench.php
http://www.bluefishgroup.com/library/2009/mwb-additional-uses/

open-migrate

http://www.tsgrp.com/misc/open-migrate.jsp

Buldoser

http://www.crownpartners.com/products/buldoser.jsp

Also there are Migration Tools from Generis

http://generiscorp.us/Migration_Tools.pdf

PathBuilder from Vital-Path

prasad

Hi Hartmut, Many Thanks for you time we want to move the contents from ABC to XYZ and use only XYZ repo Moving the document, acl, custom type are not a problem, we can achieve this by using the tools But customer wants the running workflow instances, associated documents, performs, WF history and WF comments could you please let me know using Buldoser, will is it is possible to achieve this

Prasad

Hartmut_Clausen

Hi Prasad,

regarding Buldoser, I have no experience with that product. But I know that every product or custom script will have difficulties with objects, that are created internally by the Content Server itself. Running workflows belong to this category, but also audit trail entries. How many workflows will be active at the time of the migration? How long will a workflow run from start till end? If its only a day or less, you could tell the users to finish all their task before the migration. If the workflows run for longer periods, that might not always possible. How much money will the customer invest for this particular issue? Sometimes it is easier just to abort all workflows before the migration and start them again in the new repository.

Kind regards,

Hartmut