4D structure and Qodly model are different, even though they share a lot.
If I were you, I would go for the manual way, you’ll save time.
You probably noticed that relations are not handled the same way.
Plus Qodly allows you to declare aliases directly in the model editor, without coding them.
From 4D you can get a similar json representation of your structure by calling /rest/$catalog $catalog | 4D Docs
But in the end, I think you may loose more time adapting 4D json file than redoing it manually.
Some changes are easy to spot and manage with a 4D method. It can speed up your work. But some others will be harder. You will anyway need to properly test your code back.
You can use SFTP for this.
You can also just copy/paste Qodly Pages json content directly through Qodly Studio: Page Editor | Qodly Developer Center
Be careful:
Shared datasources, shared CSS won’t be copied (these are separated files).
So you Pages won’t work directly unless you migrate them as well.
Also give a tour to your Qodly pages events and refresh them to ensure they are properly bound.
A lot can be done with SFTP:
shared css and datasources have their file in the Shared folder,
saved conditions as well if you use States in your pages
custom components as well
So the best is to copy the whole Shared folder.
Identity/user management should probably be reviewed.
Pay attention to roles and privileges as well.