In a global scenario with multiple data centers located in Japan, North America, and Russia:

Currently, there are multiple data centers globally, including locations in Japan, North America, and Russia.

Users originally registered in North America have their data stored there. Typically, they access data through the North American cluster.

In specific scenarios, users access data through the Japan cluster, resulting in high latency due to cross-region data access.

The goal is to determine whether a user is temporarily accessing the cluster in Japan or permanently (e.g., long-term residence) accessing data through the Japan cluster. If it’s long-term, data migration should occur during one of the user’s visits.

To provide a better user experience and avoid high network costs associated with cross-region access, I need a solution and function—possibly using login logs—to identify whether an originally North American user will be accessing data through the Japan cluster long-term, triggering the need for data migration (assuming the data migration API is available).

Key considerations:

Data migration should not occur if the user is only temporarily accessing data in Japan.
If users frequently switch between clusters to access data, which could be due to work-related reasons, data migration should not occur in such cases.