A message that urges migration should be slowed into a contact-entry and app-context check. The article should help the reader compare where the message came from, what Ledger Wallet shows, and what the device screen asks for.
Contact entry should be recorded before action
Record the sender path, message wording, requested action, and time received. Then return to a known Ledger entry and check whether the same task appears there.
The entry verification checklist helps compare contact path, app state, device state, and local record.
App context should explain the migration task
If Ledger Wallet shows a migration or update-related task, read the app context carefully and separate app-layer wording from device-layer wording. Do not let message urgency decide the workflow.
- Record message wording and contact path.
- Compare the task inside Ledger Wallet.
- Keep recovery phrase and PIN values out of contact replies.
Device screen should be checked after the app layer
When a device action appears, compare the hardware screen with Ledger Wallet context. The app versus firmware update guide helps separate app prompts from device-side update steps.
Close with a migration-message record
End with contact entry, app context, device-screen wording, backup boundary, and final decision. That keeps the article calm and avoids turning urgency into the decision point.
