The discussion revolves around migrating from Cusdis to Discourse and the challenges of synchronizing new data during the migration process. mikeguo is concerned about the indeterminate wait time for backup restoration and wants to ensure no new content is lost. JammyDodger suggests scheduling a migration with the Discourse team, putting the origin site in read-only mode, and restoring the backup to minimize data loss.
Now I’m going to migrate to Discourse from Cusdis that is I’m using.
I notice that I should make a backup and upload it to my instance, and connect to Discourse Team, then wait Discourse Team to restore the backup to my instance.
The amount of time to wait for a backup to be restored is indeterminate.
I want to know how to synchronize the new data generated during the waiting time to my own Discourse instance.
I think you can schedule a time with the team to migrate a restore over to a hosted site? That way you can put your ‘origin’ site into read-only, take a back-up, and then have that restored to the new site and not miss any new content.