Jive to SharePoint Migrations

Simplify and Save

Do you pay double for collaboration because you have both Jive and SharePoint?

  • If you’re tired of the complexity of having to reference a 10+ step flowchart every time you start a conversation or store a document because there are too many options in environments where you have both Jive and SharePoint…
  • If you’re frustrated with not having a fully integrated experience with social content,  web content and document content…
  • Maybe you’re simply looking for an easy way to win the love of your CFO by removing a recurring cost and stay friends with your other executives by not losing all the content in Jive?
  • Or, better yet, maybe you’ve merged with another company and having Jive is redundant and unnecessary (but you still don’t want to lose the IP in Jive by just turning it off)?

… then this message is just for you.

Here’s why…

 You can stop paying twice for collaboration – you don’t have to pay for both Jive and SharePoint anymore.

If You Ignore It…

It just gets worse

There was a time when Jive ran circles around SharePoint (with it’s lengthy 3-year product cycles), but that’s not the case anymore.  One could make the argument that Microsoft is innovating faster than Jive.  What most people do when facing the fact that Jive and SharePoint do so much in common is try and integrate the two (Jive and SharePoint) either with a connector or with manual corporate processes/policies.

But for most organizations, that doesn’t work.

  • Jive’s Connector treats SharePoint more like a data store for content and the only way you can see content is through a Jive Web Part
  • The original connector that we created still exists, but we are recommending that customers make a decision between using Jive or SharePoint for their Intranet
  • Some organizations try and create complicated manual policies that might work for a little while (and with a big stick), but over time people just fall into bad habits

And what happens if you just do nothing? If you just keep doing  what you’ve been doing?

The Jive bill will still show up.  Your users will still be confused about where to store content.  Search will continue to be a disaster.

How We Simplified

We’ve got an answer that works.

Here’s the backstory: ThreeWill was hired by Jive 7 years ago to build the original SharePoint Connector for Jive.  We designed the connector to leverage the best of what Jive has to offer (streams, social, tagging) with SharePoint (workflow, document management, enterprise search).  Jive white-labeled our services to roll out the connector to about 100 customers.

We even wrote  “Making SharePoint Social” white paper at the time where we described it as combining SharePoint and Jive together for a first class experience.

About 3 years in Jive decided to build their own version of a connector and go in a different direction.  Soon after that, we were demoted as a partner and our Jive licensing went with the partnership.  We didn’t want to loose the years of important collaboration intellectual property that was stored in Jive.  So we created a tool to migrate our content from Jive to SharePoint (for us, SharePoint Online on Office 365).

And then we started getting contacted by companies that installed the connector to migrate them from Jive to SharePoint.  Microsoft acquired Yammer and more companies moved.  Office 365 moved to a rapid development cycle and benefited from heavy investments and became one of Microsoft’s most important platform.

This year we’re getting requests every week from customers to help with the move.

It Worked For These People

(and it will work for you)

One of our first customers was PoolCorp – their Jive based Intranet, although highly leveraged within the enterprise, was too costly to justify the recurring annual license fees. This decision to unplug and replace was delayed until 8 weeks before the annual renewal date, so meeting the project deadline was a critical success factor.

We replaced Jive with SharePoint within the 8 week deadline. We implemented similar branding and functionality in order to reduce field sales and service disruption. Migration included approximately 25,000 items with metadata (majority were Jive Documents), 285 Jive Places mapped and majority were migrated, and over 1,200 users were migrated.

Here’s what our business sponsor had to say about the project –

  • “Our initiative to move from Jive to SharePoint had a strong ROI business case but was complicated due to the short window for migration completion during the end of year holiday season.  We needed a technology partner who could get the job done predictably in that short 6 week period.  Additionally, we required the new SharePoint Intranet site to look and navigate like the legacy Jive site in order to not disrupt the field sales and service teams across the country who rely on the system daily for operations.  ThreeWill not only met but exceeded our expectations in completing the migration on time and under budget!”

    IT Manager, Project Management Office, Large Distributor of Recreational Products

And this was one of our smaller migrations – we’ve migrated customers with 10,000 places and Terabytes of content.

