Yammer Basic to enterprise migration

%3CLINGO-SUB%20id%3D%22lingo-sub-1352942%22%20slang%3D%22en-US%22%3EYammer%20Basic%20to%20enterprise%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1352942%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20been%20using%20Yammer%20Basic%20(free)%20since%209%20years%20in%20our%20organisation%2C%20even%20before%20it%20was%20bought%20by%20Microsoft.%20We%20have%20a%20lot%20of%20content.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERecently%20we%20upgraded%20our%20Office%20licences%20for%20Word%2C%20Excel%2C%20PowerPoint%20etc.%20to%20office%20365%20including%20Yammer%20enterprise.%20Off%20course%20we%20would%20like%20to%20keep%20our%20content%20from%20Yammer%20Basic.%20One%20off%20our%20IT-employees%20contacted%20somebody%20at%20Microsoft%20by%20telephone%2C%20they%20referred%20to%20article%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fyammer%2Ftroubleshoot-problems%2Fcannot-migrate-a-yammer-network-across-office-365-tenants%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fyammer%2Ftroubleshoot-problems%2Fcannot-migrate-a-yammer-network-across-office-365-tenants%3C%2FA%3E%26nbsp%3Band%20told%20us%20a%20migration%20from%20basic%20to%20enterprise%20is%20not%20possible%20if%20you%20want%20to%20keep%20the%20content.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20me%20as%20the%20CEO%20of%20the%20company%20this%20is%20hard%20to%20accept.%20Your%20help%20is%20much%20appreciated%20if%20there%20is%20any%20possibility%20to%20upgrade%20to%20Yammer%20enterprise%20and%20keep%20our%209%20years%20of%20content.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3EHarrie%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1352942%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1353007%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Basic%20to%20enterprise%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1353007%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92112%22%20target%3D%22_blank%22%3E%40Harrie%20Baas%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20article%20references%20your%20Yammer%20network%26nbsp%3B%20being%20in%20a%20different%20tenant%20than%20your%20Office%20365%2C%20is%20that%20true%20-%20i.e.%20you%20have%20different%20login%20details%20for%20Yammer%20than%20you%20do%20for%20Office%20365%3F%26nbsp%3B%20You%20wont%20be%20able%20to%20migrate%20users%20in%20this%20scenario.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20in%20the%20same%20tenant%20you%20will%20be%20able%20to%20migrate%20users%20but%20you%20won't%26nbsp%3B%20be%20able%20to%20migrate%20the%20content.%20I%20suspect%20there%20is%20a%20historical%20reason%20for%20this%2C%20probably%20from%20when%20Yammer%20wasn't%20part%20of%20Office%20365.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1353072%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Basic%20to%20enterprise%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1353072%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F214649%22%20target%3D%22_blank%22%3E%40Andrew%20Hodges%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Andrew%20our%20yammer%20network%20was%20%3CA%20href%3D%22http%3A%2F%2Fwww.yammer.com%2Fnamecompany%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ewww.yammer.com%2Fnamecompany%3C%2FA%3E%3C%2FP%3E%3CP%3EWe%20logged%20in%20with%20our%20email%20adresses%20%3CA%20href%3D%22mailto%3Aname%40namecompany.nl%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ename%40namecompany.nl%3C%2FA%3E%26nbsp%3Bwith%20a%20yammer%20password%20(which%20was%20different%20from%20our%20Office365%20passwords)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20new%20yammer%20enterprise%20is%20also%20at%20%3CA%20href%3D%22http%3A%2F%2Fwww.yammer.com%2Fnamecompany%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ewww.yammer.com%2Fnamecompany%3C%2FA%3E%26nbsp%3Bthe%20old%20yammer%20(Basic)%20is%20only%20accessible%20by%20employees%20who%20haven't%20logged%20out%20or%20at%20with%20our%20mobile%20devices.%20As%20soon%20as%20you%20log%20out%2C%20you%20can%20only%20login%20tot%20the%20new%20Yammer%20enterprise.%20with%20our%20Office365%20login%20and%20passwords.%20The%20users%20have%20the%20same%20e-mail%20address%20off%20course%2C%20but%20the%20password%20for%20Yammer%20basic%20was%20different%20from%20our%20Office365%20account%20which%20is%20the%20password%20for%20our%20AD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20this%20answers%20your%20question%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1353124%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Basic%20to%20enterprise%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1353124%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92112%22%20target%3D%22_blank%22%3E%40Harrie%20Baas%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESounds%20like%20you%20have%20managed%20to%20migrate%20the%20users%20and%20what%20Microsoft%20would%20consider%20a%20network%20consolidation.%20Afraid%20it%20is%20true%20that%20the%20old%20content%20will%20be%20lost%20and%20there%20are%20no%20tools%20out%20there%20that%20I%20have%20seen%20to%20migrate%20the%20content%20from%20one%20network%20to%20the%20other.%20It%20does%20seem%20odd%20that%20it%20is%20not%20provided%2C%20I%20suspect%20its%20due%20to%20different%20versions%20or%20platforms%20left%20over%20from%20the%20purchase%20of%20Yammer%20when%20it%20wasn't%20part%20of%20Office%20365.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1353423%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Basic%20to%20enterprise%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1353423%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F214649%22%20target%3D%22_blank%22%3E%40Andrew%20Hodges%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20so%20disappointed%26nbsp%3B%20in%20this%20answer.%20We're%20talking%20about%209%20years%20of%20content.%20Upgrading%20from%20Basic%20to%20Enterprise.%20Could%20someone%20from%20Microsoft%20give%20an%20official%20statement%20on%20this%20question%3F%20How%20to%20upgrade%20from%20basic%20to%20enterprise%20with%20Yammer%20without%20losing%20the%20content.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1354558%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Basic%20to%20enterprise%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1354558%22%20slang%3D%22en-US%22%3EThey%20don't%20monitor%2Frespond%20in%20this%20forum.%20Best%20route%20to%20get%20an%20answer%20would%20be%20via%20a%20ticket%20in%20the%20Office365%20admin%20centre%20or%20via%20your%20account%20manager%20I%20am%20afraid.%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

