iMinKit Device Management Capabilities Are Migrating to KiwiCloud

Q1: What does this migration announcement mean?

iMinKit's device management module will remain operational until December 31, 2026, 23:59. After that, iMinKit will only retain basic capabilities such as device ownership, partner management, device allocation, and after-sales operations. To continue using device management capabilities — including remote control, policy management, application management, and remote assistance — you need to migrate to the KiwiCloud platform.

Q2: What do I need to do now?

Submit your migration intent by completing and submitting the Migration Application Form on the iMinKit platform. You will find the entry point "iMinKit Device Management Capabilities Are Migrating to KiwiCloud" displayed above the banner when you log in. Once received, the KiwiCloud team will reach out proactively to align on a migration schedule.

Please be patient after submitting your application — migration scheduling is not first-come-first-served (see Q4). The KiwiCloud team plans each customer's migration on a per-customer basis, taking factors such as region, device models, and device quantity into account, and will contact you directly when your migration window is ready to be discussed.

Q3: How does the migration process work?

The standard migration process begins with Pre-Project Engagement — informal early touchpoints where you explore KiwiCloud, review the Migration Playbook and FAQ, and may use a KiwiCloud Trial Account. The formal migration then proceeds through five phases:

1. Phase 1 — Application — Customer submits the Migration Application Form on the iMinKit platform, confirming preconditions, business hours, and the project contact. The KiwiCloud team checks this against the Device Compatibility Test (DCT) — an ongoing verification that the KiwiCloud platform supports your device models, Android OS, and firmware versions — before scheduling project kick-off.
2. Phase 2 — Preparation — Project kick-off; the KiwiCloud team shares supporting migration documents including the Migration Playbook, Migration Appendix, Migration Readiness Checklist, and Migration Acceptance Checklist. Regional service node and migration date are confirmed, and the Readiness Checklist is submitted.
3. Phase 3 — Test Migration (Optional) — If you'd like to verify application upgrades, data synchronization, and business continuity before committing, the KiwiCloud team configures iMin APP Store and Remote Assistance upgrading policies for test devices and performs a test migration. This phase can be skipped if you prefer to proceed directly to Phase 4.
4. Phase 4 — Official Migration — The KiwiCloud team extends the upgrading policies to all devices, and then performs the official migration to synchronize all data and configurations from iMinKit to the KiwiCloud platform.
5. Phase 5 — Acceptance — Customer observes and verifies business continuity across all devices, then signs off the Migration Acceptance Checklist to formally close the project.

Q4: Is migration scheduled on a first-come-first-served basis?

No. Migration is planned by the KiwiCloud team on a per-customer basis, taking into account factors such as region, device models, and device quantity. The KiwiCloud team will reach out proactively to align on a migration schedule and will keep you informed ahead of any official migration action.

Q5: Is there a deadline for migration?

Yes. Migration is free of charge only for accounts completing migration before December 31, 2026, 23:59. Accounts migrating after this deadline may incur additional license or migration costs. Early migration is strongly recommended.

Q6: Will my business operations be disrupted during migration?

No. End-user device operations — including POS transactions and business applications — will continue to function normally throughout all phases of the migration. There is no interruption to device-side applications at any point. Some management interfaces may temporarily appear blank during the migration window, but this does not affect device operations.

Q7: How long does the migration take?

The total duration varies by customer, depending on factors such as device quantity, region, operational readiness, Device Compatibility Test (DCT) coverage for your devices, and whether you choose to complete the optional Test Migration phase. Each phase has its own typical duration — please confirm the current end-to-end estimate with your dedicated KiwiCloud CSE, as this depends on your specific device fleet and chosen path through the phases.

Within that timeline, the actual data synchronization from iMinKit to KiwiCloud (the Official Migration Auto-Task itself) is much shorter — typically 5 to 20 minutes, depending on data scale. The KiwiCloud team will discuss and confirm a specific schedule with each customer in advance.

Q8: Will I be charged to use KiwiCloud after migration?

Devices paid for on or before June 30, 2026, 23:59 — including all legacy devices covered in this migration — will receive a Free Lifetime KC iMin Essential License. This license is tied to the physical device serial number (SN) until device retirement, transfers with the device upon ownership transfer, and cannot be reassigned to devices outside the stated migration scope. There is no charge for these devices.

