What will be the best process of migrating SharePoint data to cloud xECM?

Nitesh harjai

Hi Developers,

Regarding the migration of data from SharePoint to OpenText xECM Cloud, particularly for large files exceeding 200+ GB, the standard cloud procedure involves:

1. Exporting SharePoint data to an SFTP location.
2. Using XML control files to facilitate structured import into xECM Cloud.

Do we have any other approach which can directly migrate the data from SharePoint to xECM cloud without involving intermediate storage ?

Thanks

appuq

Several commercial connectors exist in the OT workplace. One thing one has to check is whether CS uses a front-end webserver(95% it is IIS) or if some customers use Apache or an application server(TC).In one of our migrations, we had a commercial tool called FME AG that does some ETL from data in DCTM and then puts it into OTCS. This used to fail when huge files were being tried.So one option would be to use OI which meant somehow FME had to create a OI control file and somehow make the server point to the file. In the end, I suggested creating an additional front end using TC as the app server and those errors were mitigated.IIS and Apache has a maximum file limit I believe.TC may have but in our project, it wasn't a problem.FME is probably REST-based now I am talking about SOAP-based time.

If you go to the SOLEX site https://www.opentext.com/partners/solution-extension-catalogue which is an exclusive portal for OTCS services you could probably find other vendors like FME.

OT also integrates Sharepoint but in that case OTCS handles file storage and other aspects.

Nitesh harjai

Thanks @appuq for your valuable inputs.

appuq

I reread my post and would like to clarify.

SOAP protocol is implemented by OTCS in two versions

Typically when you deploy on IIS it creates a CWS section, if you say you want it deployed on Tomcat it will deploy it there under services. In both these case,s the configuration file will say localhost/2099 which you should change to the real OTCS server and LAPI port.

The ContentService.svc is the SOAP endpoint responsible for MTOM (large file) stuff.

I had incorrectly said that we created an additional front end. While OTCS can be deployed in a TC server and is very fast very few customers use it like that.