# How to migrate web push subscribers from another provider to GetResponse?

If you are switching to GetResponse from another web push notification provider, you may be wondering how to transfer your existing web push subscribers. Due to browser security rules and differences in how providers format notification data, direct subscriber importing (such as uploading a list of subscription tokens) is not possible.

Instead, GetResponse migrates your subscribers automatically through a seamless background process called **resubscription**.

How subscriber migration works
------------------------------

When you transition to GetResponse, your site visitors do not need to re-confirm permission prompts or take any manual action. The migration happens silently in the background when an existing subscriber visits your website.

Here is what happens:

1.  Our integration script detects their existing browser permission and automatically generates a new GetResponse subscription key.
2.  The subscriber is seamlessly registered in your GetResponse account without seeing any popup or prompt.

To ensure automatic migration works, you must install the GetResponse **Web Connect script** on your site and place the **service worker file in your website’s root directory** while removing the previous provider’s script. [Click here for a step-by-step instruction](https://www.getresponse.com/help/how-to-create-a-web-push-notification.html).

Automatic permission renewal
----------------------------

In addition to migrating subscribers from other platforms, GetResponse continuously refreshes active subscriber permissions.

Web browsers and push services occasionally expire or invalidate push tokens. To prevent lost connections, GetResponse automatically renews each visitor’s subscription token periodically (up to once a week) whenever they revisit your site. This keeps your subscriber list active and improves notification deliverability without requiring any setup from you.