Now, It’s Your Turn

Take the risk-free first step…

When you get the Jive Migration Pack today, you’ll get the key to…

  • Stop paying the ongoing fees for Jive month after month
  • Get key content up and running on Office 365
  • Remove the confusion about what goes where
  • Drive out risk with the migration by using a mature tool with a proven process

It all comes as part of the Jive Migration Pack.

In the Jive Migration Pack you will get:

  1. Migrator (Trial Edition)
  2. Business Case for Migrating from Jive to SharePoint
  3. Access to the SharePoint Migration Guide (with over 50 resources for migrating to SharePoint)

The Jive Migration Pack is free – so there’s no risk on your side.

It’s Decision Time

You have a choice to make…

Do what you’ve been doing (or worse, do nothing at all).

Finally…get one (or, at least, one fewer) bill for collaboration at your company.

Which do you really want for your company?

Here’s what to do now…

Download the Jive Migrator Pack today by providing your email below (and we’ll email you the download details) and clicking “Request Download.”

We won’t resell your email.  That wouldn’t be cool.  Read our privacy policy and/or details on our trial software.

Past the Research Phase?

If you’re past the research phase and ready to get started soon, please take our pre-migration questionnaire.

FAQ

(For those of you who love to learn the details)

Some of the reasons you should work with our team on this initiative is:

  1. We have successfully migrated other customers off of Jive in a timely manner and can provide references
  2. We have an extensive background on both the Jive and SharePoint / Office 365 APIs from our experience with building commercial connectors and applications for both platforms
  3. We have built a migration utility (thousands of hours of development time) to make this whole process go smoothly
  4. Doing these types of migrations is a one-time project and therefore you should focus your internal teams on other initiatives where they can apply their experience multiple times
  5. Using lower cost outsourcing teams that will be doing this for the first time adds risk to meeting deadlines

We recommend that you reach out to us to schedule the workshop 8-10 months before your expiration date. We may not need all that time, but we have a backlog of migrations and will need to get the workshop scheduled 2-3 months in advance.

These projects are done in three phases:

  1. Jive Migration Workshop
  2. Implementation (including POC, Pilot and Production migrations)
  3. Sustainment (Post migration support/additional needs like Branding)

The purpose of this Jive Migration Workshop is to allow you and ThreeWill to review the business and technical requirements for your Jive migration, explore the migration approaches and options and establish a budget to implement your migration.

The workshop will cover a detailed review of the migration process.  From this review, we identify key decisions that you will need to make related to the migration. We will a) review the current state of both Jive, Office 365 / SharePoint, and any applicable legacy environments, b) review the requirements and drivers for Jive migration, and c) determine the requirements and desired state of Office 365 / SharePoint 2013/16 once the migration is completed. Lastly, this workshop will feed into setting a high-level roadmap, with the supporting approach, estimate and initial project plan for the migration.

Often times a primary business driver for migration of the Jive content is license renewal fee avoidance prior to the renewal date. Any migration solution will consider and include the ability to extract and backup Jive content for retrieval before your license expires.

The cost for the two-day workshop is a fixed price of $7,500 USD.

Day 1 – Topic and Timelines
TopicHoursNotes
Kickoff and Project Overview
Introductions9:00 –9:15 amTeam introductions
Office 365 / SharePoint 2013/2016 Vision and Objectives9:15 – 9:45 amReview overall Vision and Objectives for moving to Office 365 / SharePoint 2013/2016 and how this initiative will provide value to the business.  Discuss key dates that impact the schedule for migration.
Jive Migration Sponsor9:45 – 10:00 amDetermine migration product owner, or project sponsor for decisions about migration, scope, structure, etc.  Responsible for completion of Migration Worksheet after the workshop.
Current State
Current State Review – SharePoint and Jive10:00 – 10:30 amReview and document Jive usage and scope – confirm migrating Jive content to Office 365 / SharePoint 2013/2016.
Office 365 / SharePoint 2013/2016 Architecture10:30- 11:00 amHigh Level Office 365 / SharePoint 2013/2016 Architecture (site structure, site templates, wiki usage, doc libraries, managed metadata, Yammer usage, customization, branding, etc.).
Future State
Migration Process Overview11:00 – 11:30 amReview of the Migration Process.  Steps involved for migration (process flow of steps, some samples of migrated content).

