Back
Database Migration/Sync Between Two Projects Failing
Overall The migration failed mainly due to conflicts with existing data (documents, attributes, collections, etc.), exceeding attribute limits, and unsupported function runtimes.
I believe the migration was trying to add additional attributes and would not overwrite existing docs because the ids are the same. In essence all I want to do is update/sync the prod db with dev db data without having to delete all data from prod and recreate it using dev db data.
What are your suggestions?
TL;DR
Database migration/sync between two projects failed due to conflicts with existing data, exceeding attribute limits, and unsupported function runtimes. Migration issues arose because new attributes conflicted with existing data. The goal is to update/sync the prod database with dev database data without deleting all prod data.
**Solution:**
1. Consider using a database migration tool to handle conflicts and sync data between the two projects.
2. Update attributes or carefully manage conflicts during the migration process to avoid issues with existing data.
3. Verify that the migration process does not exceed attribute limits and that function runtimes are supported.
4. Ensure that the migration tool is