Vamosa, the content migration arm of T-Systems, were recently approached by a potential customer who was evaluating possible ways to move their existing content. We were asked to deliver a short demo showing content being migrated into Office 365 – no indication of which source.
Jive was chosen by us as the content types are a good fit for mapping to SharePoint but any available source system could have been used. Some sample content was created across various content types such as a Jive group, some blog posts and files as well as links within content.
A simple demonstration process was prepared in a little over a week using the Vamosa Migration Architect software. The focus was to show the main points of a typical migration – moving content and maintaining the quality using our default mapping of content types. This demo was well received when it was delivered with lots of good questions asked and answered.
One of the main points discussed was that our default “out of the box” mappings are not necessarily what customers decide to go with for production migrations. The process can be tailored to provide bespoke mappings and custom transformations can be applied to transform and enhance content during its transition into Office 365. This is the one of the strengths of our process as opposed to a simple “lift and shift” migration. While the typical steps in a migration are often similar, it’s the business requirements and source content that make each customer’s migration unique.
In talking to the customer it was also revealed that their source system was IBM Connections. Content existed in Connections Cloud as well as an on-premise 5.0 environment. One of the main questions was whether the Vamosa Migration Architect could be used to move content out of connections as well as Jive.
Our process and technology are platform agnostic, this was not a challenge. Vamosa use custom connectors to interface with any source or target system via the available Application Programming Interface (API). Another strength, as all content flows via the API which is the recommended interface of any vendor. It is usually possible to develop a new connector in a short space of time for different systems if one is not available but in this case, a connector to capture content from Connections was already available – for on-premise and Cloud. These connectors have been used extensively in dozens of migrations to move content between Connections on-premise and Cloud – and even back again!
A follow up demonstration was requested to show content being moved from Connections Cloud, again into Office 365. This was prepared very quickly as much of the process from the first demo could be re-used. We could simply switch out components specific to the source i.e. the source connector and transformation engine.
In addition to Connections community files, which were migrated into a Document Library of a SharePoint Site (created during the migration), Connections personal files were migrated into the OneDrive application of Office 365. Additional examples of how content quality is maintained was show – for instance migration of extended character set content.
One valuable point covered was the ability to maintain historical metadata relevant to the content which can be important for regulations and auditing. This includes the capability of retaining the original authors and timestamps. Often these considerations only become apparent during more detailed workshops but it’s useful to introduce these topics and begin discussing them as early during a demonstration.
The customer was again delighted and very impressed by the capabilities that we have to help them maintain their content with a successful migration to help them start using Office 365. Again, this displayed our flexibility and understanding of a customer challenge and how we can help migrate social and collaboration content.
We are well placed to support migrations from multiple sources into Office 365 and SharePoint. We’re always happy to speak to customers and deliver demonstrations of our capabilities and can usually tailor them to specified systems to show specific points of interest.
Take the next step!
A division of T-Systems, Vamosa Technologies specializes in content migration to cloud, on-premises and hybrid cloud systems. With two decades of customer migrations, Vamosa Technologies has experience with a comprehensive range of leading enterprise content management systems. To learn more about services from Vamosa Technologies, please read our case studies and whitepapers or contact us.