Preparation of Migration Documents from OSS version GROWI to GROWI.cloud
GROWI Inc. released migration documentation and an AI diagnostic tool to help users move from the self-hosted GROWI OSS to GROWI.cloud, citing a 50% year-over-year increase in migration inquiries.
📋 Article Processing Timeline
- 📰 Published: March 30, 2026 at 19:00
- 🔍 Collected: March 30, 2026 at 22:56 (3h 56m after Published)
- 🤖 AI Analyzed: April 22, 2026 at 06:21 (535h 25m after Collected)
GROWI Inc. (Headquarters: Takadanobaba Access 10F, 2-20-15 Nishiwaseda, Shinjuku-ku, Tokyo, CEO: Yuki Takei) has started organizing and publishing help documents regarding data migration from the OSS version of GROWI to GROWI.cloud, as well as providing an AI migration diagnostic tool.
We have released more detailed information than before, such as an estimated cost and the steps to migration when requesting migration work from GROWI.cloud support.
Additionally, by reducing the effort required to prepare an estimate through an AI-based preliminary diagnosis, we smooth the process from considering migration to making an inquiry.
---
## ■ About GROWI and GROWI.cloud
GROWI is an open-source information sharing tool developed and published by GROWI Inc.
Equipped with features such as flexible document creation using Markdown, real-time simultaneous multi-user editing, and page management in a hierarchical structure, it is used by a wide range of organizations, including engineering teams, as an internal Wiki or knowledge base.
GROWI is provided in two forms: 'GROWI OSS (Self-hosted)' and 'GROWI.cloud (Cloud service)'.
The OSS version is a format in which the software is built and used on your own server, and all infrastructure management, version upgrades, and security patch applications must be handled by the user.
On the other hand, all infrastructure management tasks for GROWI operated on GROWI.cloud are handled by our company.
Since the functionality and usability are basically the same in either form, you can continue your current operational style as it is even if you migrate from the OSS version to GROWI.cloud.
* Depending on the plan you contract with GROWI.cloud, some settings from the OSS version may not be carried over. For details, please check the features and pricing page on the official website.
---
## ■ Background of the increase in migration from OSS version GROWI to GROWI.cloud
In recent years, we have seen an increase in inquiries from companies and organizations operating the OSS version of GROWI on their own servers who are considering migrating to GROWI.cloud for the following reasons.
Both the number of migration inquiries received and the number of migration tasks executed in FY2025 increased by about 50% compared to FY2024.
The new fiscal year, when infrastructure inventories and budget formulation take place, is likely an opportunity to make a decision on such migrations.
Therefore, in line with the new fiscal year, help documents regarding data migration to GROWI.cloud
We have released more detailed information than before, such as an estimated cost and the steps to migration when requesting migration work from GROWI.cloud support.
Additionally, by reducing the effort required to prepare an estimate through an AI-based preliminary diagnosis, we smooth the process from considering migration to making an inquiry.
---
## ■ About GROWI and GROWI.cloud
GROWI is an open-source information sharing tool developed and published by GROWI Inc.
Equipped with features such as flexible document creation using Markdown, real-time simultaneous multi-user editing, and page management in a hierarchical structure, it is used by a wide range of organizations, including engineering teams, as an internal Wiki or knowledge base.
GROWI is provided in two forms: 'GROWI OSS (Self-hosted)' and 'GROWI.cloud (Cloud service)'.
The OSS version is a format in which the software is built and used on your own server, and all infrastructure management, version upgrades, and security patch applications must be handled by the user.
On the other hand, all infrastructure management tasks for GROWI operated on GROWI.cloud are handled by our company.
Since the functionality and usability are basically the same in either form, you can continue your current operational style as it is even if you migrate from the OSS version to GROWI.cloud.
* Depending on the plan you contract with GROWI.cloud, some settings from the OSS version may not be carried over. For details, please check the features and pricing page on the official website.
---
## ■ Background of the increase in migration from OSS version GROWI to GROWI.cloud
In recent years, we have seen an increase in inquiries from companies and organizations operating the OSS version of GROWI on their own servers who are considering migrating to GROWI.cloud for the following reasons.
Both the number of migration inquiries received and the number of migration tasks executed in FY2025 increased by about 50% compared to FY2024.
The new fiscal year, when infrastructure inventories and budget formulation take place, is likely an opportunity to make a decision on such migrations.
Therefore, in line with the new fiscal year, help documents regarding data migration to GROWI.cloud