# Reconnect bank accounts affected by a migration

When a bank migration affects your Financial Connections accounts, some previously linked accounts may need to be reconnected before you can continue accessing their data. Use the Dashboard or API to identify affected accounts and prompt customers to reconnect.
## How to manage these changes
Stripe helps you manage account migrations in two main ways.
- **Visibility into affected and upcoming account changes**
  - [Dashboard](https://dashboard.stripe.com/financial-connections/accounts): View status and timing details
  - API: Use the `expected_deactivation_date` field on the Financial Connections Account object
  - Webhooks: Receive notifications when connections are affected or approaching their deactivation date
- **A way to prompt customers to reconnect:** With [Financial Connections Relink](https://docs.stripe.com/financial-connections/relink), you can ask customers to reconnect affected accounts through the Dashboard — no code required — or via the API. There's no fee to reconnect.
## Why connections change
Bank account connectivity can change when a financial institution or provider:
* Updates its API or systems
* Consolidates brands
* Changes consent or authentication flows, or data-sharing configuration
* Introduces new reauthorization requirements
* Moves accounts to a new connection experience or a different banking platform
When that happens, some Financial Connections accounts may stop sharing data through their existing connection path, and customers may need to reconnect before you can continue accessing their data.
In most cases, these changes affect Financial Connections data access only, not payments or payouts unless Stripe notifies you otherwise.