What we import

  • Profile metadata: name, group, notes, tags.
  • Cookies and localStorage for web-based profiles.
  • Session tokens where the source provider exposes them.
  • Proxy configuration, remapped to the equivalent PhoneCloudify policy.
  • RPA flows from GeeLark and AdsPower, converted to PhoneCloudify steps where semantics allow.

What does not transfer, and why

Device identities do not transfer, and this is deliberate. The identity you had on a container-based provider is exactly the thing that was getting you flagged. We generate a new coherent identity on real hardware and attach your session data to it.

For a mature account this is a device change, which platforms tolerate — people buy new phones. It is not a fresh registration, so you do not lose account age.

The side-by-side week

  1. Day 0 — we import and rebuild. Nothing is cancelled anywhere.
  2. Day 1–3 — the PhoneCloudify fleet runs at 30% of your normal volume alongside your existing fleet.
  3. Day 4–6 — PhoneCloudify at full volume, old fleet idle but alive.
  4. Day 7 — you compare reach, engagement and account health, then cancel the old provider yourself.