Migration scope and customer considerations for moving from Lingma Enterprise Dedicated Edition to Qoder CN (Full Suite) Enterprise VPC.
This document explains how to migrate enterprise member lists and AI conversation history from an existing Lingma Enterprise Dedicated Edition instance to Qoder CN (Full Suite) Enterprise VPC.
Lingma Enterprise VPC and Qoder CN (Full Suite) Enterprise VPC use different commodity codes, so a seamless one-click migration is not currently available. You must first purchase a new Qoder CN (Full Suite) Enterprise VPC instance and then cancel the previous Lingma Enterprise Dedicated Edition instance based on your requirements.
The migration service supports two types of account and data transition: migrating the enterprise member list and retaining members' AI conversation history.
This migration service is available only to customers who have purchased Qoder CN (Full Suite) Enterprise VPC. It covers the enterprise member list and members' AI conversation history from the existing Lingma Enterprise Dedicated Edition instance.
Orders, refunds, and instance release are not handled as part of this migration. You must manage these commercial and resource-release matters based on your own purchase and usage arrangements.
Purchase a Qoder CN (Full Suite) Enterprise VPC instance and confirm that the new instance meets your requirements. Make sure the target instance has enough seats for all members to be migrated from the Lingma Enterprise Dedicated Edition instance.
You must also provide an email address for every member of the existing Lingma Enterprise Dedicated Edition instance. Qoder CN (Full Suite) Enterprise VPC uses the email address as the unique account identifier. Member migration and subsequent sign-in both depend on this information.
After completing the preparations, provide the following information to the Qoder CN team by submitting a ticket through your account manager or after-sales manager:
Purchase Qoder CN (Full Suite) Enterprise VPC and make sure the number of seats in the target instance is no less than the number of members to migrate.
The relevant commodity codes are:
Evaluate the enterprise management capabilities of Qoder CN (Full Suite) and confirm that you accept the functional differences from Lingma Enterprise Dedicated Edition.
Statistical reports, knowledge management, extension management, and other capabilities from Lingma Enterprise Dedicated Edition are no longer provided in their previous form. Use the corresponding Qoder CN (Full Suite) capabilities, such as Metrics & Insights, Enterprise Knowledge Base, and Extensions & Marketplace. The corresponding policy configuration capability from Lingma is still under development.
Qoder CN (Full Suite) currently does not support importing enterprise members from DingTalk, Feishu, or WeCom.
Every Qoder CN (Full Suite) Enterprise VPC account must be associated with a personal email address. Enterprise VPC uses email addresses as unique account identifiers. Existing sign-in methods, including Yunxiao, Feishu, DingTalk, WeCom, LDAP / AD, SAML / OIDC / CAS / OAuth, are changed to email-and-password sign-in after migration. You can configure SAML, OIDC, or other single sign-on methods later as needed.
Members can add their email addresses themselves. After signing in to the existing dedicated domain, go to
If your team currently relies on the VS Code extension for daily development, switch to Qoder CN IDE or the JetBrains plugin and complete the necessary compatibility checks before migration.
After migration, enterprise members must use the new dedicated domain URL to sign in to their new accounts. In Qoder CN IDE or the JetBrains plugin, members can migrate AI data from the old instance account to the new account, including conversation history, rules, memories, agents, and code indexes. Historical records are retained after migration.
After a member signs in with the new account and migrates AI conversation history, signing in to the original dedicated URL with the old account no longer displays the migrated AI conversation history. Inform all enterprise members in advance and confirm the migration window and member operation schedule.
Administrators can add the actual migration time and target dedicated domain before sending the following message to enterprise members.
As scheduled, the company will perform the Qoder CN (Full Suite) Enterprise VPC migration from XX:XX to YY:YY on Month DD, YYYY.
Before this time, continue signing in through the existing Lingma dedicated URL.
After this time, change the dedicated domain URL to
Cancellation, refunds, and instance release for the existing Lingma Enterprise Dedicated Edition order are outside the scope of this migration. Decide when to cancel or request a refund based on your requirements.
The Lingma Enterprise Dedicated Edition instance is deleted 15 days after the subscription expires. If you actively request a subscription refund, the instance is deleted within 24 hours after the refund. Back up and archive the enterprise data in the existing instance before it is deleted.
Background
Lingma Enterprise VPC and Qoder CN (Full Suite) Enterprise VPC use different commodity codes, so a seamless one-click migration is not currently available. You must first purchase a new Qoder CN (Full Suite) Enterprise VPC instance and then cancel the previous Lingma Enterprise Dedicated Edition instance based on your requirements.
The migration service supports two types of account and data transition: migrating the enterprise member list and retaining members' AI conversation history.
Scope
This migration service is available only to customers who have purchased Qoder CN (Full Suite) Enterprise VPC. It covers the enterprise member list and members' AI conversation history from the existing Lingma Enterprise Dedicated Edition instance.
Orders, refunds, and instance release are not handled as part of this migration. You must manage these commercial and resource-release matters based on your own purchase and usage arrangements.
Prerequisites
Purchase a Qoder CN (Full Suite) Enterprise VPC instance and confirm that the new instance meets your requirements. Make sure the target instance has enough seats for all members to be migrated from the Lingma Enterprise Dedicated Edition instance.
You must also provide an email address for every member of the existing Lingma Enterprise Dedicated Edition instance. Qoder CN (Full Suite) Enterprise VPC uses the email address as the unique account identifier. Member migration and subsequent sign-in both depend on this information.
Information to submit
After completing the preparations, provide the following information to the Qoder CN team by submitting a ticket through your account manager or after-sales manager:
- Target organization ID: the Qoder CN Enterprise VPC organization ID.
- Source organization ID: the existing Lingma Enterprise Dedicated Edition organization ID.
- Expected migration date and time window.
- Email addresses of members in the existing Lingma Enterprise Dedicated Edition instance, or a mapping between existing member accounts and target email addresses.
826fdXXX-8XXX-5XXX-bXXX-d011580aXXXX and df0d6XXX-2XXX-5XXX-bXXX-5cd05f17XXXX.
Migration considerations
1. Purchase the target instance with enough seats
Purchase Qoder CN (Full Suite) Enterprise VPC and make sure the number of seats in the target instance is no less than the number of members to migrate.
The relevant commodity codes are:
- Enterprise VPC subscription:
lingma_CNenterpriseVPC_public_cn - Enterprise VPC resource package:
lingma_CNaddOnEnterprise_public_cn
2. Review capability differences in advance
Evaluate the enterprise management capabilities of Qoder CN (Full Suite) and confirm that you accept the functional differences from Lingma Enterprise Dedicated Edition.
Statistical reports, knowledge management, extension management, and other capabilities from Lingma Enterprise Dedicated Edition are no longer provided in their previous form. Use the corresponding Qoder CN (Full Suite) capabilities, such as Metrics & Insights, Enterprise Knowledge Base, and Extensions & Marketplace. The corresponding policy configuration capability from Lingma is still under development.
Qoder CN (Full Suite) currently does not support importing enterprise members from DingTalk, Feishu, or WeCom.
3. Provide an email address for every member
Every Qoder CN (Full Suite) Enterprise VPC account must be associated with a personal email address. Enterprise VPC uses email addresses as unique account identifiers. Existing sign-in methods, including Yunxiao, Feishu, DingTalk, WeCom, LDAP / AD, SAML / OIDC / CAS / OAuth, are changed to email-and-password sign-in after migration. You can configure SAML, OIDC, or other single sign-on methods later as needed.
Members can add their email addresses themselves. After signing in to the existing dedicated domain, go to {dedicated-domain URL}/users/settings/profile, open Personal settings > Personal information, and add or update the email address. This email address is used to identify the member account after migration to Qoder CN 2.0. If an administrator prepares the account mapping, members must confirm the target email address for each existing sign-in account.
Alternatively, the administrator can collect all member email addresses and submit the list to the Qoder CN team before migration.
4. The VS Code extension is no longer supported after migration
If your team currently relies on the VS Code extension for daily development, switch to Qoder CN IDE or the JetBrains plugin and complete the necessary compatibility checks before migration.
5. Members must use the new dedicated domain URL
After migration, enterprise members must use the new dedicated domain URL to sign in to their new accounts. In Qoder CN IDE or the JetBrains plugin, members can migrate AI data from the old instance account to the new account, including conversation history, rules, memories, agents, and code indexes. Historical records are retained after migration.
6. AI conversation history migration is irreversible
After a member signs in with the new account and migrates AI conversation history, signing in to the original dedicated URL with the old account no longer displays the migrated AI conversation history. Inform all enterprise members in advance and confirm the migration window and member operation schedule.
Member notification template
Administrators can add the actual migration time and target dedicated domain before sending the following message to enterprise members.
Qoder CN (Full Suite) Enterprise VPC sign-in and migration
As scheduled, the company will perform the Qoder CN (Full Suite) Enterprise VPC migration from XX:XX to YY:YY on Month DD, YYYY.
Before this time, continue signing in through the existing Lingma dedicated URL.
After this time, change the dedicated domain URL to abc.yyy.qoder.com.cn and sign in with the email address associated with your existing account. For your first sign-in, use Forgot password on the Qoder CN website to initialize your password. Then sign in to Qoder CN IDE or the JetBrains plugin and follow the AI conversation history migration prompt.
Replace the time and dedicated domain URL with the actual values.