July 10, 2019
Migrating from one platform to another can seem daunting, but if you go into it with a clear strategy and organized content, it doesn't have to be. I interviewed Robert Hanson, Social Edge's collaboration technology architect and migration wiz, to answer some of the most frequently asked questions people have about platform migration.
It really depends on your business goals. When working with a client on a migration project, we start by asking what their primary objectives are so we can develop a migration plan that matches their specific needs. We customize the experience and tailor it to each individual organization.
Generally everything will be migrated, but there may be some platform limitations that prevent migrating some content types. If a limitation is discovered we will work with you to come up with a solution that may allow us to retain your content in a different but similar format. We also recommend performing a data cleanup and review in advance of the content migration so that you don't end up bringing over content you might not necessarily need.
In order to make sure everything is migrated to the correct places we work with you to make an inventory of your content followed by a mapping exercise to keep everything organized. You can map it closely to your current state so that the future state reflects what you already have set up in the community you are migrating from. Alternatively, sometimes our clients prefer to use this mapping exercise to do an overall place cleanup and map content to new information architecture by creating new space/group hierarchies.
It depends on the platforms you are migrating from and to, and the platform's capabilities. By capabilities we are referring to what the API of each platform allows us to do with regards to exporting and importing data. Our team will work with you to identify any affected content items and attempt to identify alternate strategies to meet your business goals.
We try to find alternatives that meet your objectives. For example, take the "helpful answers" feature. Some platforms don't support "helpful answers" but every platform has a similar feature in some form or another, such as "suggested answers." In scenarios like this, we'd used the recommended platform approach to accomplish this goal. Another example would be document versioning. Both Telligent and Igloo have "wikis" that support the versioning of content, similar to native Jive documents, so we would use that content type to provide you with similar capabilities.
The ability to migrate profile data depends greatly on the platform you are migrating to, but typically we are able to migrate the majority if not all of your profile data. If you are looking at a specific platform to migrate your data to we could provide you with a consultation on how well your current profile data maps to the target platform.
Sometimes permissions can be exported but we haven't found this to be the best way to set them up on a new platform as permissions don't always match up from one platform to another. During a platform migration project our Social Edge strategists work with our clients to inventory existing permissions and map them out in the new platform.
Turn off moderation in the new platform for the import so it's not stuck in the moderation queue and awaiting admin approval. If you have content in the moderation queue of your current platform during a data migration (content that has not yet been approved or rejected) it is typically not exported, so the moderation queue should be reviewed by an administrator before a data export.
It depends on the platform, but generally any content that is in a state other than "published" (e.g. drafts, archived content, future dated blog posts, etc.) will not be visible to our export tooling. For example, a future dated blog post is only visible to the author, so our tooling won't be able to see it to export it. Our recommendation from a change management perspective would be to give your users advance notice that a migration is coming, what to expect, and how to publish their content so it is brought over.
In most cases yes.
In most cases yes, aside from links in attachments (e.g. Word Documents).
We will provide a solution that meets your budget and platform needs.
Typically the overall project is 8-12 weeks, but it depends on the size of the migration and your business objectives.
Typically you should start looking around six months before your license renewal, and you should start your data migration no later than three months before your license renewal. Many platforms are willing to negotiate the start of the production license date.