"Our on-premises groupware server is getting old, and we were told maintenance expires next year. We'd like to use this opportunity to move to the cloud, but we have no idea what or how to migrate." We have seen an influx of such inquiries lately. Frequent complaints like "Sales reps can't check schedules on smartphones while out of the office" or "Younger employees complain the UI is outdated and hard to use" also serve as typical catalysts prompting a switch. Packaged editions of Cybozu Office, desknet's NEO, and proprietary email/groupware hosted on internal servers are undeniably reaching the end of their lifecycle.
In fact, support for the packaged edition of Cybozu Office is scheduled to end on September 30, 2027, and for most companies, license expiration dates will render it unusable even earlier. Once maintenance expires, security vulnerability patches stop, making this something you cannot afford to postpone simply because "it still works." Google Workspace is a compelling migration destination, but there is one fundamental reality to understand first: there is a clear divide between items that map easily, such as email and calendars, and items that cannot be transferred in their existing form, such as bulletin boards and internal approvals. If you proceed without drawing this distinction clearly, the migration will inevitably stall halfway through.
What Migrates Cleanly and What Does Not Transfer Directly
First, sort the features of your legacy groupware into two categories based on ease of migration. Understanding this distinction from the outset makes the entire migration plan much clearer.
The easiest to migrate are email, calendars, address books, and files. These have clear counterparts in Google Workspace—Gmail, Google Calendar, Google Contacts, and Google Drive—allowing for straightforward data mapping. Since these four comprise the core of daily operations, migrating them represents a significant step forward. For migrations from Microsoft 365, standard migration tools within the Admin Console have also matured, and key insights are detailed in our article on migrating from Microsoft 365 to Google Workspace.
On the other hand, bulletin boards, proprietary workflows (internal approvals and application forms), custom business apps, and custom databases do not transfer in their existing form. Domestic Japanese groupware platforms were heavily tailored to bundle everything into a single suite, meaning internal workflows are often deeply dependent on these proprietary features. Because Google Workspace does not offer 1:1 matching capabilities for these, they require redesign rather than simple migration. Assuming that "a migration tool will take care of it somehow" is the most common miscalculation.
The Critical Points in Migration Data Lie in Email and Calendar Details
Even for email and calendars—items that should transfer easily—critical pitfalls can emerge during actual execution.
Historical emails can be imported using Google's new data migration service, provided the legacy server supports IMAP. Administrators connect Workspace to the IMAP server and batch-import up to 100 users at a time using a CSV file containing user email addresses and passwords. However, for legacy environments with IMAP disabled or groupware platforms that only export to proprietary formats, this standard route cannot be used, requiring separate export and conversion measures.
Issues that frequently arise during import include character encoding errors, missing attachments, and broken folder hierarchies. Deep folder structures unique to Japanese groupware and custom flags like "Reply Required" are not replicated as-is in Google, so it is safer to plan on rebuilding them using labels post-migration. For calendars, recurring events (such as weekly regular meetings) and facility reservations may not transfer correctly, making thorough verification in a test migration essential. Furthermore, re-architecting permissions is often overlooked. Access controls from the legacy environment—such as "visible only to this department"—are not included in the migrated data and must be redesigned from scratch as Google Drive sharing settings. These data migration challenges are not unique to groupware, and the perspectives covered in our article on business system data migration apply directly here.
How to Replace Non-Transferable Features
The core challenge is replacing bulletin boards, workflows, and business apps that lack a 1:1 migration path. Broadly speaking, there are three options, chosen according to functional complexity.
The first path is substituting with standard Google Workspace features. Bulletin boards and team announcements can move to Google Chat spaces, while internal approvals and applications can be replaced with native approval features in Google Docs/Sheets, or a combination of Google Forms for intake and Google Sheets as a ledger. The native approval feature is available without extra fees on Business Standard plans and above. While cost-effective, it is not well-suited for complex conditional branching or multi-stage approvals spanning multiple departmental tiers.
The second path is rebuilding with no-code tools like AppSheet. Proprietary databases and simple internal tools can be reconstructed on top of Google Sheets using no-code platforms, delivering mobile compatibility at the same time. This fits middle-tier requirements that feel too constrained by standard features but do not warrant full custom development. For practical build techniques, refer to our article on building business apps with AppSheet.
The third path is custom development for clients. Workflows with intricate conditional branching, core system integrations, or specialized business form generation that cannot be fully handled by standard features or no-code tools are built from scratch according to specific requirements.
| Replacement Destination | Suitable Functions | Primary Constraints |
|---|---|---|
| Standard features (Spaces / Approvals / Forms) | Bulletin boards, simple applications and internal approvals | Struggles with complex branching and multi-stage approvals |
| AppSheet (No-code) | Custom databases, simple business applications | Limits on advanced external integrations and complex processing |
| Custom development for clients | Multi-tier internal approvals, core system integrations, custom form generation | Cost and timeline vary depending on requirements |
In practice, combining these three approaches is the standard strategy. Assign the optimal replacement destination on a per-function basis: bulletin boards to Spaces, expense requests to Forms and Approvals, and only complex internal approvals to custom builds. Because custom development costs vary significantly based on requirements, pricing is provided via individual estimates.
How to Proceed: Starting with an Inventory and a Mapping Matrix
Once the replacement destinations are clear, following this sequence ensures a dependable rollout.
The starting point is a current-state inventory. Catalog which features of the legacy groupware are being used, by whom, and how. This exercise often uncovers bulletin boards that are barely touched or approval processes handled by only one specific person, allowing you to streamline workflows as part of the migration. Next, based on the inventory, build a feature-by-feature mapping matrix. This serves as your migration blueprint: email to Gmail, internal approvals to the approval feature, custom apps to AppSheet, and so on. Without this matrix, you will repeatedly stall during implementation, wondering where each component should go.
After that, avoid an abrupt cutover. Instead, run the legacy environment and Google Workspace in parallel while carrying out a phased migration by department or function. Finally, don't overlook user training. When the user interface changes, employees will inevitably revert to the legacy environment unless operational training and a help desk are in place. If you have concerns about the initial setup on the Google Workspace side, reviewing our Google Workspace Implementation Guide beforehand will give you a solid foundation.
The pitfalls are also clear: big-bang cutover failures (skipping parallel operations to switch the entire company at once, causing issues to cascade company-wide), data retention oversights (discarding historical bulletin board archives without preserving them), and insufficient training (failing to drive adoption because usage practices didn't stick). These three represent classic failure modes. The first priorities to tackle are an inventory of legacy groupware features and establishing priority tiers, such as "email is mandatory / an archive view is sufficient for bulletin boards." Once these are decided, the migration design will naturally take shape.
GleamHub has supported clients across both domains: implementing and driving adoption of Google Workspace, as well as developing no-code solutions and custom software where standard features fall short. If you find yourself asking, "Support for our Japanese groupware is ending soon, but where do we even begin?" or "We don't know how to replace our bulletin boards and internal approvals," please reach out via our Google Workspace and IT Consulting Desk. We will partner with you every step of the way, from legacy feature inventories and target mapping matrices to replacement architecture and user adoption.
Sources
- About the New Data Migration Service － Google Workspace Admin Help
- Migrate Email from IMAP Accounts － Google Workspace Admin Help
- Generally Available: Migrate User Email from Google Workspace, Gmail, and Other IMAP-Enabled Mail Servers － Google Workspace Updates
- Manage Document Approvals － Google Workspace Admin Help
- Notice of End of Sales and Support for Packaged "Cybozu Office" － Cybozu
- How to Create Approval Flows in Google Workspace: What Standard Features Can and Cannot Do － Gluegent
