Essential Information for ASEAN Server Migration?
1.V-net V2.0 is not an iteration of V-net V1.0, and there may be differences in certain features and interfaces. Some data may not be transferable to the new V-net V2.0 platform. (For details, please refer to the Disclaimer or Feature Comparison Table.)
2.The migration process will be executed in 2 phases：
Phase 1: Manual Migration (June 10, 2025 – June 24, 2025) — Recommended
Our team will conduct pre- and post-migration data validation to ensure seamless transition integrity. Users need to apply for manual migration independently during May 20, 2025 – June 9, 2025
(Contact the distributors or check platform pop-up notifications)
Phase 2: Unified Migration (June 25, 2025 – July 6, 2025)
Our team will migrate the remaining accounts on V-net 1.0 to V-net 2.0 in batches. This phase will not involve manual verification, which may result in partial functional anomalies
Manual migration will be scheduled based on received client migration requests. Due to some objective factors including time zone differences, advance notification may not be feasible. If you can not login V-net after submitting a migration request, this likely indicates ongoing migration activities. Please reattempt access V-net platform after 2-3 hours later.
3.During manual migration, our team will perform necessary migration procedures and verification under the authorization of each user. We recommend that you strengthen your account security after completing the platform migration.
4.After migration, please ensure to use the updated software and new domain to access the V-net 2.0 platform and its devices.(Download link will coming soon)
5.Additionally, we will clear accounts that have not logged in for over 90 days and are not bound to any device at 00:00 (UTC+8) on June 9,2025.
6.V-net 1.0 platform will be ended at 00:00 (UTC+8) on 1st Aug,2025.
7.Do not bind devices on the V-net 2.0 platform if they are already bound to any V-net 1.0 accounts.Do not share V-net 2.0 accounts with others.These operations may cause data issues affecting future migration processes.