> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/account/data-migration.md).

# Loading your Snapfix account

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/account/data-migration.md).
{% endhint %}

The Android screen that copies the data already stored on the phone from the old local database into the newer one, once, at launch.

* **Where:** Android: app launch, from the [splash screen](https://docs.snapfix.com/how-the-apps-work/screens/account/splash.md) or the deep-link handler, when the user is signed in and the `room_migration_required` flag is set. The old database sets that flag when it upgrades through version 75, the step that adds the move-to-red, move-to-amber and move-to-green columns (android @ 86068bfeea, `db/DBHelper.java:251-262`). A signed-out launch with the flag set does not open this screen: the splash treats it as a data clear and opens the [walkthrough](https://docs.snapfix.com/how-the-apps-work/screens/account/walkthrough.md) or [Sign in](https://docs.snapfix.com/how-the-apps-work/screens/account/sign-in.md).
* **Who:** that signed-in user; no role check.
* **Feature:** [App launch](https://docs.snapfix.com/product/features/account/app-launch.md)

## Layout

Top to bottom: the Snapfix logo, a looping animation of the logo, a horizontal progress bar, "Loading your Snapfix account", and a version label at the bottom that nothing fills in, so it stays blank.

The bar starts at 0 and moves forward by 3 after each of the 31 tables is copied, so it stops at 93 and never fills (`DataMigrationActivity.kt:130-134, 403-411`). It counts tables, not rows: tasks, task messages and checklist items are copied in chunks, and the bar still moves once for the whole table.

## Inputs

None.

## Actions

Nothing on the screen is tappable. Back is not blocked: the screen registers no back handler, so back can close it while the copy runs in the background.

| Action                 | Who       | What happens                                                                                                                                                                                                                                                                                                                                                                                                                      | API |
| ---------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- |
| Copy the stored data   | Automatic | Refreshes the list of API endpoints (`APIEndPointUtils.checkAndLoadEndPoints`), then copies 31 tables on a background thread: sites, groups, group settings, users, consent records, group members, tags, statuses, tasks, task messages and reactions, checklist items and their media, task tags, task users and assignees, attribute rules, task links, time and cost, notifications, viewed-by logs, and the device contacts. |     |
| Record later refreshes | Automatic | When the new database is already at version 2, records that `notifMute` must be refreshed (from 27 September 2024); at version 3 also the time-cost type, default currency and auto-archive columns (from November and December 2024).                                                                                                                                                                                            |     |
| Finish                 | Automatic | Clears `room_migration_required`, starts sync, and opens the group list, or the flow for a user who still has to create a site when `shouldCreateBusiness` is "1".                                                                                                                                                                                                                                                                |     |

## States

* **Loading:** the animation, the progress bar and "Loading your Snapfix account".
* **Empty:** a phone with no stored rows still finishes; the bar still moves once per table.
* **Error:** no message. Only the contacts copy is guarded: a failure there is logged and skipped. A failure on any other table is not caught in the background thread, which on Android ends the app rather than leaving the screen up.
* **No permission:** the copy asks for no permission.
* **Offline (mobile):** the copy is local and still runs. Sync starts afterwards.

## Platform differences

Android only. iOS has no such screen: it adds new local database columns on the [splash screen](https://docs.snapfix.com/how-the-apps-work/screens/account/splash.md), with no progress shown.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/account/data-migration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
