Hi this kind of activity is almost done everyday by integrators and there are a few commercial tools ready made for this purpose available at pretty exorbitant rates and training.My advise to you is approach this as not a technical project as migrating content will be the least of your worries.You will certainly need to have a plan and by that I mean
A)Does the Object model of Stellent have things common to Livelink.An e.g some DMS's call Documents by their mimetypes.In livelink a document is a single subtype with a varying mime
B)does the source system have concepts of users & groups.Livelink has but its ACL's are done a different way.
C)does source system have some kind of metadata that will be useful in the new one
I would say if you spend 70 % of your project time on a plan to understand both sytems then it will take only 30 % effort for actual migrtaion as both companies have IN/OUT ways
the most cheap way of importing content into livelink is by installing and configuring the ever popular Object Importer module in livelink.It has a syntax guide that tells you the xml a programmer has to create to get the content in livelink.Naturally if you use this tool then you will need a programmer who understands how to make ASCII files .In my tenure I was using a access database with some VBA to make the xml.I have used PERL.I have use C# ,Java anything that you can make up a xml file.
An eg xml instruction that creates a document in livelink.I have dumb ed it down so only the very minimum data is shown
<node action="create" type="Document">
<file><![CDATA[F:\csdata\opentext\oe\destination\aaa_20120918142005\2012091814200527800\0000000001]]></file>
<location><![CDATA[Enterprise:OEFolderx]]></location>
<mime><![CDATA[text/xml]]></mime>
<modified><![CDATA[20120918132547]]></modified>
<title><![CDATA[OE_test.xml]]></title>
</node>
You just go on adding about 1000 of these instructions and feed it.If you need more install a bunc of OI servers to increase your thruput
If you are the programming kind then you have webservices in livelink ,the old lapi interfaces or even OSCRIPT which is the language that livelink uses
Commercial tools are from Syntergy,OT GENIO it is called something else now,Document Pipelines for LES from OT .All commercial tools don't require you to do programming but light weight scripting but comes with a price and training.
I have used OI to make all my migration projects succeed and have never felt the need to buy any other tool for this.When I do migration projects such as this the two sides arrange on a staging are perhaps a database where stellent can deliver and livelink can pickup that is the approach I have used.That helps is re-trying faile do nes and increasing throughput
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
