Guide to Merge Different Zoho Organizations into One Unified Instance
Identification of Organizations and Applications
This article will guide you though the process of merging different Zoho Organizations into one instance. If you would like to learn about Zoho Organisation, please refer to this documentation.The first step in merging your organizations is to identify all source organizations involved and gather details such as organization IDs, primary admin email contacts, and the applications associated with each organization.
Example: Lets consider a customer wants to merge three different Zoho Organizations named Org A, B & T.
Org A has Zoho Cliq, Zoho Vault, Zoho Connect, and Zoho Directory.
Org B has Zoho Cliq, Zoho Vault, and Zoho Forms.
Org T(Target Org) has Zoho One, Zoho Connect, Zoho Cliq, and Zoho Forms.
Collecting these details helps us understand the current applications state before the merge.
Org A has Zoho Cliq, Zoho Vault, Zoho Connect, and Zoho Directory.
Org B has Zoho Cliq, Zoho Vault, and Zoho Forms.
Org T(Target Org) has Zoho One, Zoho Connect, Zoho Cliq, and Zoho Forms.
Collecting these details helps us understand the current applications state before the merge.
Review of Application Overlaps and Conflicts
Next, we carefully review all applications across the organizations to identify any overlaps and conflicts. Certain applications, such as Zoho Cliq and Zoho Vault, can only have one active instance in the merged organization.
Example:
Zoho Cliq exists in Org A, Org B, and Org T.
Zoho Cliq exists in Org A, Org B, and Org T.
Zoho Vault is present in Org A and Org B.
Zoho Connect appears in Org A and Org T.
Zoho Forms is available in Org B and Org T.
These overlapping applications will require a decision on which instance to retain.
Determining Application Retention
Following the review, you should determine which instances of overlapping applications will be retained. You have to decide which of each duplicate application will remain active post-merge, and the other instances will be removed.
Example: Lets assume Organization admins chooses to retain the following services:
Zoho Cliq from Org T
Zoho Vault from Org B
Zoho Connect from Org A
Zoho Forms from Org T
Zoho One from Org T.
Zoho Cliq from Org T
Zoho Vault from Org B
Zoho Connect from Org A
Zoho Forms from Org T
Zoho One from Org T.
Accordingly, duplicate instances in the other organizations will be deleted during the merge.
Org Admins Confirmation and Approval
Before proceeding, we request confirmation and approval from the administrators of all involved three organizations. Each admin must provide consent emails clearly specifying which application instances they agree to retain and which duplicate instances they approve for permanent deletion. Additionally, they must agree to merge the organizations under these terms.
Example: Admins from Org A, Org B, and Org T are asked to confirm their approval to retain Zoho Cliq from Org T, Zoho Vault from Org B, Zoho Connect from Org A, Zoho Forms from Org T, and Zoho One from Org T. They must also consent to delete the duplicate applications in the other organizations and approve the overall merge.
Verification of Confirmations
Once all confirmations are received, we verify that responses are complete and consistent, ensuring no open questions or objections remain. This verification step ensures a smooth merge without conflicts.
Example: Zoho Team will validate that all admins from Org A, Org B, and Org T have provided their consent emails agreeing to the retention and deletion decisions for the applications and the merge itself.
Execution of the Merge
With approvals finalised, we proceed to execute the merge from backend. This involves deleting the duplicate application instances according to the agreed plan and consolidating all data and access into the target organization.
Example:
Zoho Cliq instances from Org A and Org B are deleted, retaining only Org T’s Zoho Cliq.
Zoho Vault from Org A is deleted, retaining Org B’s instance.
Zoho Connect from Org T is deleted, retaining Org A’s instance.
Zoho Forms from Org B is deleted, retaining Org T’s instance.
Zoho One from Org T remains intact.
Zoho Cliq instances from Org A and Org B are deleted, retaining only Org T’s Zoho Cliq.
Zoho Vault from Org A is deleted, retaining Org B’s instance.
Zoho Connect from Org T is deleted, retaining Org A’s instance.
Zoho Forms from Org B is deleted, retaining Org T’s instance.
Zoho One from Org T remains intact.
User data and permissions from all organizations are consolidated accordingly.
Post Merge Validation and Communication
After the merge, we conduct a thorough validation to ensure that all applications are working correctly and that user data and access rights are properly maintained. We then communicate the successful completion of the merge to all Org admins involved.
Example:
The final merged organization includes the following applications:
Zoho Cliq (retained from Org T)
Zoho Vault (retained from Org B)
Zoho Connect (retained from Org A)
Zoho Forms (retained from Org T)
Zoho One (retained from Org T).
Zoho Cliq (retained from Org T)
Zoho Vault (retained from Org B)
Zoho Connect (retained from Org A)
Zoho Forms (retained from Org T)
Zoho One (retained from Org T).
Users from Org A and Org B are fully integrated, and all applications function as expected. Confirmation of completion is sent to all organization admins.
Points to be Noted:
- This is a manual, exception-based process not generally supported as a self-service option and is handled based on requests.
- Zoho reserves the right to approve or deny such requests based on internal policies and technical constraints.
Article Created by Maddy | Zoho Partner SupportIf you need any further clarifications, please don’t hesitate to contact partner-support@zohocorp.com.
Additionally, we kindly ask all Europe and UK Partners to reach out to partner-support@eu.zohocorp.com.