Here is a more organized and technical version of your message:
Critical Issue When Migrating Data Source to ASDB
Hello Everyone,
We have encountered a critical issue affecting application data migration from external data sources to ASDB.
Issue Summary
When attempting to duplicate an existing application and change its data source from SmartSheet to ASDB, the data is not transferred to the new ASDB source as expected.
Environment
Original Data Source: SmartSheet
Target Data Source: ASDB
Platform: AppSheet
Impact Scope: Company-wide (hundreds of active and upcoming Citizen Developers)
Steps Performed
Created an application connected to a SmartSheet data source.
Attempted to copy the application.
Modified the data source to ASDB during the duplication process.
Regenerated the schema.
Reloaded the browser.
Reattempted the process multiple times.
Expected Behavior
When copying the application and switching the data source to ASDB, the existing data from the original source should be migrated or captured in the new ASDB data source.
Actual Behavior
No data is transferred or saved into ASDB after the application copy process. The target ASDB remains empty.
Impact
This issue is critical for our organization, as we are onboarding hundreds of users to become Citizen Developers. The inability to migrate or initialize ASDB data during app duplication significantly disrupts our workflow.
We would appreciate any guidance on:
Known workarounds
Best practices for migrating data to ASDB
Confirmation on whether this is a known AppSheet platform issue
I’ve already send it. However the fill up form is predefine, its like asking what apps, the security filter. But that is not the problem, its like it ask incorrect question in the form, but I just explain the problem and send the ticket.
By the way, welcome to the AppSheet Community @JanMico_Macdon !
Contacting support is definitively the best thing to do. I looked for instructions on how to copy a database to ASDB and I noticed you might need to first export your Smartsheet to Google Sheets by Select File > Export > Export to Google Sheets.
Hi Jose. Thanks for commenting. Regarding the process you’ve mention we can’t do that because our company account is Microsoft users and we don’t have access to google sheets. So, we do that as well exporting it from SmartSheet to MsExcel, then choose this datasource by importing the MsExcel downloaded, then do the copying app and change the datasource ASDB.
I hope I explain it well. But thank you for the comments. I’ve already reachingout to Contact Support and they are asking to get an access from all my apps, but I mention that it happens to all users so I think it can check to any app. You can try it. Then yesterday there is another issue that even though the person is the owner of the ASDB is says that it could not access the datasource. I think Google Appsheet team is making changes or improving the ASDB for another feature or working with some of the reported bugs?
I hope this should be address because I saw this post since September 2025.
So you export from SmartSheet to Excel, then import Excel into ASDB? You should be able to tell at this point whether the data is loaded into ASDB, even before trying to connect the app to ASDB. If the data isn’t present here, don’t bother trying to connect the app to it, it won’t work.
For the best experience, the same AppSheet account should own both the app and the ASDB, but it’s not a strict requirement (I don’t think?). For troubleshooting, though, it would be a good idea to use an ASDB owned by the app owner to remove ownership as a potential problem (to “reduce friction”). Get that working, then worry about transferring ASDB ownership or switching to an ASDB owned by someone else.
Support should not be making changes without asking your permission and telling you what they’re doing. If they are, you should start looking for a new vendor (honestly, you should be anyway). It is unlikely the development team is making changes that would affect ASDB.
We did have a regression with this and a fix has now been released. Thanks for bringing it to our attention. Please try again and let me know if you’re still seeing a problem with the copy.