Q9: What license tier will my devices be on after migration?

By default, migrated devices will be on the Free Lifetime KC iMin Essential License, which supports IMA (iMinKit Managed Access) and KMA (KiwiCloud Managed Access) modes. Customers who require access to more advanced features — such as GMA (Google Managed Access) mode, geolocation features, or enhanced support — can upgrade to the KC Enhanced license. Please contact your KiwiCloud Sales Representative for pricing.

Q10: What happens to devices procured after June 30, 2026?

For activated IMA-eligible devices purchased after June 30, 2026 (iMin Android 13 and earlier), a 60-day Complimentary KC iMin Essential License is automatically provided from the account migration date. This complimentary license is a transitional grace period and is not tied to the device — it will not be transferred with the device upon ownership transfer. After the 60-day complimentary period, a paid KC Enhanced license is required to continue management on the KiwiCloud platform. Please contact your KiwiCloud Sales Representative for pricing.

Q11: Can the Free Lifetime KC iMin Essential License be transferred to a new device?

The Free Lifetime KC iMin Essential License is tied to the physical device SN until device retirement. It transfers with the device upon ownership transfer, but cannot be reassigned to devices outside the stated migration scope (i.e., it cannot be moved to a new device that was not part of the original migration).

Q12: What data will be migrated from iMinKit to KiwiCloud?

The following data will be migrated:

• iMinKit Official Account and all associated iMinKit Sub-accounts (full organizational hierarchy). For accounts holding the Super Admin role (registered when an organization or sub-organization is created), both the physical account and its iMinKit-side authorization (Cooperative or Controllable sub-type) are synchronized to the KiwiCloud platform. For non-Super-Admin accounts (e.g., iMinKit User Accounts holding an Ordinary Admin role), only the physical account is synchronized.
• All enrolled devices
• Device grouping configurations and legacy policies
• Application libraries, publish policies, update policies, and kiosk configurations
• Configuration data including compliance rules, boot animations, secondary screen ads, permission settings, and scanner configurations

The following will NOT be migrated:

• All types of logs (system logs, operation logs, device logs)
• My Apps — remains available on the iMinKit platform until December 31, 2026, 23:59; no longer available from 2027
• iMin APP Store management functions — no longer available on the iMinKit platform from the point of official migration
• User authorization for non-Super-Admin accounts — the iMinKit-side roles and access permissions of iMinKit User Accounts (e.g., Ordinary Admins) are not synchronized to the KiwiCloud platform. After migration, the KiwiCloud Super Administrator must assign roles and access permissions to these accounts on the KiwiCloud platform before they can access it. See Appendix 1 — Account Types and Terminology for details.

Q13: Will my existing configurations and policies be preserved after migration?

Yes. Existing device grouping configurations and APP policies are synchronized and converted into KiwiCloud platform-structured formats during the official migration. Capabilities such as device management, APP policies, remote assistance, scheduled tasks, notifications, and user authorization are delivered by the KiwiCloud UEM platform after migration. For an overview of capability coverage before and after migration, refer to the Capability Coverage table in the Migration Playbook, Section 2.1.

Q14: Will iMinKit be shut down after migration?

No. Only iMinKit's device management capability will be retired by December 31, 2026, 23:59. iMinKit itself will continue to operate beyond 2026 for the following capabilities:

• Account management — company profile, partners, operators, support, and ticket records
• Device ownership — device overview, transfer, allocation, and gifting

In addition, My Apps on iMinKit is not migrated to the KiwiCloud platform but remains available on iMinKit until December 31, 2026, 23:59; from 2027 onwards, My Apps will no longer be available. Other iMin APP Store management functions on iMinKit will no longer be available from the point of official migration. APP policy configuration functions on iMinKit (such as blacklist) are migrated to the KiwiCloud UEM platform together with the customer's APP policies. Customers are advised to familiarize themselves with the corresponding KiwiCloud platform capabilities during Phase 2 — Preparation.

Q15: Can I partially migrate some devices and leave others on iMinKit?

