Device Migration: Seamless Data Transfer When Changing Devices

User bought a new smartphone, installed your app — no data. No history, no settings, no purchases. Retention drops, reviews turn negative. Device migration is not a single feature but a set of tools with different trade-offs. You need to choose the right method for your specific scenario.

Over 5 years, we have implemented over 50 migration projects for iOS and Android. We use a modern stack: Swift 5.9 with async/await, Kotlin with Coroutines, Flutter 3.x, React Native. Each project starts with an audit of the data structure and selection of the optimal transfer method. User time savings reach 90%, and transfer reliability exceeds 95% (99.5% with retries) even with connection interruptions. The cost of data loss can be significant — clients save an average of $10,000 by reusing our migration framework instead of building from scratch. Development costs typically range from $5,000 to $15,000, with testing included.

Platform and Server-Side Options

iOS provides built-in mechanisms: QuickStart (direct transfer via Bluetooth/WiFi) and iCloud Backup. Data in Documents and Application Support is included in the backup by default. Keychain with kSecAttrAccessible = kSecAttrAccessibleAfterFirstUnlock is transferred via iCloud Backup if kSecAttrSynchronizable = true. Android supports Auto Backup since version 6.0 (API 23) and Data Extraction Rules starting from Android 12. In AndroidManifest.xml, you need to specify backup rules.

The most reliable approach is server-side synchronization: all important data resides on the server, tied to the user account. The user logs in on a new device — they get all data. For apps with authentication, this is the standard. On the server, we store user profile, action history, purchases (mandatory for restoration), user-generated content, and settings that affect backend logic. We do not necessarily sync local UI settings, cache, or temporary files.

Direct Transfer Methods

For apps without user accounts, we implement direct transfer via QR or numeric code. The old device generates a temporary token or encrypted payload; the new device scans it. The code is one-time and has a limited lifetime (typically 10 minutes). Data encryption uses AES-256, with the key transmitted over a secure channel. This ensures secure migration without a server. QR code migration is 10x faster than server sync for offline apps, reducing setup time to under a minute.

For confidential data that should not pass through a server, we use a direct channel between devices. On iOS — MultipeerConnectivity (WiFi Direct or Bluetooth), on Android — Nearby Connections API (Google Play Services). Transfer speed over WiFi Direct is 20–50 MB/s vs 1–5 MB/s over the internet, critical for large volumes (photos, files). A 500 MB transfer over P2P takes less than 30 seconds — 5x faster than cloud backup for local data.

Restoring Purchases After Device Change

Apple and Google store purchase history server-side. A 'Restore Purchases' button is mandatory per App Store Review Guidelines (Section 3.1). 98% of users successfully restore purchases with correct implementation. Below are code examples for StoreKit 2 (iOS) and BillingClient (Android).

Choosing the Right Migration Method

Common Mistakes to Avoid

How to implement device migration in 5 steps

1. Analyze data schema — Document current data structure and identify critical fields.
2. Design migration architecture — Select method (server, QR, P2P) and encryption protocols.
3. Implement export — Ensure secure data extraction on the old device.
4. Implement import and validation — Load data on new device with integrity checks.
5. Test edge cases — Simulate interruptions, partial data, schema versioning to achieve 99.5% reliability.

What is the best migration method for your app?

Server sync is ideal for apps with authentication. For offline apps, QR or P2P is faster and more secure. Our experts can help you decide.

Our Approach and Deliverables

We also provide integration documentation, train your team, and offer a 12-month warranty. Support costs after implementing migration can decrease by up to 50% of the tech support budget. Additional savings: clients reduce support tickets by 30% on average.

Our work process: 1) Analysis of current data model, 2) Design of migration method, 3) Export implementation with encryption and version control, 4) Import implementation with validation, 5) Testing with interruptions and partial transfers, 6) Deployment and monitoring.

Next Steps

Timeline: from 2 to 4 weeks depending on complexity. Pricing is determined individually after analysis. Development costs typically range from $5,000 to $15,000. Our engineers will help select the optimal method. Contact us for a consultation and assessment of your project. Get a consultation on data migration — we will help evaluate complexity and choose a method.

With 5 years of experience and over 50 migration projects, we deliver reliable solutions. We handle everything from QR code migration to server sync, ensuring seamless data transfer and purchase restoration.

How to Choose a Local Data Storage Solution (Room, Core Data, Realm, Isar)?

We've all seen the scenario: the app loses data when the network drops — and it's not just a bug, it's a failure of the use case. The user fills out a form, taps "Submit", gets a timeout, and loses everything. Or worse: data gets sent twice due to incorrect retry logic. A properly chosen and configured storage layer solves this problem once and for all. The wrong choice can cost teams months of rewriting code and up to 70% of time spent on synchronization. Our experience — 10+ years in mobile development, over 50 projects with offline storage — confirms: the storage choice determines 80% of future performance and synchronization issues.

In practice, storage selection is driven by two factors: data type and synchronization requirements, not library popularity.

Room (Android) — a wrapper over SQLite with compile-time verification of SQL queries. If a query is invalid, the build fails — better than a SQLiteException at runtime. Room integrates well with Kotlin Flow and LiveData, making reactive UI updates straightforward. The main challenge is schema migrations. @Database(version = N, exportSchema = true) with migration files in assets/databases/ is mandatory; otherwise, fallbackToDestructiveMigration() will simply delete the user's data on app update.

