SOLVED

Migration to SPO - Retention Policies

%3CLINGO-SUB%20id%3D%22lingo-sub-1558588%22%20slang%3D%22en-US%22%3EMigration%20to%20SPO%20-%20Retention%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1558588%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20client%20who%20has%20been%20on%20SPO%20for%20a%20year%20now.%26nbsp%3B%20They%20also%20have%20SP%202013%20and%20they%20are%20getting%20ready%20to%20migrate%20to%20SPO.%20However%2C%20they%20have%20retention%20policies%20turned%20on%2C%20on%20all%20SP%20sites%20in%20SPO.%20They%20can't%20turn%20them%20off%2C%20due%20to%20legal%20reasons.%20I%20ran%20a%20couple%20of%20test%20migrations%2C%20and%20I%20do%20get%20some%20errors%20because%20the%20migration%20tool%20has%20to%20create%20and%20delete%20elements%20during%20the%20migration%20process%20to%20reproduce%20what%20we%20have%20at%20the%20source.%20Question%20is%2C%20has%20anyone%20had%20to%20migrate%20to%20SPO%20with%20retention%20policies%20turned%20on%20in%20the%20destination%20tenant%20and%20did%20you%20run%20into%20any%20major%20issues%3F%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1558588%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1562254%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20to%20SPO%20-%20Retention%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1562254%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F158376%22%20target%3D%22_blank%22%3E%40janet%20sleiman%3C%2FA%3E%26nbsp%3BI've%20had%20this%20issue.%20The%20solution%20was%20to%20exclude%20the%20sites%20I%20was%20migrating%20from%20the%20retention%20policy%20before%20copying%20content%20and%20then%20enable%20it%20after%20the%20migration%20was%20completed.%20I%20made%20this%20a%20step%20in%20the%20UAT%20process.%20You%20can%20use%20this%20process%20to%20remove%20sites%20that%20you%20want%20to%20delete%20also.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%20that%20the%20retention%20policy%20takes%2024%20hours%20to%20apply%2C%20so%20you%20need%20to%20do%20this%20the%20day%20before%20migrating.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, 

 

I have a client who has been on SPO for a year now.  They also have SP 2013 and they are getting ready to migrate to SPO. However, they have retention policies turned on, on all SP sites in SPO. They can't turn them off, due to legal reasons. I ran a couple of test migrations, and I do get some errors because the migration tool has to create and delete elements during the migration process to reproduce what we have at the source. Question is, has anyone had to migrate to SPO with retention policies turned on in the destination tenant and did you run into any major issues? Thank you!

1 Reply
Best Response confirmed by JSlei (Occasional Contributor)
Solution

@JSlei I've had this issue. The solution was to exclude the sites I was migrating from the retention policy before copying content and then enable it after the migration was completed. I made this a step in the UAT process. You can use this process to remove sites that you want to delete also. 

 

Note that the retention policy takes 24 hours to apply, so you need to do this the day before migrating.