Review the role of Migration Tools in the process.

Migration Worksheet11:30 – 12:00 pmReview Migration Worksheet and mapping requirements
End of Day 1
Day 2 Topic and Timelines
Identity Migration9:00 – 9:45amIdentity management and mapping.  Identities in Jive, mappings to Office 365 / SharePoint 2013/2016, migrating content with original  users, created dates, etc.
Content Mapping9:45 – 10:45amInitial discussion of the Taxonomy, site structure, content tagging. Do the Taxonomies remain the same?  Are there any integration points between the two Taxonomies desired?  Any private or sensitive data (PII, IP, etc.) that should be removed prior to migration? Discuss the governance considerations when migrating content (e.g. security mappings from Jive to Office 365 / SharePoint 2013/2016?).
Migration Project Planning
Review Migration Approach10:45 – 11:15amIncludes review of content migration, mapping, identities, etc.

Review of the overall migration process – migration iterations, validation, and production cutover.

The deliverables for the workshop are:

  • high level roadmap with the supporting approach and dates,
  • product backlog with estimates,
  • and initial project plan for the migration.

We suggest including:

  • Business Sponsor(s)
  • Jive Admin(s)
  • SharePoint Admin(s)
  • Client Project Manager
  • Other Key Stakeholders that will be impacted by the migration

No, you are free to do the migration with another consulting firm or internally and with another utility. But, you will not be able to use our migration utility if we do not perform the Implementation.

A typical migration has a pilot migration and a production migration. Smaller migrations typically take 3-4 weeks.  Larger migrations typically take 3-4 months.  The amount of time depends on the amount and types of content – we have made the tool multi-threaded to maximize the amount of content we can move.

Typical costs range from about $25,000 USD for smaller migrations to over $300,000 for larger and more complex migrations. We have been focusing on helping customers with larger Jive communities that have a lot of intellectual property stored on Jive.

If we are just migrating content types that we currently support that has a significant impact on cost.  Reach out to us for more details.

At this time, we are the only partner with a utility that will migrate content from Jive into Office 365 / SharePoint (although this may change). Dell has a product that you should look at if you are looking to migrate content to Yammer. We opted to take an approach where we migrate the content to SharePoint lists and libraries.

Great question – this list will need to be updated but here is where we currently stand:

  • Documents
  • Discussions
  • Binary Files
  • Collaborative Documents
  • Blogs
  • Videos (with some caveats depending on how you are using videos)
  • Jive Comments
  • Jive Messages
  • Links in Jive Content and Jive User Profile Pages (updated to point to SharePoint content)
  • Created / Modified timestamps and Modified By / Created By values
  • Jive Content like Tags and Categories are archived (but not migrated)
  • Group Member Security (Owners/Members from Jive Groups)

  • Polls
  • Tasks
  • Calendars
  • Status Updates
  • Private Messages
  • Shared Links
  • Bookmarks
  • Announcements
  • Streams
  • Jive Overview Pages
  • Tiles
  • Tags
  • Categories
  • Follows
  • Profile Properties
  • Personal Documents (Collaborative or Binary)
  • Space Member Security (Owners/Members from Jive Spaces)

But, like any good consulting firm will say, anything can be done for a price.  If you need to migrate one of these content types let us know during the workshop.

We do archive many of the content types to a SQL Server database (including polls, tasks and calendar events).  This way this information could be accessed a later date.

Yes.  And, we will work with your organization to validate migration of content to these groups in a way that maintains confidentiality.

We use SCRUM (read this article – Using SCRUM on Migration Projects) and set our clients up with a Client Extranet Site (on Office 365, of course ;).

It’s pretty common for us to help customers soften the edges of SharePoint and make it more familiar to end users. Also, it’s pretty common for us to set up a Sustainment Agreement to support future needs.

Danny RyanJive to SharePoint Migrations