No. All devices under your iMinKit Official Account must be migrated together. Partial migration is not supported — devices that remain unmanaged after the iMinKit device management module is retired on December 31, 2026 will no longer be manageable.

Q16: What happens if a device is offline during the migration?

The KiwiCloud platform's shadow device mechanism retains and auto-executes management commands upon reconnection. Devices that are offline during the migration window will be automatically synchronized when they come back online. It is strongly recommended to keep all devices online and network-connected throughout the migration window.

Q17: Can I log in to KiwiCloud using my existing iMinKit account credentials?

Yes, but only after your iMinKit Official Account has been migrated. Upon successful migration, your iMinKit Official Account becomes a KiwiCloud Migrated Account, accessible to both the iMinKit platform and the KiwiCloud platform using the same email address and password. A "Log in to KiwiCloud" shortcut will also appear in the upper-right corner of your iMinKit page after migration.

Q18: Will my password be the same on both platforms after migration?

At the point of migration, yes — both platforms share the same credentials. However, after a successful official migration, the KiwiCloud platform account password can be changed independently and may subsequently differ from the iMinKit platform password. The two platforms have independent authentication systems; a password change on one platform does not automatically sync to the other.

Q19: Will my sub-accounts and organizational structure be migrated?

Yes. All iMinKit Sub-accounts (partner and sub-organization accounts) are migrated together with the iMinKit Official Account during the official migration, preserving the full organizational hierarchy on the KiwiCloud platform. After migration:

