Moving from Jive Community to Salesforce Community Cloud: Addressing Data Migration Concerns
Since Jive’s external communities platform was sold to Lithium recently, many customers are looking to move to a new platform. Due to its size and huge number of integrations and partnerships, Salesforce Community Cloud is becoming an increasingly tantalizing choice for businesses, especially those who are working through growth and want to scale quickly, or enterprise organizations looking for further reach in their technology integrations.
At Paladin, we’ve seen dozens of our clients decide to make the jump from Jive to Salesforce Community Cloud. The biggest obstacle for any business facing this kind of move is how to handle the data migration. After hundreds of migrations of this type, Paladin has developed several solutions to handle the major pain points, specifically in a migration from Jive to Salesforce Community.
Known Gaps: A few known gaps exist between Salesforce and Jive data, most notably blogs and Jive Native Documents (or Wikis). Paladin has developed solutions to address these gaps, and we make sure to identify them in our initial stage Strategy and Mapping Workshop.
Defining Use Cases: The aforementioned Strategy and Mapping Workshop that we hold for all new customers helps us determine which features in Salesforce Community will be most useful to your organization. Once we know what your intentions are with your external community, we can devise the right architecture for your data’s new home.
Configuration: Paladin has a proprietary migration tool that maps the data from Jive to the new Salesforce Community architecture, again addressed in the initial Strategy and Mapping Workshop that we hold for all of our customers.
Data Accuracy: To ensure accuracy in data, we complete at least two “dry runs” prior to Go Live, and perform quality assurance measures each time. The first dry run is completed with a sample set of data so that we can correct any issues before the full migration. Our data migration server tracks all data elements and states as well.
User Mapping: There are several user differences between Jive and Salesforce, such as permission sets and profiles. We address these issues during migration and associate users with correct content, even if they are inactive users. We also backdate content and create/disable user accounts to correct for these issues.
Downtime: We mitigate downtime by having a Go Live about two weeks before the cutover date and then do a differential for cutover. In addition to the dry runs, this early Go Live ensures a smoother transition and more uptime for your site during the final migration.
Of course, no two migrations are ever exactly the same, and while our experience has given us the expertise to handle known pain points, it has also given us the ability to address new ones that arise based on specific customer data issues. Contact us today to see how we can customize a data migration from Jive to Salesforce Community for your organization, or handle other data migration projects you may have on your plate.