Johan Björnfot
Sep 17, 2012
  5598
(3 votes)

EPiServer 7 Staging (Export/Import)

A small change that has been done that is useful if you use Export/Import for staging purposes is that we have made it possible to run import/export with kept identities (like when you run mirroring). You control this by a simple checkbox on import page in admin mode as shown below:

Import

When the checkbox is selected then the import will keep the same guid based identities for items (e.g. pages, blocks and files) that they had on the exporting site. During import a check whether an item already exist is performed and in case that is true that item is updated (given that the imported item had a changed date that is later than existing item). In previous versions of CMS during Import all items got new guid based identities which caused that for each item in the package a new item was created on the importing site.

As an example say that you have an import package with one page. If you import that package several times in previous CMS versions (or having the checkbox unselected in CMS7) then you get a new page for each import. Now if you run several imports with the checkbox selected then you will still only have one page.

Sep 17, 2012

Comments

Sep 17, 2012 09:37 AM

Nice!

henriknystrom
henriknystrom Sep 17, 2012 11:54 AM

Excellent stuff! Who came up with this brilliant idea!? :)

Huilaaja
Huilaaja Sep 19, 2012 07:43 AM

What if you import page which ID has already been used by another page?

Sep 19, 2012 08:29 AM

It is not the int based integer that is preserved, it is the guid based identifier.
That means that the int based identifier (that will be PageReference/ContentReference) will probably differ between exporting site and importing site.

Jeff Wallace
Jeff Wallace Sep 20, 2012 11:04 PM

Like

Huilaaja
Huilaaja Sep 25, 2012 12:05 PM

Thanks Johan, it sounds great!

K Khan
K Khan Oct 10, 2013 04:04 PM

How can we export/Import for Global Block that have been used in some helper classes rather in Pages directly?

Sep 30, 2014 11:26 AM

Good to know the breaking change in EPi 7.

Thanks Johan.

Please login to comment.
Latest blogs
Accelerating Optimizely CMS Upgrades with Intelligent Automation

Upgrading an Optimizely (formerly EPiServer) CMS solution has traditionally been a high-risk, resource-intensive endeavor. Transitioning from CMS 1...

Vaibhav | Apr 13, 2026

Optimizely CMS 13: The Evolution We’ve Earned

Tired of migration flashbacks? Optimizely CMS 13 is the evolution we’ve earned. Learn why the move to .NET 10 is easier and how AI-first...

Stuart | Apr 13, 2026 |

The Entra ID Surprise

How assumptions can lead to mysterious issues.

Damian Smutek | Apr 13, 2026 |

OptiPowerTools.Hangfire 2.0.0: CMS 13 Support and Sample Jobs

When I released OptiPowerTools.Hangfire back in March, it targeted Optimizely CMS 12. With CMS 13 now out and running on .NET 10, it was time to...

Stanisław Szołkowski | Apr 13, 2026 |