• Super Admins (the founding accounts of each organization and sub-organization, including yours and your partners') are automatically synchronized as KiwiCloud Super Admins with the same email credentials and full management access to their respective organizational scopes on the KiwiCloud platform.
• Other iMinKit User Accounts (e.g., Ordinary Admins created on iMinKit) are also synchronized to the KiwiCloud platform as physical account entities, but their iMinKit roles and access permissions are not carried over. The corresponding KiwiCloud Super Admin must assign new roles and access permissions to these accounts on the KiwiCloud platform before the users can access it.

For details on the post-migration authorization model, refer to Appendix 1 — Account Types and Terminology.

Q20: I created a sub-organization on the KiwiCloud platform, but I can't find it on iMinKit. Why?

This is expected behavior. The iMinKit and KiwiCloud platforms have an asymmetric synchronization relationship:

• iMinKit → KiwiCloud: Any sub-organization (and its Super Admin) created on the iMinKit platform is automatically synchronized to the KiwiCloud platform — both during official migration and afterwards, for newly created sub-organizations.
• KiwiCloud → iMinKit: Sub-organizations created directly on the KiwiCloud platform are not synchronized back to iMinKit. The two platforms differ significantly in functionality (iMinKit is focused on device ownership management, while KiwiCloud is a full UEM platform with policy, role, and management capabilities that iMinKit does not have), so a one-way sync is the only practical model.

For this reason, customers are recommended to maintain organizational structure — including sub-accounts that hold the Super Admin role — on the iMinKit platform after migration. Sub-organizations created on iMinKit will appear on both platforms (iMinKit and KiwiCloud); sub-organizations created only on KiwiCloud will exist only on KiwiCloud. For details, refer to Appendix 1 — Account Types and Terminology.

Q21: I have been told my iMinKit account is migrated, but I cannot log in to the KiwiCloud platform. Why?

The most common reason is that your account is an iMinKit User Account (e.g., an Ordinary Admin) rather than a Super Admin of your organization. Although your physical account has been synchronized to the KiwiCloud platform during migration, your iMinKit-side roles and access permissions are not automatically carried over — the KiwiCloud Super Admin of your organization must assign you a role and access permissions on the KiwiCloud platform before you can log in.

To resolve this:

1. Identify the KiwiCloud Super Admin of your organization or sub-organization (typically the holder of the email originally registered as your iMinKit Main Account, or the partner's iMinKit Official Account).
2. Ask the KiwiCloud Super Admin to assign you a role with the appropriate access permissions on the KiwiCloud platform.
3. Once the role and permissions are assigned, log in to the KiwiCloud platform with your existing email and password.

If you are a Super Admin and still unable to log in, contact your dedicated KiwiCloud CSE (Customer Service Engineer) for assistance. For further details on the account types and the post-migration authorization model, refer to Appendix 1 — Account Types and Terminology.

Q22: After logging in to the KiwiCloud platform, why is my full name displayed in the first-name field?

This is a known difference in account profile structure between the two platforms. The iMinKit platform stores user identity as a single name field, while the KiwiCloud platform uses two fields — First Name and Surname. When your account is synchronized to the KiwiCloud platform during migration, the entire iMinKit name value is placed into the KiwiCloud First Name field by default, leaving the Surname field empty.

This does not affect your account access, role, or device management functions. You can edit your profile on the KiwiCloud platform at any time to split the value into First Name and Surname as you prefer.

Q23: I already have a KiwiCloud account under the same email as my iMinKit account. What happens?

This situation can arise in two ways:

Scenario 1 — KiwiCloud Standalone Account
A KiwiCloud Standalone Account may have been created by the KiwiCloud team under your iMinKit Official Account email address during the early access period (March–April 2026). Although the Standalone Account is accessible to both the iMinKit platform and the KiwiCloud platform using the shared email address, it was created independently of any migration operation — so the iMinKit-to-KiwiCloud synchronization mechanism has never been triggered, and none of your iMinKit organization structure exists under the Standalone Account on the KiwiCloud platform. Since the official migration requires creating a KiwiCloud Migrated Account under your iMinKit Official Account email, this existing Standalone Account would cause a conflict.

Scenario 2 — KiwiCloud User Account created under the same email as an iMinKit Sub-account
The email address used for an iMinKit Sub-account may have also been registered as a KiwiCloud User Account (a user created directly on the KiwiCloud platform under another customer's or partner's account). Since iMinKit Sub-accounts are migrated together with the iMinKit Official Account and will need to be accessible on the KiwiCloud platform under the same email credentials, a pre-existing KiwiCloud User Account under the same email could create a conflict.

In both scenarios, you must confirm consent to the KiwiCloud team to clear all existing data on the conflicting KiwiCloud platform account before migration can proceed. Migration is not recommended without this authorization. Please contact your dedicated KiwiCloud CSE to identify and resolve any such conflicts before migration begins.

Q24: What is a KiwiCloud Trial Account, and is it the same as my official account after migration?

A KiwiCloud Trial Account is a separate account provisioned by the KiwiCloud team under a different email address from your iMinKit Official Account. It comes with a complimentary 60-day KC Enhanced license for you to explore the KiwiCloud platform before your official migration. It is not your official migrated account — the two are completely separate. The KiwiCloud Trial Account will be deleted by the KiwiCloud team at the start of Phase 4 — Official Migration, prior to the official migration.

Q25: How do I acquire a KiwiCloud Trial Account?

1. Register an iMinKit account using a different email address from your iMinKit Official Account at https://kit.imin.sg/user/register. A different email is required to avoid conflict with your existing iMinKit Official Account during the Trial Account provisioning flow.
2. Inform your dedicated KiwiCloud CSE of the email address you registered. The CSE will then perform the account synchronization to the KiwiCloud platform and provision the trial license.

For details on the provisioning flow and license tier variations (existing iMinKit customers vs. new customers), refer to Appendix 1 — Account Types and Terminology.

Q26: Will my existing apps and configurations in iMinKit be available in KiwiCloud after migration?

Yes. All app-related data and configurations — including application libraries, publish policies (such as blacklists), update policies, and kiosk configurations — are migrated to the KiwiCloud platform as part of the official migration. Customers can find their published APPs on the KiwiCloud platform through a function entry equivalent to My Apps on iMinKit.

For continuity during the migration period, the My Apps function entry on iMinKit remains available — for reference and review of previously published APPs — until December 31, 2026, 23:59. From 2027 onwards, the My Apps function entry on iMinKit is no longer available, but the underlying APP data continues to be managed on the KiwiCloud platform.

Q27: Will the iMin APP Store on my devices change after migration?

Yes. The iMin APP Store on devices will be upgraded from the legacy iMinKit-controlled interface to the new KiwiCloud platform-controlled interface as part of the migration process. The upgrade is delivered via an upgrading policy configured by the KiwiCloud team on the iMinKit platform. You can verify that the upgrade has been successfully applied by opening the iMin APP Store on the device — if the upgrade is complete, the UI will appear visually different from the legacy interface, reflecting the new KiwiCloud platform-controlled design.

Q28: Can I still manage app releases on iMinKit after migration?

Yes, but only until the iMinKit device management module is retired. Customers retain the ability to manage business application releases on the iMinKit platform until December 31, 2026, 23:59. After that date, all application management must be performed on the KiwiCloud platform.

Q29: What device management modes does KiwiCloud support?

The KiwiCloud platform supports three device management modes:

Most legacy iMin devices will be managed under IMA mode after migration. KMA and GMA modes are available for newer devices with the appropriate license.

Q30: Will my devices need any physical changes or manual reconfiguration during migration?

No physical changes or hardware replacements are required. Device OS versions will remain as-is throughout the migration. The main device-side changes are:

• iMin APP Store UI upgrades to the KiwiCloud platform-controlled interface
• Remote Assistance upgrades to KiwiCloud Remote Assistance
• AnyDesk is installed on devices after the official migration via an app release policy configured by the KiwiCloud team on the KiwiCloud platform

All of these are delivered automatically via policies — no manual on-device action is required under normal circumstances.

Q31: What happens to my devices' network and firewall configuration?

Customers may need to whitelist specific KiwiCloud platform domains and ports in their network and firewall configuration to ensure device connectivity to the KiwiCloud platform. The KiwiCloud team will provide the full list of required domains and ports at project kick-off. Please contact your dedicated KiwiCloud CSE for the network whitelist details in advance if needed.

Q32: What is KiwiCloud Remote Assistance?

KiwiCloud Remote Assistance is the upgraded version of the iMin-developed Remote Assistance application. After upgrading, the application is designed to redirect end-user remote access requests to AnyDesk via system call, replacing the legacy iMin remote assistance service.

Q33: Will remote assistance be charged after migration?

No. Remote assistance remains free after migration, delivered through KiwiCloud Remote Assistance (AnyDesk). If you need to increase the number of concurrent remote assistance sessions, contact your KiwiCloud Sales Representative to discuss upgrade options.

Q34: Do I need to manually download or install AnyDesk?

No manual download or installation is required. After the official migration, AnyDesk is automatically installed on devices via an app release policy configured by the KiwiCloud team on the KiwiCloud platform. The AnyDesk companion add-on (AD1) is also automatically downloaded and installed as a background service by AnyDesk itself.

Q35: How long will it take for AnyDesk to be installed on all my devices after migration?

After the official migration, the KiwiCloud team configures AnyDesk installation policies on the KiwiCloud platform for all devices. Devices will receive and install AnyDesk progressively — online devices will receive it within hours, while devices that are offline at the time will receive it when they next come online. We recommend scheduling the migration during low-traffic business hours to maximize the number of devices that receive AnyDesk promptly.

Q36: I installed the free version of AnyDesk myself. Will it conflict with the KiwiCloud-integrated AnyDesk?

No conflict. KiwiCloud uses a customized version of AnyDesk that does not interfere with the free version you installed independently. Note, however: if you previously used a paid KiwiCloud AnyDesk license and later switch back to the free version, you must first remove the configured license from the AnyDesk client; otherwise the free version may show "disconnected by your system administrator".

Q37: Is the free concurrent remote assistance session shared between the main account and sub-accounts?

Yes. The single concurrent remote assistance session provided under the free tier is shared between the main account and all of its sub-accounts.

Q38: What is the difference between a Test Migration and an Official Migration?

• Test Migration — An optional phase (Phase 3), performed by the KiwiCloud team on the customer's iMinKit Official Account, covering test devices only. It temporarily converts the iMinKit Official Account into a KiwiCloud Migrated Account, allowing the customer to verify platform connectivity and business continuity on test devices before committing to the official migration. The test migration can be rolled back. Customers who prefer to proceed directly to Official Migration may skip this phase.
• Official Migration — Performed by the KiwiCloud team during Phase 4 (Official Migration) on the customer's iMinKit Official Account, covering all devices. This is the definitive, permanent migration. If a Test Migration was performed, the KiwiCloud team rolls it back first to ensure a clean starting state. The official migration data synchronization itself typically completes within a few minutes.

Q39: What is the KiwiCloud regional service node, and which one should I choose?

The KiwiCloud platform operates dedicated regional service nodes to ensure your device management data stays within its designated geographic region, supporting data residency requirements and local regulatory compliance. Available nodes are:

• Europe — Frankfurt
• Asia-Pacific — Singapore
• USA — N. Virginia
• China — Beijing

The appropriate node is determined based on your country/region of operation and will be confirmed with you by the KiwiCloud team at project kick-off. If you are unsure, please contact your dedicated KiwiCloud CSE for guidance.

Q40: Will logs from iMinKit be available in KiwiCloud after migration?

No. All types of logs — including system logs, operation logs, and device logs — are not included in the migration and will not be inherited by the KiwiCloud platform. Historical logs will remain accessible on iMinKit for reference purposes. New logs will be generated on the KiwiCloud platform from the point of migration onwards.

Q41: Can I roll back the migration if something goes wrong after the official migration?

Yes, during the Phase 5 — Acceptance period (recommended minimum of one week). If wide-range business disruption is observed, the customer can trigger a rollback decision and notify the KiwiCloud team, who will perform the technical rollback. Specific rollback criteria and the scope of rollback will be discussed and agreed with each customer on a case-by-case basis prior to migration. Please note that any new configurations created on the KiwiCloud platform during the acceptance phase will not be preserved if a rollback is triggered, as the KiwiCloud platform supports many functions that iMinKit does not.

Q42: What should I do if my iMin APP Store or Remote Assistance application is blacklisted on the iMinKit platform?

You must remove the blacklist entries for iMin APP Store and Remote Assistance from your iMinKit platform before the KiwiCloud team configures the upgrading policies. Blacklisting either application will prevent the upgrading policies from being applied successfully. Please log in to the iMinKit platform and check your blacklist settings under the app management section, and remove any such entries before the migration project begins.

Q43: What is a KiwiCloud Standalone Account, and how is it different from a Trial Account?

A KiwiCloud Standalone Account is a KiwiCloud platform account that was created independently of any migration operation, before the customer's iMinKit Official Account had been migrated to the KiwiCloud platform. These accounts were provisioned by the KiwiCloud team for certain customers during March–April 2026 as an early access arrangement and are no longer created for existing iMinKit customers from May 2026 onwards.

KiwiCloud Standalone Accounts fall into two patterns based on email registration:

• Most share the same email address as the customer's iMinKit Official Account, so they are accessible to both the iMinKit platform and the KiwiCloud platform — but no migration operation has been performed, so the two platforms operate independently for this account.
• A few were registered with a different email address from the customer's iMinKit Official Account, so they are accessible to the KiwiCloud platform only.

In either case, because no migration operation has taken place, none of the customer's iMinKit organization structure exists under the Standalone Account on the KiwiCloud platform — the Standalone Account begins as an empty workspace on the KiwiCloud platform.

A KiwiCloud Trial Account, by contrast, is provisioned under a different email address from the iMinKit Official Account, and its provisioning flow triggers the iMinKit-to-KiwiCloud synchronization mechanism so the customer can authentically experience how iMinKit organization structure synchronizes to the KiwiCloud platform.

Q44: How can I tell whether the KiwiCloud trial account I hold is a KiwiCloud Standalone Account or another account type?

Customers may not always know which account type they hold. The following diagnostic guidance helps identify the correct type:

• If the KiwiCloud trial account you hold is accessible to the KiwiCloud platform only (i.e., the registered email address cannot log in to the iMinKit platform), that account is a KiwiCloud Standalone Account.
• If the KiwiCloud trial account you hold shares the same email address as your iMinKit Official Account, log in to the iMinKit platform with the shared email address and check the iMinKit interface:
  • If the iMinKit interface still shows full Device Management and iMin APP Store functions (refer to the Migration Playbook for the pre-migration interface), the KiwiCloud trial account is a KiwiCloud Standalone Account — because the iMinKit interface has not been limited through any migration operation.
  • If the iMinKit interface shows limited Device Management and iMin APP Store functions (i.e., the iMinKit device management module has been retired or restricted as a result of migration), the KiwiCloud trial account is not a KiwiCloud Standalone Account — it is most likely a KiwiCloud Migrated Account resulting from a prior Official Migration Auto-Task.

If you are unsure, please contact your dedicated KiwiCloud CSE.

Q45: I hold a KiwiCloud Standalone Account. Should I transition to a KiwiCloud Trial Account, and how?

Yes, transitioning is recommended. Because a KiwiCloud Standalone Account was created without a migration operation, the iMinKit-to-KiwiCloud synchronization mechanism is never triggered for it — meaning you cannot authentically explore how your iMinKit organization structure synchronizes to the KiwiCloud platform, which is one of the key purposes of pre-migration trial usage. Transitioning to a KiwiCloud Trial Account provisions this synchronization mechanism and provides a clearer and supported pathway toward the Official Migration Auto-Task.

The transition is performed by the KiwiCloud team in two steps:

1. The existing KiwiCloud Standalone Account is deleted by the KiwiCloud team.
2. A different email address (not currently registered with any account on either the iMinKit platform or the KiwiCloud platform) is used to register the new KiwiCloud Trial Account.

To initiate the transition, contact your dedicated KiwiCloud CSE.

Q46: Is it safe to continue using my iMinKit Official Account on the iMinKit platform during test migration?

Yes. Other than the addition of iMin APP Store and Remote Assistance upgrading policies — which are applied only to the test devices you've assigned, and which are the mechanism by which test migration is enabled on those devices — the test migration does not alter the existing data and configurations in your iMinKit Official Account on the iMinKit platform. You can continue using your iMinKit Official Account for routine operations such as device list review, device allocation, device gifting and ownership transfer, and account management throughout the test migration phase.

The test migration only temporarily makes your iMinKit Official Account also accessible on the KiwiCloud platform, allowing you to verify platform connectivity and business continuity on test devices. The test migration can be rolled back by the KiwiCloud team before the official migration begins.

Q47: Why do I need a KiwiCloud Trial Account? Why can't I just explore the KiwiCloud platform using my existing iMinKit Official Account?

The iMinKit Official Account and the KiwiCloud platform are governed by independent authentication systems prior to migration. Your iMinKit Official Account becomes accessible on the KiwiCloud platform only after the Test Migration Auto-Task (Phase 3) or Official Migration Auto-Task (Phase 4) has been performed by the KiwiCloud team. Before that point, your iMinKit Official Account cannot be used to log in to the KiwiCloud platform.

To allow customers to familiarize themselves with the KiwiCloud platform's capabilities before the formal migration takes place, the KiwiCloud team provisions a KiwiCloud Trial Account registered under a different email address. This account comes with a complimentary 60-day KC Enhanced license — the highest license tier — enabling exploration of the full range of KiwiCloud platform features.

A KiwiCloud Trial Account is optional. Customers who prefer to wait until their iMinKit Official Account is migrated may do so. The KiwiCloud Trial Account is deleted by the KiwiCloud team at the start of Phase 4 — Official Migration to prevent any conflict with the official migration process.

Q48: Why do I need a KiwiCloud Bridging Account?

A KiwiCloud Bridging Account is only needed if you have purchased iMin devices running Android OS 14 or above (eligible for KMA mode) or GMS-certified Android OS 13 or above (eligible for GMA mode), and you need to begin managing these devices before your iMinKit Official Account has been officially migrated.

These newer devices cannot be managed on the iMinKit platform — iMinKit only supports IMA mode. The KiwiCloud UEM platform is the only management platform that supports KMA and GMA modes, so customers with such devices need access to the KiwiCloud platform from day one of device deployment, which may be earlier than their scheduled official migration.

The KiwiCloud Bridging Account is provisioned by the KiwiCloud team under a different email address from your iMinKit Official Account, and is accessible to both the iMinKit platform and the KiwiCloud platform. It is a transitional arrangement — once your iMinKit Official Account has been officially migrated and becomes a KiwiCloud Migrated Account, the KiwiCloud Bridging Account is consolidated accordingly. Customers who do not have Android 14+ or GMS-certified Android 13+ devices do not require a KiwiCloud Bridging Account.