Hi.
One you have copied your data into your new database and created a feature service to mirror your original one, I would start by creating a clone of your production survey. This clone would be just for testing, to make sure you can replicate your survey on top of the new feature service. You can do this as follows:
- In Connect, create a copy of your survey (but do not publish it yet). We will change the submission URL later so this new copy of your survey points to a new feature service.
- In Connect, create a survey from your new feature service as described here: https://community.esri.com/groups/survey123/blog/2017/09/25/working-with-existing-feature-services-i...
- Get the submission_url and form_id values from the survey you created in step 2 and copy/paste them into your clone survey created in step 1
- Publish your clone survey and make sure it works as expected. If something goes wrong, make sure you fix the problem by adjusting your feature service. For example, enabling attachments if you need them. Do not modify the XLSForm questions.
If you got your new clone survey to work well, then you can now go into your production service, and copy/paste the submission_url and form_id values into the production survey and publish. At that point, data submitted from the survey123 app will start going into the new feature service. End users do not need to download your production survey again, because the target feature service of a survey is discovered at runtime.
Note: If for whatever reason you are not able to smoothly make your clone test survey work against the new feature service, you may want to publish a new version of your survey and ask users to download the new version.
Before doing anything of the above, make sure you make backup copies of your data and surveys so you can revert changes in case you need to. Any changes you make anywhere in a production system (database, feature service, survey, device...) implies risk. The above is provided as a suggestion but you may encounter issues through implementation. Be ready to have a back-up and recovery plan in case things do not go as planned.
