User journeys • MIGRATION
Why a migration?
LockSelf version 4 (V4) is built on a completely redesigned database architecture, distinct from that of version 3 (V3). Existing data is therefore not directly compatible between the two versions.
To move to V4, a migration transfers all of your data from V3 to V4, while ensuring its integrity, security and availability throughout the operation.
The migration takes place in two phases:
- Phase 1 — migration of unencrypted data, during a short period of unavailability.
- Phase 2 — migration of encrypted data, on your first login to V4.
Who is affected?
All users in the organization. Phase 1 is handled automatically by LockSelf; Phase 2 requires an action from each user on their first login to V4. Super Admins, Admins and Moderators also have access to a tracking dashboard.
Phase 1 — Data migration (temporary unavailability)
During this first phase, both V3 and V4 are temporarily unavailable while unencrypted data is transferred to the new architecture.
An unavailability page is displayed throughout the operation. It indicates:
- the reason for the unavailability (migration to V4);
- the estimated time at which the service will be restored.
At the end of this phase, the organization's administrator receives an email confirming that the data migration is complete and that V4 is accessible again.
Phase 2 — Encrypted migration on first login
To guarantee the confidentiality of your data, LockSelf relies on a zero-knowledge architecture: encrypted data cannot be migrated by the server alone. This step is therefore carried out user by user, on the first login to V4 after Phase 1.
First login steps
Log in as usual with your password and PIN code, or via SSO + PIN code.
- Once logged in, a screen informs you of the change in authentication mechanism introduced by V4.
- You are prompted to set up your security key, as when creating an account or logging in via SSO for the first time.
- Once the setup is complete, you are automatically redirected to the V4 web app.
Logging in via the browser extension
If you try to log in from the browser extension before completing your first login on the web app, a redirection screen prompts you to first finalize your migration on the V4 web app.
Updated