GROWI, Inc. (Headquarters: 10F Takadanobaba Access, 2-20-15 Nishi-Waseda, Shinjuku-ku, Tokyo; Representative Director: Yuki Takei) has organized and published help documentation regarding data migration from the OSS version of GROWI to GROWI.cloud, and has launched an AI migration diagnostic tool.

We have released more detailed information than ever before, including estimated costs for requesting migration work from the GROWI.cloud support team and the steps involved in the migration process. Additionally, by using AI-based preliminary diagnostics to streamline the preparation of estimates, we are making the process from considering a migration to making an inquiry much smoother.

---

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 multi-user editing, and hierarchical page management, it is used by a wide range of organizations, including engineering teams, as an internal wiki or knowledge base.

GROWI is provided in two formats: "GROWI OSS (self-hosted)" and "GROWI.cloud (cloud service)."

The OSS version is a format where the software is built and used on your own company's servers, and infrastructure management, version upgrades, and the application of security patches must all 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 features and usability are basically the same in both formats, you can continue your existing operational style even after migrating from the OSS version to GROWI.cloud.

* Depending on the plan you subscribe to on GROWI.cloud, some settings from the OSS version may not be transferable. Please check the features and pricing page on our official website for details.

---

Background of the Increase in Migrations from OSS GROWI to GROWI.cloud

In recent years, we have received an increasing number of 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.

The number of migration inquiries received and the number of migration projects carried out in fiscal year 2025 both increased by approximately 50% compared to fiscal year 2024.

The new fiscal year, when infrastructure inventory and budget planning take place, is a good opportunity to make decisions about such migrations. Therefore, in line with the new fiscal year, we have reorganized and published help documentation regarding data migration to GROWI.cloud.

### Challenges in Operating the OSS Version

* **Increased Infrastructure Management Costs:** Management costs for the OSS version are rising, including server maintenance and operation expenses, and the man-hours required by engineers in charge. * **Security Concerns:** Concerns regarding security risks due to continuing to use older versions. Since the OSS version requires the company to apply security patches itself, responses are often delayed. * **Server Migration/Replacement:** Consideration of migration destinations due to the aging of on-premises equipment or the termination/switching of contracted VPS or cloud VM services. * **Cloud Migration of Internal Systems:** As part of the SaaS-ification of overall internal systems, there is a desire to entrust the operation of GROWI to an external service.

### Benefits of Migrating to GROWI.cloud

* **Automatic Version Upgrades:** We handle updates to the latest and stable versions. You can always use a stable version. * **Strengthened Security Measures:** Standard provision of unauthorized access countermeasures via WAF and virus scanning. You can significantly reduce the burden of security operations. * **Freedom from Infrastructure Operations:** You can concentrate the man-hours previously spent on infrastructure management—such as server monitoring, troubleshooting, and backups—on core business tasks. * **Reliable Support System:** A dedicated support team will follow up from the migration work to post-operation troubleshooting.

---

Updated Help Documentation

* [Data Migration to GROWI Created on GROWI.cloud](https://growi.cloud/help/ja/cloud/data-migration.html) * [Requesting Migration Work from Support](https://growi.cloud/help/ja/cloud/data-migration/request-to-support.html) * [Migration Using Data Archive/Import Function](https://growi.cloud/help/ja/cloud/data-migration/data-archive-import.html)

Overview of Help Documentation

We provide two methods for migrating data from the OSS version of GROWI to GROWI.cloud. The help pages mentioned above provide more detailed information on estimated costs and work steps for requesting migration work from us.

### 1. Requesting Migration Work from GROWI.cloud Support (Recommended)

* Available regardless of the version of the source GROWI. * We will receive your mongodump data and attached files and perform the restore work ourselves.

### 2. Self-Migration Using Data Archive/Import Function

* A method where you perform the migration work yourself. * Available if the source GROWI has been updated to v7.0.0 or later and meets certain conditions.

---

Migration Track Record and Scope of Support

The GROWI.cloud support team has handled numerous migration projects to date.

We support not only migrations from older versions of GROWI and various data storage locations, but also migrations from knowledge bases other than the OSS version of GROWI.

### Migrations from OSS GROWI

* **Supported Versions:** We have a track record of migrating from older versions prior to the v7 series, such as v3–v6. * **Data Storage:** MongoDB (GridFS), AWS S3, GCP, etc.

Even if the version of your source GROWI is old and it is difficult for you to handle the update, we can handle the update as part of the migration work to GROWI.cloud.

### Migrations from Other Wiki Services

We also have a track record of migrating from internal wiki services other than GROWI, such as Confluence, esa, and Notes. Please feel free to contact us.

---

First, Consult the GROWI.cloud Migration Consultation Tool!

If you are worried about whether you can migrate or don't know what to prepare, please try the AI chat-based GROWI.cloud migration consultation before making an inquiry.

By answering a few questions, you can organize the difficulty level, cost estimate, and information required for your inquiry.

### How to Use

1. Download the .skill file for the GROWI.cloud Migration Consultation and add it to an AI chat tool such as Claude. * You can download the .skill file [here](https://github.com/growilabs/growi-skills/blob/e9dfc184cfa7dd8126ee1131c9ed6f20d93f0602/growi-migration-consultant.skill). 2. Type "I want to consult about a GROWI migration" into the chat to start. 3. The AI will ask about your current environment (GROWI version, construction method, file storage location, etc.) in a conversational format. * Having your current server configuration files on hand will allow for a more accurate diagnosis. 4. Check the diagnostic results and estimated costs. 5. The tool will automatically generate an inquiry text that you can copy and paste into the form!

We support not only migrations from the OSS version of GROWI but also consultations for migrations from other wiki services!

---

Inquiries

For inquiries regarding migration to GROWI.cloud, please contact us via the inquiry form below.

If you would like a specific estimate for migration costs, you can receive a smoother response by checking the updated help pages or using the AI migration diagnostic tool.

Inquiry Form: https://growi.cloud/v2/contact

---

Company Overview

GROWI, Inc. Location: Shinjuku-ku, Tokyo Representative: Yuki Takei, Representative Director Official Website: https://growi.co.jp/

Contact Information Inquiry Form: https://growi.co.jp/contact/

Related Links GROWI Official Website: https://growi.org GROWI.cloud: https://growi.cloud

FACT BOX

  • Source: PR TIMES
  • Category: product_launch