When we export data we take the Name of categories and the Name of page types. And then on import, we map the names back to the IDs on the destination. You could use the names instead of IDs in your property if don't plan to change them. You have a DataExporter.Exporting event that allows you to prepare your data for export (static event so register in Application_Start, same goes for the Global.EPDataFactory events). The source of the event is the DataExport class which contains the pages to export in the DestinationPages collection, just modify your properties in them. You also have a DataImporter.Imported event that allows you to do post-import modifications. The source in this case will be the DataImporter class which will have properties such as DestinationPages with the imported pages and PageLookup with page ID mappings. You also have a DataImporter.ImportingPages which trigges a bit earlier in the process. You could also load the mapping object manually by calling EPiServer.Enterprise.Mirroring.MirrorLookupInfo.LoadByContext(Guid of mirroring destination), remember that this is a non-cached administrative method so use it with care (at least not on every hit on your site). That is you options to support mirroring. There is one more little trick, if you store your page IDs as HTML-alike XML you get the page mapping for free. This is recommended for multi-page properties as you get reference warnings when deleting pages in EPiServer also (we'll detect them as ordinary links). For example: Hope this helps..

Thank you! This helps a lot. Just one follow-up question. Is the XML-link syntax independent of whether the site uses search engine friendly URLs or not? Thomas

No, we always support both..