Move Content during uSync Migration
# help-with-umbracot
TECKSPEED
06/21/2024, 1:44 PMHi all,
Using uSync Migrations to migrate a site from v8 to v13. The site is undergoing quite a transformation with content being reorganized into a more logic tree structure. During the uSync migration is there a way to move a content node? Below is an example:
From
Copy code
Home -> Products -> [Node Currently Resides] Copy code
Home -> Products -> Product Category -> [Node should reside]TECKSPEED
06/21/2024, 1:45 PMPerhaps @Kevin Jump could quickly answer?
m
Mike Chambers
06/21/2024, 1:47 PMjust update the uSync config file to reference the correct parent? (either before or after the conversion during migration) should be able to do via powershell script if it's more than a few... or use another property that gives you the category?
t
TECKSPEED
06/21/2024, 1:48 PM@Mike Chambers its around id say 1k nodes
TECKSPEED
06/21/2024, 1:49 PMyou lost me on
(either before or after the conversion during migration)TECKSPEED
06/21/2024, 1:49 PMwhen you run the migration, is there no way to just tap into the uSync file? I know it gives the datatype and its configs etc for a custom migrator?
m
Mike Chambers
06/21/2024, 1:50 PMjust offering a path of least resistance. 😉
t
TECKSPEED
06/21/2024, 1:50 PMOR are you saying forgo the migratiosn and run a custom powershell script to change the parent to the right key?
m
Mike Chambers
06/21/2024, 1:50 PMyep that..
Mike Chambers
06/21/2024, 1:52 PMthen either run your migration after you've updated the parent in the v8 usync config files.. or do the migration and then update the migration/configs prior to import.. or even do the migration import and then clean export to generate the v9 new site configs and update parents then...
t
TECKSPEED
06/21/2024, 1:53 PMLogically would it make more sense to update the parent key, then migrate all the things, then import so that at the end of pressing the button we come out clean?
m
Mike Chambers
06/21/2024, 1:55 PMguess whatever suits you.. if you've moved prior to the migration on the v8 site.. then you can just repeat the migration on failures.. rahter than having to repeat the parent update too. ... but if it's all scripted then horses for courses.
t
TECKSPEED
06/21/2024, 1:55 PMNever heard that saying before lol
TECKSPEED
06/21/2024, 1:55 PMill have to see how indepth the power shell script is
TECKSPEED
06/21/2024, 1:57 PM@Mike Chambers one thing i just thought of, are you saying change the key before or after you generate the pack?
TECKSPEED
06/21/2024, 1:57 PMafter seems problematic
m
Mike Chambers
06/21/2024, 1:58 PMdepends if you only have your new product category nodes in the new site.. then you have no parent guids in the v8 site. 🙂
p
ProNotion
06/21/2024, 3:08 PMI'm not sure if you can do that out of the box with uSync migrations but you should be able to do it easy enough programmatically so that it is repeatable each time you run the migration. Write something to do it either before or after the migration. In my case I am doing as much of that stuff as I can before the migration.
93 Views