How to Transfer Profile Data From GPM Login v4 to GPM Login Global

There are two ways to transfer profile data from GPM Login v4 to GPM Login Global: manually export and import cookies inside the software, or use a dedicated migration tool that copies all 4 profile data files — including Telegram and Discord logins.

GPM Login Global is the newer version of GPM Login and can be activated with the same license key as GPM Login v4, but each version keeps its own profiles — nothing carries over automatically. This guide covers two ways to transfer profile data (cookies, proxies, and app logins like Telegram or Discord) from GPM Login v4 to GPM Login Global: the built-in export/import feature for profiles stored on the cloud, and a dedicated migration tool for copying every data file at once. You'll also learn why the migrated profile gets a new fingerprint, and whether it's safe to run both versions side by side.

What's different between GPM Login Global and v4, and why migrate profile data?

GPM Login Global runs alongside GPM Login v4 rather than replacing it automatically — both versions share one license key but keep profile data completely separate, so anything you want to keep (cookies, proxies, logged-in accounts) has to be moved over on purpose.

Keeping profiles separate by version lets each one run stably and lets the team ship new Global-only features without touching v4 data. The trade-off: users who already manage dozens or hundreds of v4 profiles for Facebook, TikTok, Shopee and similar platforms need a clear process for bringing over the data that matters — login cookies, proxies, and app data — without logging back into every account from scratch.

What should you prepare before migrating profile data?

Before migrating, prepare four things: confirm your license key activates both versions, list the proxy assigned to each profile, write down the exact profile names to match between versions, and back up any cloud-stored profile data first.

Quick checklist of what to prepare before migrating profile data to GPM Login Global.

Four things to do before you start:

● Confirm the license key you're using can activate both GPM Login v4 and GPM Login Global (usually one key works for both — see the Setting and license activation guide).

● Write down the proxy (IP:Port or IP:Port:Username:Password) attached to each profile in v4.

● Name each profile in GPM Login Global exactly the same as its counterpart in v4, so nothing gets mismatched during migration.

● If data is stored on the cloud or a Private Server, export a backup copy first to avoid any risk of data loss.

Method 1: Manually export and import a profile (cloud-stored data)

For profiles stored on the cloud, export them directly from GPM Login v4 and import them into GPM Login Global — a 4-step process, though it only transfers cookies, not other app data.

1. In GPM Login v4, select the profile you want to migrate.

2. Click Export profile, then choose “To folder.”

3. Pick a folder to save the exported file — use a clear folder name if you're handling several profiles at once, so they're easier to track.

4. Once the export finishes, open GPM Login Global, create (or select) a matching destination profile with the same name, then use Import profile to load the exported data.

You can find the full Export/Import steps in the official GPM Login Global Profiles guide. This method works well when a profile only needs to keep its web login state (cookies) — if it also needs to keep app logins like Telegram or Discord, use Method 2 below instead.

Method 2: Use a migration tool to copy all 4 profile data files

If a profile needs to keep app logins such as Telegram or Discord, not just browser cookies, the fastest route is a dedicated migration tool that copies all 4 data files from the old profile to the new one in just a few steps.

You can see the exact steps in the walkthrough video: https://www.youtube.com/watch?v=U_I9CU3KOkM&list=PLpEwQxqRGbYm7brELz65JhSp8oGK0x7z1&index=10

1. In GPM Login Global, create the matching list of new profiles first — same count and names as in v4 — and assign the correct proxy to each one so it lines up with the old version.

2. Download the migration tool from the link shared in that video's description, then install and open it.

3. In the tool's interface, enter the profile storage path for both versions (v4 and Global) so it can scan the available profiles.

4. Search for and select the exact source profile name in GPM Login v4, then search for and select the matching destination profile name in GPM Login Global.

5. Click Import Data. The tool copies all 4 data files from the old profile to the new one — cookies, cache, and login data for apps like Telegram and Discord.

 Migration flow: moving profile data from GPM Login v4 to GPM Login Global with the 4-file migration tool.

Because the tool copies all 4 data files instead of just cookies, agencies and multi-account managers often prefer it when they don't want to log back into Telegram or Discord on every profile.

Which method should you use? Comparison table

If a cloud-stored profile only needs its cookies, manual export/import is enough and needs no extra install; if it needs to keep every logged-in app including Telegram and Discord, use the 4-file migration tool instead.

Comparing manual cookie export/import against the 4-file profile migration tool.

Does the fingerprint change after migration?

Yes — after migration, the new profile in GPM Login Global gets a different browser fingerprint from the original v4 profile, even though its cookies and login data stay the same.

Both migration methods above only carry over cookies or login data, not the fingerprint configuration (Canvas, WebGL, User-Agent, screen resolution, and so on) of the original profile — GPM Login always generates a fresh fingerprint for each profile at the moment it's created. This is exactly why the GPM Login team itself flags plain cookie transfer as something to use carefully rather than as a full clone.

In other words, the device fingerprint a platform sees after migration belongs to a brand-new environment — only the login session (cookies) is familiar. If an account on that platform is sensitive to sudden environment changes, watch it closely for the first few days after switching rather than migrating everything in one batch.

Can you run GPM Login v4 and GPM Login Global at the same time?

Yes — GPM Login v4 and GPM Login Global can be installed and used on the same machine at the same time, activated with one shared license key, with no need to buy a second license.

That means you don't have to migrate every profile at once. Many users migrate gradually: start with the most important profiles, watch them for a few days to confirm accounts stay stable, then move the rest — while still using GPM Login v4 as usual for profiles not yet migrated. You can check your license's device-slot limits in the GPM license management portal.

FAQ

Will I lose the proxy assigned to a profile after migrating?

Manual cookie export/import doesn't carry over proxy settings — you need to reassign the same proxy to the new profile in GPM Login Global. Even with the 4-file migration tool, it's best to assign the proxy to the destination profile beforehand to avoid mixing up IP addresses.

When is manual cookie export/import enough on its own?

When a profile only needs its web login state (no Telegram, Discord, or other app data) and the data is stored on the cloud — this method is built into the software, with nothing extra to install.

Does the migration tool affect the original profile in GPM Login v4?

No. The tool only copies data to the new profile in GPM Login Global; the original v4 profile stays untouched and can keep being used normally.

Does sharing one license key between both versions limit the number of activated devices?

The license key works on both versions but still follows your plan's device-activation limit — check the details in the GPM license management portal.

Do I have to migrate every profile to GPM Login Global right away?

No. Since both versions can run side by side, you can migrate important profile groups first, confirm everything works, then move the rest over time.

Conclusion

Migrating profile data from GPM Login v4 to GPM Login Global isn't complicated — the key is picking the right method for your needs: manual cookie export/import if you only need web login state, or the 4-file migration tool if you need Telegram and Discord logins kept intact too. Whichever you choose, prepare your proxy and profile-name lists carefully first, and remember that a new fingerprint on the migrated profile is expected behavior, not a software bug.