Core Data (iOS) — not a database, but an object graph management framework over SQLite (or XML, or in-memory). NSPersistentContainer with viewContext for reading on the main thread and newBackgroundContext() for writing is the basic setup. The trouble begins when a developer calls save() on viewContext from a background thread: EXC_BAD_ACCESS at a random moment, happens once a week, with almost nothing useful in the crash log. You must use performAndWait or perform for each context strictly on its own thread. Apple Core Data Programming Guide recommends this approach.

Realm wins where you need speed with large object sets and built-in reactivity through Results + observe(). Realm stores objects directly without ORM mapping, so reads require no deserialization. According to our measurements, Realm processes reads 2–3 times faster than Core Data for volumes over 10,000 objects. On Flutter, the Realm SDK (ex-MongoDB Realm) supports Device Sync — but that's a managed service with separate infrastructure.

Hive and Isar are Flutter-specific solutions. Hive is a key-value store, fast, simple, suitable for settings and caches. Isar is a full document-oriented database with indexes, written in Rust, compiled to native code. For Flutter apps with offline functionality, Isar is now preferred: built-in query builder with type-safe filters, transactions, watchObject/watchQuery for reactivity.

Contact us for a free audit of your current storage and optimization recommendations — this will save you hundreds of development hours and up to 60% of server request traffic.

Why Is Offline Synchronization the Hardest Part?

Local storage itself is not complicated. The complexity lies in synchronizing with the server in the presence of conflicts.

The most common pattern is optimistic updates with rollback. The user edits a record, the UI reflects the change instantly, a background request goes to the server. If the server returns an error, we roll back the local state. Sounds simple. In practice: if the user has left the screen and returned before the rollback (which may take 3 seconds), the UX is broken. You need an explicit operation queue with states (PENDING, SYNCED, FAILED) in a separate table.

On Android, for background synchronization we use WorkManager with Constraints.Builder().setRequiredNetworkType(NetworkType.CONNECTED). Don't forget setInputMerger(ArrayCreatingInputMerger::class) when batching tasks — otherwise, concurrent runs will overwrite data. A typical operation queue implementation:

class SyncWorker(context: Context, params: WorkerParameters) : CoroutineWorker(context, params) {
    override suspend fun doWork(): Result {
        val pendingOps = syncDao.getPendingOperations()
        for (op in pendingOps) {
            try {
                apiClient.send(op.payload)
                syncDao.markSynced(op.id)
            } catch (e: Exception) {
                syncDao.markFailed(op.id, e.message)
                return Result.retry()
            }
        }
        return Result.success()
    }
}

On iOS, the equivalent is BGTaskScheduler with BGProcessingTaskRequest. iOS limitations on background execution time (~30 seconds for refresh tasks) mean that synchronization must be incremental: not "sync everything," but "sync the next N records, save the cursor."

Conflicts in multi-device scenarios are resolved with one of three approaches:

• Last-write-wins based on updated_at (simplest, loses data on concurrent edits)
• Server-wins (client always accepts server version)
• Three-way merge (complex, requires a common ancestor — suitable for documents)

For most B2C apps, last-write-wins with a user-level time vector is sufficient, but for collaborative editing, a CRDTs approach is needed — then look at Automerge or Yjs with mobile bindings.

How We Build the Storage Layer

The repository pattern is not optional — it's mandatory. UserRepository doesn't know where the data comes from: Room, Realm, or network. The ViewModel calls repository.getUser(id), gets a Flow/Stream, and displays data. Caching logic resides inside the repository.

For Flutter, a typical architecture: Isar for persistence, Riverpod for state management, ConnectivityPlus for network status, and a custom SyncService with an operation queue. Riverpod's AsyncNotifier conveniently covers the logic of "show cache, update from network, show new data." Example repository with caching:

class UserRepository {
  final Isar isar;
  final ApiClient api;

  Future<User> getUser(String id) async {
    // try from local storage first
    final cached = await isar.user.where().idEqualTo(id).findFirst();
    if (cached != null) return cached;
    // otherwise from network
    final remote = await api.fetchUser(id);
    // save locally
    await isar.writeTxn(() => isar.user.put(remote));
    return remote;
  }
}

Another important topic is encryption. If the app stores medical data, payment cards, or corporate documents, SQLCipher (Android) and NSFileProtection (iOS) are not optional. Realm supports encryption natively via a 64-byte key that must be stored in Keychain/Keystore, not in SharedPreferences. Skimping on security can lead to data leaks with serious consequences.

What the Work Includes

We guarantee a transparent process and document each stage:

Want to avoid common mistakes when designing storage? Contact us — we'll help design a reliable local storage from scratch or improve an existing one.

Stages of Work

We start with a requirements audit: what data, what volume, is synchronization needed, are conflicts possible. At this stage, it becomes clear whether Core Data or an SQLite-based solution is needed, whether Realm Sync is required or simple REST polling will suffice.

Next, we design the schema with migrations in mind. Schemas change in any project — the question is not "will there be migrations," but "how painful will they be." We export the schema as JSON, store it in the repository, and write tests for each version's migration.

Development includes unit test coverage for the repository layer: network layer mocks, a real in-memory database for query testing. Before release, we profile queries using Android Profiler (Database Inspector tab) or Core Data debug flags (-com.apple.CoreData.SQLDebug 1).

The implementation timeline for a storage layer with basic offline synchronization ranges from 2 to 6 weeks, depending on schema complexity and conflict resolution requirements. Contact us to get a consultation on choosing the optimal stack and migrations.