We have been using Yammer Basic (free) since 9 years in our organisation, even before it was bought by Microsoft. We have a lot of content.

 

Recently we upgraded our Office licences for Word, Excel, PowerPoint etc. to office 365 including Yammer enterprise. Off course we would like to keep our content from Yammer Basic. One off our IT-employees contacted somebody at Microsoft by telephone, they referred to article: https://docs.microsoft.com/en-us/yammer/troubleshoot-problems/cannot-migrate-a-yammer-network-across... and told us a migration from basic to enterprise is not possible if you want to keep the content.

 

For me as the CEO of the company this is hard to accept. Your help is much appreciated if there is any possibility to upgrade to Yammer enterprise and keep our 9 years of content.

 

Kind regards,

Harrie

5 Replies

Hi @Harrie Baas ,

 

That article references your Yammer network  being in a different tenant than your Office 365, is that true - i.e. you have different login details for Yammer than you do for Office 365?  You wont be able to migrate users in this scenario. 

 

If in the same tenant you will be able to migrate users but you won't  be able to migrate the content. I suspect there is a historical reason for this, probably from when Yammer wasn't part of Office 365.  

@Andrew Hodges 

 

Hi Andrew our yammer network was www.yammer.com/namecompany

We logged in with our email adresses name@namecompany.nl with a yammer password (which was different from our Office365 passwords)

 

Our new yammer enterprise is also at www.yammer.com/namecompany the old yammer (Basic) is only accessible by employees who haven't logged out or at with our mobile devices. As soon as you log out, you can only login tot the new Yammer enterprise. with our Office365 login and passwords. The users have the same e-mail address off course, but the password for Yammer basic was different from our Office365 account which is the password for our AD.

 

I hope this answers your question

@Harrie Baas 

 

Sounds like you have managed to migrate the users and what Microsoft would consider a network consolidation. Afraid it is true that the old content will be lost and there are no tools out there that I have seen to migrate the content from one network to the other. It does seem odd that it is not provided, I suspect its due to different versions or platforms left over from the purchase of Yammer when it wasn't part of Office 365. 

@Andrew Hodges 

 

I'm so disappointed  in this answer. We're talking about 9 years of content. Upgrading from Basic to Enterprise. Could someone from Microsoft give an official statement on this question? How to upgrade from basic to enterprise with Yammer without losing the content.

They don't monitor/respond in this forum. Best route to get an answer would be via a ticket in the Office365 admin centre or via your account manager I am afraid.