docs: datastore migration guide for web#8578
Merged
cadivus merged 1 commit intodocs/datastore-migrationfrom Apr 28, 2026
Merged
docs: datastore migration guide for web#8578cadivus merged 1 commit intodocs/datastore-migrationfrom
cadivus merged 1 commit intodocs/datastore-migrationfrom
Conversation
cadivus
added a commit
to cadivus/amplify-category-api
that referenced
this pull request
Apr 27, 2026
Replace the internal docs-PR link (aws-amplify/docs#8578) with the published Gen1 documentation page: https://docs.amplify.aws/gen1/react/build-a-backend/more-features/datastore/migrate-from-datastore Three call sites updated: - preserve-sync-fields.ts: module-level comment + MIGRATION_GUIDE_URL const - appSync-walkthrough.ts: the 'No' branch info line added in Phase 5f Tests reference MIGRATION_GUIDE_URL by symbol, not by literal, so the 25 existing tests pass unchanged.
soberm
changed the title
soberm
changed the title
soberm
force-pushed
the
datastore-migration-disable-conflict-resolution
branch
2 times, most recently
from
62f37e2 to
5043a9c
Compare
…flict resolution cleanup
soberm
force-pushed
the
datastore-migration-disable-conflict-resolution
branch
from
5043a9c to
a6496fe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updates the DataStore-to-GraphQL migration guide to include backend changes required for a zero-downtime migration.
Problem
PR #8540 assumes clients can keep their Gen1 backend with DataStore/conflict resolution enabled. This is incorrect because:
_deleted: true) remain in DynamoDB_deletedin the schema, clients cannot filter them outSolution
This PR documents the correct migration approach:
amplify update api_deleted: Booleanto the GraphQL schema (maps to existing DynamoDB data)amplify pushto apply changes{ _deleted: { ne: true } }_deletedfield once all clients are migratedWhy this approach?
Files changed
src/directory/directory.mjs— Added navigation entries for the new migration guide pagessrc/pages/gen1/[platform]/.../migrate-from-datastore/index.mdx— Parent page explaining why backend changes are requiredsrc/pages/gen1/[platform]/.../migrate-from-datastore/disable-conflict-resolution/index.mdx— Step-by-step guide for disabling conflict resolutionTesting
yarn prebuildgenerates directory.json successfully with new entriesRelated: #8540