SharePoint Online is continuously evolving and improving, which is a great thing for you as a consumer of the service. One of the key features is the availability of modern sites, which are modern Office 365 group-connected team sites or communication sites, combined with improved functionality that can be consumed from a beautiful, responsive, modern user interface. To learn more about modern checkout the SharePoint classic and modern experiences<\/a> article and get inspired by the SharePoint Look Book<\/a>.<\/p>\n All of this is great, but you might ask yourself, I have lots of classic (team) sites…how do I bring them into the modern SharePoint world?<\/strong> The answer is (in-place) modernization: you can fully transform (or “modernize”) a classic site team sites into modern, optionally Office 365 group-connected, sites by following the SharePoint modernization guidance<\/a>. Check out the Modernize your SharePoint pages <\/a>blog post to learn more about the page modernization basics.<\/p>\n A key part of modernizing your sites is transforming your\u00a0wiki and web part pages into modern client-side pages. This transformation is possible using the SharePoint PnP Modernization framework<\/a>, which is\u00a0a .Net library that you can use via either .Net code<\/a>, PnP PowerShell<\/a> or the Page Transformation UI tool<\/a>.<\/p>\n The March release of the SharePoint PnP Modernization framework contains several major improvements. The March release is available via:<\/p>\n The default page transformation behavior is to create the modern\u00a0client-side pages in the same site as the source wiki or web part page, but now you can also create the modern client-side page in another, modern, site collection (e.g. a communication site). During a cross-site page transformation, dependent media assets (images, videos) are copied from the source site collection to the sitepages library in the target site collection.<\/p>\n When using PnP PowerShell<\/a> you can specify the url of the target site collection via the TargetWebUrl<\/strong> parameter.<\/p>\n When using .Net<\/a> you need to create a ClientContext object instance for the target web and specify that in the PageTransformator constructor as shown in below code snippet.<\/p>\n Not all web parts are supported for a cross-site transfer. More web parts will be enabled in upcoming releases, check out the\u00a0Cross-site support<\/strong>\u00a0column in\u00a0web part transformation list<\/a>\u00a0to learn more.<\/p>\n The following web parts are now transformed as well. Check out the\u00a0web part transformation list<\/a>\u00a0to get an overview of which web parts are transformed and how.<\/p>\n \u201cSharing is caring\u201d<\/em><\/span><\/p>\n <\/p>\n SharePoint Team, Microsoft\u00a0 – 13th of March 2019<\/i><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":" An overview of what’s new in the March release for SharePoint PnP Page Transformation.<\/p>\n","protected":false},"author":69078,"featured_media":2304,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2648","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365-developer"],"acf":[],"blog_post_summary":" An overview of what’s new in the March release for SharePoint PnP Page Transformation.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/2648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69078"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=2648"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/2648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/2304"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=2648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=2648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=2648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}March 2019 updates<\/h2>\n
\n
Cross-site page transformation<\/h3>\n
Using PnP PowerShell<\/h5>\n
# Connect to the site with pages to modernize \nConnect-PnPOnline -Url https:\/\/contoso.sharepoint.com\/sites\/ateamsite \n# Modernize page1.aspx and create the resulting modern client side page in another site \nConvertTo-PnPClientSidePage -Identity page1.aspx -TargetWebUrl<\/strong> https:\/\/contoso.sharepoint.com\/sites\/acommunicationsite<\/pre>\n
Using .Net<\/h5>\n
var pageTransformator = new PageTransformator(sourceClientContext, targetClientContext<\/strong>); \nvar pages = clientContext.Web.GetPages(); \nforeach (var page in pages) \n{ \u00a0\u00a0\u00a0 \n PageTransformationInformation pt = new PageTransformationInformation(page) \u00a0\u00a0\u00a0 \n { \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \n \/\/ If target page exists, then overwrite it \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \n Overwrite = true, \u00a0\u00a0\u00a0 \n }; \u00a0\u00a0\u00a0 \n pageTransformator.Transform(pt); \n}<\/pre>\nNote:<\/h5>\n
New and improved web part transformations<\/h3>\n
\n
Other improvements<\/h3>\n
\n
Resources<\/h2>\n
\n
\n