Get-SPOFeature

%3CLINGO-SUB%20id%3D%22lingo-sub-66384%22%20slang%3D%22en-US%22%3EGet-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66384%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20migrating%20from%20one%20SharePoint%20Online%20tenancy%20to%20another%20SharePoint%20Online%20Tenmancy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20I%20copy%20bespoke%20features%20from%20the%20source%20tenancy%20to%20the%20destination%20tenancy%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20enable%20and%20disable%20features%20using%20Enable-SPOFeature%20and%20Disable-SPOFeature%2C%20but%20how%20do%20I%20get%20the%20feature%20copied%20across%20%3F%20Do%20I%20need%20the%20source%20of%20the%20Feature%20and%20the%20upload%20it%20into%20the%20destination%20tenancy%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-66384%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPnP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66454%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66454%22%20slang%3D%22en-US%22%3EAgree%20with%20Pieter%2C%20it%20seems%20your%20scenario%20is%20just%20a%20normal%20provisioning%20scenario%20where%20your%20source%20is%20one%20SPO%20tenant%20and%20the%20destination%20is%20another%20one%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66410%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66410%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20give%20Get-PnPProvisioningTemplate%20and%20Apply-PnPProvisioningTmeplate%20a%20try%20then.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66409%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66409%22%20slang%3D%22en-US%22%3E%3CP%3Ethey%20are%20custom%20look%20and%20feel%20features%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66408%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66408%22%20slang%3D%22en-US%22%3E%3CP%3Eno%20they%20are%20not%20sandbox%20solutions%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66403%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66403%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20these%20features%20coming%20from%20Sandbox%20solutions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESandbox%20solutions%20shouldn't%20still%20be%20use.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fmarios_mo_betta_blog%2F2016%2F08%2F02%2Fsharepoint-online-sandboxed-solutions-disabled%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fmarios_mo_betta_blog%2F2016%2F08%2F02%2Fsharepoint-online-sandboxed-solutions-disabled%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66402%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66402%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2387%22%20target%3D%22_blank%22%3E%40Pieter%20Veenstra%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETHis%20is%20a%20SharePoint%20Online%20to%20a%20SharePoint%20Online%20migration%2C%20but%20the%20source%20and%20destination%20are%20in%20different%20tenancies.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66400%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66400%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1992%22%20target%3D%22_blank%22%3E%40Nigel%20Price%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20there%20isn't%20really%20a%20way%20to%20migrate%20them.%20You%20could%20use%20PnP%20to%20copy%20columns%2C%20content%20types%20etc%20created%20by%20your%20features.%20However%20you%20are%20likely%20to%20hit%20some%20issues%20on%20the%20way.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20things%20that%20used%20to%20make%20perfect%20sens%20in%20on-premises%20environment%20simply%20do%20no%20exist%20in%20Office%20635.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ealso%20migrating%20like%20for%20like%20would%20make%20you%20ignore%20all%20the%20new%20features%20available%20and%20therefore%20you%20might%20not%20end%20up%20with%20the%20best%20solution%20possible.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66397%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66397%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2387%22%20target%3D%22_blank%22%3E%40Pieter%20Veenstra%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20are%20bespoke%20features%20either%20site%20collection%20features%20or%20site%20features.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66386%22%20slang%3D%22en-US%22%3ERe%3A%20Get-SPOFeature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66386%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1992%22%20target%3D%22_blank%22%3E%40Nigel%20Price%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20you%20talking%20about%20features%20from%20Farm%20solutions%3F%20-%26gt%3B%20You%20can't%20copy%20these%20as%20farm%20solutions%20don't%20exist.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20out%20of%20the%20box%20features.%20-%26gt%3B%20Yes%20you%20could%20enable%20these.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20looked%20at%20using%20PnP%3F%20You%20could%20simply%20(it%20might%20not%20%26nbsp%3Bbe%20as%20simple%20as%20this)%20export%20a%20template%20from%20your%20on-premises%20site%20and%20merge%20it%20with%20and%20export%20form%20your%20destination%20office%20365%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20Get-PnP%20Provisioing%20Template%20form%20both%20source%20and%20destination%20and%20then%20manually%20copy%20bits%20across%20in%20the%20template%20file.%20%26nbsp%3BYou%20could%20also%20consider%20using%20my%20PnP%20PowerShell%20Sample%20(%20currently%20in%20preview%20only!)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fveenstra.me.uk%2F2017%2F04%2F19%2Foffice-365-sharepoint-20132016-moving-sites-around%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fveenstra.me.uk%2F2017%2F04%2F19%2Foffice-365-sharepoint-20132016-moving-sites-around%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi 

 

I am migrating from one SharePoint Online tenancy to another SharePoint Online Tenmancy.

 

How do I copy bespoke features from the source tenancy to the destination tenancy ?

 

I can enable and disable features using Enable-SPOFeature and Disable-SPOFeature, but how do I get the feature copied across ? Do I need the source of the Feature and the upload it into the destination tenancy ?

 

Regards

 

Nigel

9 Replies

Hi @Nigel Price,

 

Are you talking about features from Farm solutions? -> You can't copy these as farm solutions don't exist.

 

For out of the box features. -> Yes you could enable these.

 

Have you looked at using PnP? You could simply (it might not  be as simple as this) export a template from your on-premises site and merge it with and export form your destination office 365 site.

 

So Get-PnP Provisioing Template form both source and destination and then manually copy bits across in the template file.  You could also consider using my PnP PowerShell Sample ( currently in preview only!) 

 

https://veenstra.me.uk/2017/04/19/office-365-sharepoint-20132016-moving-sites-around/

 

 

 

Hi @Pieter Veenstra

 

These are bespoke features either site collection features or site features.

 

Regards

 

Nigel

Hi @Nigel Price,

 

Then there isn't really a way to migrate them. You could use PnP to copy columns, content types etc created by your features. However you are likely to hit some issues on the way. 

 

Some things that used to make perfect sens in on-premises environment simply do no exist in Office 635.

 

also migrating like for like would make you ignore all the new features available and therefore you might not end up with the best solution possible.

 

 

 

Hi @Pieter Veenstra

 

THis is a SharePoint Online to a SharePoint Online migration, but the source and destination are in different tenancies.

 

Regards

 

Nigel

Are these features coming from Sandbox solutions?

 

Sandbox solutions shouldn't still be use.

 

https://blogs.technet.microsoft.com/marios_mo_betta_blog/2016/08/02/sharepoint-online-sandboxed-solu...

no they are not sandbox solutions

they are custom look and feel features

I would give Get-PnPProvisioningTemplate and Apply-PnPProvisioningTmeplate a try then. 

Agree with Pieter, it seems your scenario is just a normal provisioning scenario where your source is one SPO tenant and the destination is another one