Migration and QuickParts in Documents

%3CLINGO-SUB%20id%3D%22lingo-sub-140774%22%20slang%3D%22en-US%22%3EMigration%20and%20QuickParts%20in%20Documents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140774%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3EWondering%20if%20anyone%20has%20any%20advice%20or%20experience%20in%20with%20the%20following.%3C%2FP%3E%0A%3CP%3EI%20am%20currently%20migrating%20from%20a%20hosted%20SharePoint%20Environment%20to%20SharePoint%20Online%2C%202%20Site%20collections%2C%20thousands%20of%20documents%20etc%20etc.%20Pretty%20straight%20forward.%20Using%20Sharegate%20as%20the%20tool%20of%20choice.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EProblem%20is%20that%20the%20documents%20have%20a%20couple%20of%20quick%20parts%20added%20to%20the%20template%20that%20is%20being%20used%20by%20a%20number%20of%20Content%20Types.%20These%20quick%20parts%20refer%20to%20a%20SharePoint%20Column%20in%20the%20document%20libraries%20for%20example%20%22current%20version%22%20(which%20basically%20is%20a%20replication%20of%20the%20SharePoint%20version%20number).%20The%20issue%20is%20that%20after%20the%20migration%20the%20mapping%20between%20the%20quick%20parts%20and%20the%20SharePoint%20Column%20is%20lost.%20This%20is%20known%20and%20not%20supported%20by%20Sharegate%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.share-gate.com%2Fhc%2Fen-us%2Farticles%2F115000647288-Quick-Parts-are-not-supported%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.share-gate.com%2Fhc%2Fen-us%2Farticles%2F115000647288-Quick-Parts-are-not-supported%3C%2FA%3E).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EQuestion%20is%20how%20can%20I%20%22re%20map%22%20the%20association%20in%20these%20documents%20without%20having%20to%20go%20through%20each%20and%20every%20document%3F%20Is%20there%20a%20programmatic%20approach%20that%20could%20be%20taken%20here%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-140774%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071293%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20and%20QuickParts%20in%20Documents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071293%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72749%22%20target%3D%22_blank%22%3E%40Daniel%20Anderson%3C%2FA%3EHey%20guys%2C%20I%20was%20faced%20with%20the%20same%20problem%20and%20ended%20up%20fixing%20it.%20I%20wrote%20a%20how%20to%20guide%20on%20this%20too%3A%20%3CA%20href%3D%22https%3A%2F%2Fblog.gtconsult.com%2Fquick-parts-in-word%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblog.gtconsult.com%2Fquick-parts-in-word%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20it%20helps!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-363480%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20and%20QuickParts%20in%20Documents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-363480%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%20not%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-363272%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20and%20QuickParts%20in%20Documents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-363272%22%20slang%3D%22en-US%22%3E%3CP%3EWere%20you%20able%20to%20find%20a%20solution%20for%20this%3F%20Im%20in%20a%20similar%20situation%20now%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-260997%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20and%20QuickParts%20in%20Documents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-260997%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20Have%20you%20found%20a%20solution%20to%20this%20in%20the%20meantime%3F%20I'm%20facing%20the%20same%20problem...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1846872%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20and%20QuickParts%20in%20Documents%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1846872%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8719%22%20target%3D%22_blank%22%3E%40Scott%20McCann%3C%2FA%3E%26nbsp%3BHello%2C%20I%20have%20the%20similar%20problem.%20I%20try%20to%20use%20your%20link%20but%20its%20broken.%20Can%20you%20share%20any%20details%20about%20the%20solution%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi all,

Wondering if anyone has any advice or experience in with the following.

I am currently migrating from a hosted SharePoint Environment to SharePoint Online, 2 Site collections, thousands of documents etc etc. Pretty straight forward. Using Sharegate as the tool of choice.

 

Problem is that the documents have a couple of quick parts added to the template that is being used by a number of Content Types. These quick parts refer to a SharePoint Column in the document libraries for example "current version" (which basically is a replication of the SharePoint version number). The issue is that after the migration the mapping between the quick parts and the SharePoint Column is lost. This is known and not supported by Sharegate (https://support.share-gate.com/hc/en-us/articles/115000647288-Quick-Parts-are-not-supported).

 

Question is how can I "re map" the association in these documents without having to go through each and every document? Is there a programmatic approach that could be taken here?

5 Replies

Hi. Have you found a solution to this in the meantime? I'm facing the same problem...

Were you able to find a solution for this? Im in a similar situation now

Unfortunately not :(

@Daniel AndersonHey guys, I was faced with the same problem and ended up fixing it. I wrote a how to guide on this too: https://blog.gtconsult.com/quick-parts-in-word/

 

Hope it helps!

@Scott McCann Hello, I have the similar problem. I try to use your link but its broken. Can you share any details about the solution?