Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I tried to migrate a site template from an on premise installation to SharePoint 2010 Online (Office 365). When I try to create a new site I get the following error:

The site template requires that the Feature {2acf27a5-XXXXX-xxxx...} be activated in the site collection.

I already know that a missing feature is the web analytics feature which is not available on SP Online.

Does anybody have a good guidance on how to get around these issue? Do I just need deactivate the feature on premise and save the template again? Or do I need import the site template .wsp into Visual Studio and edit the XML (eg. remove the required feature IDs)?

share|improve this question

2 Answers 2

up vote 2 down vote accepted

I've found that this is exceeedingly difficult. Many of the features which may be enabled in an "on premises" farm cannot be deactivated through the UI or even with Powershell. I went through this exercise just trying to move one of my demos which depended on virtually none of the SharePoint 2010 available features and ended up giving up because it was impossible to turn some of those features off.

Also consider the fact that you need to turn those features off in your existing farm, which may well be in use. This can cause really ugly ramifications becasue you can end up with all sorts of orphaned features and other "stuff".

It's possible that editing the .wsp manually will work, but you're basically on your own there. You would need to experiment because of the interdependencies between features, etc.

share|improve this answer
    
For a simple site, exporting and importing the individual lists and libraries may give you a head start to recreating your site template in Office 365, –  Tom Resing Jun 26 '11 at 0:30
    
That's true, Tom, but it still means a complicated, manual process. I think one of the biggest weaknesses of the whole Office365 idea is moving content to it and from it. There's just nothing there for it. I do believe that vendors like MetaVis can help, but that costs extra $$$. –  Marc D Anderson Jun 26 '11 at 3:22
    
I agree, if your site contains a lot of lists and libraries, the manual process will take some effort. There is a lot of potential with the platform and so for some it will be worth it. As for the tools, they are worth it if your time is valuable or the move needs to happen quickly. –  Tom Resing Jun 27 '11 at 17:49
1  
Moving one relatively simple site is one thing; moving multiple sites or trying to preserve Create, Created By, Modified, and Modified By is entirely another. I worry about people using Office365 and having their content "stuck" there as well as being able to move existing content to Office365. –  Marc D Anderson Jun 28 '11 at 13:14

Deactivate the feature on your local instance and regenerate the template and you should be all set to create sites with it on Office 365.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.