DataStore gave Amplify apps local storage with automatic sync and conflict resolution. Gen 2 has no equivalent, and Gen 1 reaches end of life on May 1, 2027. Which apps actually need offline-first, and the three realistic paths: Amplify Data online with local caching, Apollo clients with AppSync, or a different sync engine.
DataStore stored data on the device, synced it through AppSync when connected, and resolved conflicts. Amplify Gen 2 supports GraphQL through Amplify Data but not DataStore. For an app built around it, that is the largest single piece of a Gen 1 to Gen 2 migration.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Many apps used DataStore because it was the easiest data API, not because users work offline. These move to Amplify Data with little user-visible change.
Apps that needed fast local reads but rarely work fully offline can use a local cache in front of Amplify Data.
Field apps, warehouse scanners and anything used where connectivity is unreliable genuinely need offline-first with sync.
The Apollo paths are those Amplify's DataStore migration guides recommend for offline-first.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Leaving AWS Amplify and AppSync: When It Is Time, and How to Do It Without a Rewrite
Amplify gets a startup to launch fast. The trouble starts later: list queries that scan, resolvers that can't throw or call out, a 30-second ceiling, and a data model that was never designed. The signs it is time to leave, what to move to, what to keep, and a cutover that doesn't log anyone out.
Read
Cutting Over From AppSync to Your Own API Without Downtime (and Without Logging Anyone Out)
Keep the Cognito user pool, verify the same tokens in the new API, move one screen at a time behind a flag, and keep AppSync alive until old mobile app versions are gone. The order that avoids a big-bang release, and the checks that tell you it is safe to switch off the old backend.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.