CloudM Archives - Version 2 Limited

Microsoft 365 EWS Retirement: What IT Teams Should Do Before April 2027

Microsoft’s retirement of Exchange Web Services (EWS) is no longer a distant roadmap item. Enforcement has started rolling out across Microsoft 365 tenants, and the service is scheduled to be switched off permanently on 1 April 2027. For organisations using CloudM Migrate for Microsoft 365 projects, that makes migration readiness a task to put on the calendar now.

CloudM’s support update of 30 October 2026 explains that some Microsoft 365 workloads in CloudM Migrate still use EWS. The company is moving those connectors to Microsoft Graph, but that work is not generally available yet. In the meantime, customers need to make sure the CloudM application is permitted to use EWS in each affected tenant.

What is changing with EWS?

Microsoft is moving Exchange Online integrations away from EWS and towards Microsoft Graph. The change is being enforced progressively rather than on one single date for every tenant. From October 2026, Microsoft began setting EWS to disabled in tenants where it had not been explicitly configured. It also introduced an application allow-list model, so simply setting EWS to enabled is no longer enough once enforcement reaches a tenant.

From 1 April 2027, EWS will be fully disabled in Exchange Online. No tenant setting or allow-list entry will keep it working after that date. If a migration project depends on an EWS-based workload, the team needs a tested plan well before the cut-off.

Which CloudM Migrate workloads could be affected?

CloudM says the change affects Microsoft 365 migrations involving mail, calendars, contacts, tasks and notes where the current connector uses EWS. The impact depends on the workloads in scope, the tenant’s EWS configuration and whether the CloudM application registration is already on the relevant allow list.

There is one important detail for IT teams: Microsoft may have created an allow list based on applications that used EWS in the previous 60 days. Apps that are used infrequently, or were created more recently, may not be included automatically. A migration that worked during an earlier test is not proof that every production tenant is ready.

What should Singapore IT teams do now?

Inventory active migration projects. Identify every Microsoft 365 tenant and workload that relies on CloudM Migrate, including mail, calendar, contact, task and note data.
Check the tenant’s EWS settings. Confirm whether Microsoft’s enforcement has reached the tenant and whether an application allow list is in place. Do not rely on the legacy EWS-enabled setting alone.
Allow-list the CloudM application. Follow CloudM’s current guidance to add its Migrate app registration to Microsoft’s EWS allow list for the affected tenant. Have the Microsoft 365 administrator verify the application ID and policy change.
Allow time for the change to take effect. CloudM advises allowing up to 24 hours after updating the allow list before testing the migration again.
Run a representative test. Validate each workload, check data counts and permissions, and confirm that the migration can complete within the planned change window.
Keep the Graph transition on the roadmap. Ask your migration partner to confirm when Microsoft Graph support for the required workloads becomes generally available and what version or configuration will be needed.

Plan migration windows around the deadline

For Singapore organisations, the risk is not just a failed connector. A migration can affect staff access, project deadlines and business operations, especially when email and collaboration data are being moved between tenants. Build the EWS check into the project plan, schedule a test before the production cutover, and make sure the Microsoft 365 owner and migration partner agree on who is responsible for the allow-list change.

It is also worth checking how the migration handles data governance. Confirm where migration data is processed, who can access it, how temporary copies are protected and how exceptions are recorded. These questions matter for organisations handling personal data, confidential customer information or regulated business records under Singapore’s PDPA and internal security policies.

Do not leave the check until the final cut-off

CloudM’s guidance gives customers an interim way to keep affected migrations running while its Microsoft Graph work progresses. That is useful, but it should not become a reason to postpone planning. Tenant-by-tenant enforcement has already begun, and the April 2027 retirement date is fixed.

If your organisation is planning a Microsoft 365 migration, ask your IT team or CloudM partner to review the EWS dependency now. A short compatibility check, allow-list review and controlled test can help prevent a last-minute disruption when the migration window matters most.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.

About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

CloudM 2026

Scaling Google Drive Management: 7 Admin Best Practices

Scaling Google Drive Management: 7 Admin Best Practices

Google Drive’s frictionless user experience is its greatest asset—and an administrator’s primary challenge. Employees instantly spin up Shared Drives, invite external contractors, and distribute public links to maintain operational speed. However, as your organization scales from a handful of Drives to hundreds, this unchecked organic growth inevitably leads to orphaned data, lingering external access, and governance blind spots. While Google Workspace provides robust native controls for basic administration, managing enterprise-scale sprawl requires a pivot from manual oversight to systemic visibility and bulk execution. Here are seven strategies to secure and streamline your Google Drive environment.

1 Establish Comprehensive Visibility

Effective governance requires an accurate inventory. Relying on piecemeal data is insufficient when managing hundreds of Drives. Administrators must establish a centralized view answering critical baseline questions:

Who are the designated managers for each Shared Drive?
What is the total membership count, and which Organizational Units (OUs) are involved?
Are active public links or external members present?
What is the total data footprint?

Instead of manually clicking through hundreds of native console menus, tools like Drive Management for Automate & Protect aggregate this telemetry into a single, filterable dashboard, allowing IT to instantly isolate high-risk environments.

2 Remediate Orphaned Shared Drives

Unmanaged Shared Drives materialize easily—projects wrap up, managers depart, and ownership is never transferred. These orphaned repositories become security liabilities, harboring outdated policies, duplicate content, and forgotten external access. The challenge is not whether you can fix them, but how rapidly you can identify them. Utilizing Drive Management, administrators can filter exclusively for manager-less Drives and rapidly execute a remediation plan: assign new leadership, audit legacy access, migrate relevant data to active OUs, or permanently delete obsolete containers.

3 Audit External Exposure

External collaboration is essential, but lingering access is a vulnerability. Permissions granted for a specific project six months ago rarely remain necessary today. Regular audits must scrutinize public-facing files and third-party collaborators to ensure access aligns with current security postures. Centralized management layers surface these external metrics instantly, transforming a complex forensic hunt into a straightforward administrative review.

4 Enforce Granular Permissions (Beyond Membership)

Membership does not equal appropriate access. Within Shared Drives, roles dictate capability—ranging from full managerial control to restricted view-only access. Audits must evaluate:

Whether current access tiers are overly permissive.
If external users hold rights exceeding their requirements.
Whether sensitive financial, HR, or proprietary data folders have bypassed intended sharing restrictions.

5 Govern Individual “My Drives”

While Shared Drives dominate governance discussions, critical corporate IP frequently accumulates in personal “My Drives.” When an employee departs, IT inherits a visibility crisis. Administrators must determine what files exist, who relies on them, and what has been exposed externally. Through Automate & Protect, admins gain direct visibility into user Drives without requiring account impersonation. You can search files, filter by external link status, manage access, and selectively transfer critical assets to active personnel, bypassing Google’s limitation on transferring entire folder structures simultaneously.

6 Standardize Drive Cleanup in Offboarding

Employee offboarding triggers cascading Drive complications. The most secure approach is integrating Drive review directly into a standardized, repeatable offboarding workflow. By utilizing automated workflows, IT can programmatically review ownership, revoke unauthorized sharing, transfer vital assets, and deploy Backup or Archive protocols to secure the departing user’s data.

7 Execute Bulk Operations

Google’s native controls excel at surgical, one-off fixes. They fail when executing identical policy changes across fifty different Shared Drives. Manual repetition is slow and breeds configuration drift. At scale, efficiency demands bulk action capabilities. Whether updating sharing restrictions, modifying organizational placement, or cleaning up defunct environments, applying changes programmatically across multiple Drives ensures strict consistency and reclaims valuable IT hours.

The Bottom Line: When Native Controls Fall Short
For smaller organizations, native Google Workspace controls suffice. However, enterprise complexity necessitates specialized tooling. Drive Management for Automate & Protect centralizes oversight of both Shared Drives and individual My Drives, integrating seamlessly with Backup, Archive, and Workflow systems. By elevating Drive governance from a siloed task to a core component of your overarching IT strategy, you can confidently scale your operations without sacrificing security.

CloudM 2026

Navigating Data Privacy Compliance in Retail with Google Workspace

How Retailers Can Master Data Privacy Compliance Using Google Workspace

The Core Challenge: Retailers handle massive volumes of sensitive data. However, the real compliance hurdle isn’t just the sheer amount of data—it’s the chaotic operational environment. High turnover, seasonal hiring, and shared devices create security gaps that platforms like Google Workspace cannot automatically seal on their own.

Modern retail is fundamentally data-driven. A typical mid-sized operation processes thousands of daily transactions, manages vast loyalty programs, and executes regional email marketing campaigns. Every single point of contact with customer data brings strict regulatory obligations. To successfully navigate data privacy in retail, IT teams must first understand where risks hide within a typical Google Workspace setup. By recognizing the practical fallout of unmanaged gaps, organizations can transition from reactive troubleshooting to proactive, policy-driven governance.

The Retail Compliance Battlefield

For retailers operating in the UK and EU, the General Data Protection Regulation (GDPR) dictates the rules, wielding potential fines of up to €20 million or 4% of global annual turnover. In 2023 alone, the Information Commissioner’s Office (ICO) levied over £10 million in penalties, frequently citing failures in data access controls and inadequate data retention. Furthermore, merchants accepting card payments must comply with PCI-DSS, which demands rigorous access management around cardholder data. The primary issue for retail IT directors isn’t ignorance of these laws; it’s the difficulty of executing them at scale. When IT and compliance teams are stretched thin by rapid hiring cycles, new store launches, and holiday rushes, manual compliance processes inevitably break down. Google Workspace is a popular choice for retail IT to manage users, communications, and files. Building a defensible security posture requires a clear understanding of both what the platform can do natively—and where it falls short.

Where Google Workspace Shines Natively

When configured correctly, Google Workspace offers a robust technical baseline for compliance. Key native features include:

Encryption: Data is encrypted both in transit and at rest across Gmail, Drive, and other services, protecting customer records and internal HR files.
Data Loss Prevention (DLP): Configurable rules can detect and prevent the unauthorized outbound sharing of sensitive information, like customer lists or payment details.
Multi-Factor Authentication (MFA): Enforcing MFA significantly reduces the risk of compromised credentials—a critical safeguard in high-turnover sectors where maintaining account hygiene is challenging.

While crucial, these features primarily address the platform’s security layer. They do not govern the messy, day-to-day operational processes that dictate whether compliance is actually maintained. This operational disconnect is where most retail compliance failures take root.

Operational Blind Spots in Retail Workspace Environments

Unlike a static corporate office, a retail environment is highly fluid. The following scenarios highlight real-world compliance risks that Google Workspace’s native tools cannot reliably prevent without additional help.

1. The Seasonal Surge and Sloppy Offboarding

Consider a national chain hiring 300 temporary workers for the holiday season, creating 300 new Workspace accounts. Come January, every single account must be suspended, access revoked, and data transferred or deleted according to retention policies. If even 10% of these offboarding tasks are delayed because they rely on a store manager manually raising an IT ticket, 30 former employees still have live access to customer data. Under GDPR Article 5, this is a clear data minimization failure.

2. The Shared Device Dilemma

Shop floor staff frequently access Google Workspace via shared tablets or point-of-sale systems. When shifts change or a device is handed off, tracking exactly whose credentials are active—and what data they can view—becomes a major compliance headache. Without automated session management and strict role-based permissions, shared devices represent a persistent vulnerability in access control.

3. Scope Creep and Stale Permissions

Retail hierarchies involve regional managers, store managers, and team leads, each requiring specific access levels to HR, scheduling, and customer data. Without regular audits, access permissions inevitably drift. A promoted store manager might retain access to a regional HR folder, or a team lead might still have customer data from an old marketing campaign. GDPR demands that access be limited to what is strictly necessary; manual permission reviews rarely keep up with reality.

4. Hoarding Customer Data

Customer emails from a past holiday campaign, loyalty data from a shuttered location, or old transaction records create massive liability if left lingering in Google Drive or Gmail archives. Without automated data retention and deletion policies, this information silently accumulates, inflating compliance risk and expanding the blast radius of any potential data breach.

The Shift to Automated Governance

The common denominator in these retail risks is the reliance on manual processes. Checklists, ticketing systems, and periodic manual audits simply do not scale to the speed and complexity of retail operations. Human error isn’t an anomaly here; it’s a guaranteed result of asking an overloaded IT team to manually police a highly dynamic workforce. Retail IT teams require policy-driven automation that enforces compliance controls consistently, 365 days a year. Practically, this looks like:

Zero-Touch Offboarding: Workflows that trigger instantly when a contract ends, automatically revoking access, suspending the account, and transferring data ownership without requiring IT to lift a finger.
Automated Data Retention: “Set-and-forget” policies that automatically delete archived data after a predefined period, ensuring GDPR compliance without manual reviews.
Granular Backup and Recovery: Solutions that extend beyond Google’s native capabilities, allowing IT to rapidly restore individual files, user accounts, or specific datasets following an accidental deletion or security incident.

Close the Compliance Gap with CloudM

CloudM is specifically engineered to solve the complex data privacy challenges inherent to retail businesses by replacing manual interventions with automated governance policies. For retail IT, CloudM provides onboarding and offboarding workflows featuring over 30 configurable, automated steps—including instant access revocation and data transfer. CloudM’s Smart Teams feature allows IT to dynamically group users by store location, department, or seniority level, far exceeding Google’s standard Organizational Units. This ensures permissions and policies are applied consistently across complex, multi-site operations. Furthermore, backup policies are automatically assigned to new users from day one. For Data Protection Officers (DPOs) and compliance managers, CloudM delivers the essential “set-and-forget” archiving and retention tools required by modern regulations. Data is held for the requisite period and then automatically purged. Comprehensive audit trails are maintained, streamlining regulatory reporting and subject access requests. Crucially, CloudM empowers retailers to host backups on their own infrastructure, rather than routing data through third-party servers, ensuring the data sovereignty increasingly mandated by privacy laws. If your retail organization is still relying on manual processes to manage Google Workspace compliance, a breach or violation is merely a matter of time. Discover how CloudM can build a resilient compliance posture that withstands the pressures of retail operations. Get started with CloudM today.

CloudM 2026

Retail Compliance Governance: Google Workspace Architecture

Retail environments run on high-velocity data. However, the true compliance risk vector isn’t data volume—it is the structural volatility of the retail workforce. High employee turnover, massive seasonal hiring surges, and shared shop-floor endpoints create severe data exposure risks that standard cloud suites are not naturally designed to manage automatically.

Regulatory Mandate: Under GDPR frameworks, organizations face administrative penalties up to €20 million or 4% of global annual turnover for data governance failures. Concurrently, cardholder data environments must strictly satisfy the explicit access containment rules defined by PCI-DSS.

Systemic Operational Gaps in Retail Configurations

While Google Workspace provides baseline encryption and data loss prevention (DLP) templates, manual administration cannot reliably protect against the operational friction unique to retail chains:

1. High-Volume Offboarding Delays

Onboarding hundreds of holiday temporary workers creates a severe operational deficit when contracts terminate simultaneously. If account de-provisioning relies on manual IT ticketing systems, orphan accounts remain active for days, allowing former staff unauthorized entry into repositories containing sensitive customer metadata.

2. Endpoint Sharing Anonymity

Shop-floor tablets and point-of-sale stations are continually passed between users mid-shift. Without automated session termination and role-based permissions tied dynamically to the active user profile, true forensic accountability and access logging become impossible.

3. Intradepartmental Permission Drift

Frequent store-level re-organizations introduce role creep. When supervisors change locations or responsibilities, legacy access rights to regional shared drives or HR folders are rarely purged cleanly, violating the fundamental security principle of least privilege.

Operational Matrix: Infrastructure Control Comparison

Control Vector	Manual Ticketing / Standard Workspace	Automated Governance Layer
User Offboarding	Prone to administrative delays; risks inactive orphan account exposure.	Instantaneous, trigger-driven de-provisioning and policy-enforced data migration.
Workforce Grouping	Static, manual Organizational Units (OUs) that fail to scale.	Dynamic synchronization based on active store geolocation, role, and seniority tier.
Data Retention	Relies on user compliance; risks stale data liability accumulation.	Set-and-forget deletion protocols matching specific regulatory retention lifecycles.

Enforcing Absolute Compliance with CloudM

Manual checklists and periodic internal audits do not scale to match the velocity of modern retail operations. CloudM replaces manual administrative drag with structured, programmatic lifecycle automation.

Automated De-Provisioning: Executes a comprehensive sequence of over 30 customizable lifecycle steps to immediately restrict access, suspend accounts, and relocate data ownership upon contract conclusion.
Smart Teams Orchestration: Dynamically groups staff across distributed locations automatically, ensuring appropriate access rights are calculated dynamically based on real-time organizational roles.
Defensible Data Sovereignty: Enables compliance teams to manage retention workflows silently and host secure backups inside their own infrastructure, eliminating third-party routing risks.

Do not wait for an operational failure to reveal an access control gap. Secure your Google Workspace infrastructure today with CloudM.

CloudM 2026

Google Workspace Domain Switch Migration Strategy

Executing a domain switch within Google Workspace is a structural operation. Unlike standard migrations, the domain identity must be released from one tenant and captured by another in real-time. This requires a zero-latency execution path.

The Architectural Pivot: Because a domain cannot exist in two Workspace instances at once, identities must be temporarily re-homed to allow the domain to be released and re-verified at the destination.

The 6-Phase Execution Roadmap

Bulk Ingestion: Migrate data from the source to a staging domain at the destination to minimize cutover volume.
Identity Stripping: Use GAM to rename all source users off the primary domain onto a temporary secondary domain.
The Domain Capture: Release the primary domain from the source and immediately verify it at the destination.
Final Alignment: Rename destination users from staging addresses to their permanent primary domain identities.
MX Cutover & Delta: Update mail routing and run a final delta sync to capture the last remaining messages.
Safety Buffer: Maintain the source tenant for 30 days as a read-only safety net before final decommissioning.

Warning: “Domain in Use” errors are usually caused by a single forgotten alias or group. Automated auditing of the source environment is critical.

CloudM 2026

Product release: Improve your compliance posture with CloudM Archive 2.7

Product Update

CloudM Archive 2.7 Release

Introducing Google Chat Archiving and Progressive Search Enhancements

We are excited to announce the release of CloudM Archive 2.7. This update is designed to help organizations better manage their digital footprints, ensure legal compliance, and reduce storage costs across the Google Workspace ecosystem.

The Headline: Google Chat Archiving

As remote and hybrid work continues to dominate, the volume of data generated in Google Chat has skyrocketed. Version 2.7 now allows administrators to seamlessly archive Google Chat messages, including 1-to-1 conversations, group chats, and Spaces.

Retention Compliance: Meet legal requirements by storing chat history outside of the active production environment.
Metadata Preservation: Archive messages along with timestamps, sender details, and attachments.
Cost Efficiency: Move aging chat data to low-cost storage without losing searchability.

What’s New in Archive 2.7?

Progressive Search

We've optimized our search engine to be faster and more intuitive. Find specific archived items across Drive, Gmail, and now Chat with improved filtering and reduced latency.

Enhanced Security

Improved auditing logs and granular permissions ensure that only authorized personnel can view or restore sensitive archived chat data.

Refined UI

A refreshed dashboard view provides a clearer overview of your storage savings and archive health at a glance.

Improved API Access

Developers can now leverage updated API endpoints to integrate CloudM Archive data with third-party eDiscovery or analytics tools more effectively.

Why Use CloudM Archive?

CloudM Archive remains the leading solution for businesses looking to optimize their Google Workspace tenant. By moving data to your own cloud storage (GCP, Azure, or AWS), you maintain total ownership and control over your data while significantly reducing the "license bloat" associated with keeping ex-employees' data active just for retention purposes.

Seamless Migration Integration

As always, CloudM Archive works hand-in-hand with CloudM Migrate. When offboarding an employee, you can automatically trigger an archive process that clears their active license while preserving every file and chat for future reference.

CloudM 2026

CloudM Launches a New ROI Calculator: How Much Can You Save?

Product News

CloudM Launches Interactive Google Workspace ROI Calculator

CloudM has officially released a new interactive ROI Calculator designed to help IT leaders and financial decision-makers quantify the potential savings and efficiency gains of using the CloudM platform within their Google Workspace environment.

Why an ROI Calculator?

Managing Google Workspace at scale involves significant manual effort in offboarding, data migration, and archive management. Many organizations struggle to visualize the "hidden costs" of these manual processes. The CloudM ROI Calculator bridges this gap by providing data-driven insights tailored to your specific organization size and IT complexity.

Quantifying IT Efficiency

The calculator focuses on several key areas where CloudM significantly impacts the bottom line:

Automated Offboarding: Calculate hours saved by automating the 20+ steps typically required to offboard a user securely.
License Optimization: Visualize the savings achieved by moving ex-employee data to CloudM Archive rather than paying for active Google Workspace licenses.
Data Migration: Estimate the reduction in project costs and time when migrating large volumes of data.
IT Admin Productivity: See how centralizing management into a single pane of glass reduces ticket resolution times.

75% Faster Offboarding

50% License Cost Reduction

100% Data Compliance

How the Calculator Works

The tool is simple and intuitive. Users input a few basic data points, such as:

Total number of Google Workspace users.
Average number of monthly leavers (offboarding events).
Current cost of IT admin time.
Storage requirements for archived data.

The calculator then generates a comprehensive report detailing your Estimated Annual Savings and the Payback Period for your CloudM investment.

Empowering IT Leaders

This tool is more than just a marketing asset; it is a business case builder. IT Managers can use these personalized reports to justify budget requests and demonstrate the strategic value of IT automation to the C-suite.

CloudM 2026

CloudM recognized as a High Performer in G2 Fall 2025 Cloud Migration Report

Product Update

CloudM Archive 2.7 Release

Introducing Google Chat Archiving and Progressive Search Enhancements

The Headline: Google Chat Archiving

Retention Compliance: Meet legal requirements by storing chat history outside of the active production environment.
Metadata Preservation: Archive messages along with timestamps, sender details, and attachments.
Cost Efficiency: Move aging chat data to low-cost storage without losing searchability.

What’s New in Archive 2.7?

Progressive Search

We've optimized our search engine to be faster and more intuitive. Find specific archived items across Drive, Gmail, and now Chat with improved filtering and reduced latency.

Enhanced Security

Improved auditing logs and granular permissions ensure that only authorized personnel can view or restore sensitive archived chat data.

Refined UI

A refreshed dashboard view provides a clearer overview of your storage savings and archive health at a glance.

Improved API Access

Developers can now leverage updated API endpoints to integrate CloudM Archive data with third-party eDiscovery or analytics tools more effectively.

Why Use CloudM Archive?

Seamless Migration Integration

CloudM 2026

CloudM Migrate 4.5: Google Chat and Spaces migrations have just become easier

As organizations increasingly rely on Google Chat and Spaces for real-time collaboration, migrating this critical data between Google Workspace tenants has been a persistent industry challenge. Today, that changes.

CloudM is proud to introduce Migrate 4.5, a significant update engineered to solve this problem. This release delivers comprehensive support for migrating Google Chat direct messages and Spaces, ensuring that no conversation is left behind.

Seamless Tenant-to-Tenant Google Chat & Spaces Migration

CloudM Migrate now fully supports the migration of all Google Chat and Spaces data in tenant-to-tenant scenarios. This includes direct messages (both 1-to-1 and group chats) and collaborative Spaces, allowing you to seamlessly transfer your team’s complete communication history to a new domain.

Key Migration Capabilities for Spaces Include:

All messages within a Space conversation
Replies organized in message threads
Attachments from all users (both migrating and non-migrating)
Formatting such as unordered and nested lists
GIFs, reactions, and custom emojis
Quoted messages

This ensures a high-fidelity migration that preserves the context and integrity of your team’s collaborative work.

Additional Enhancements in Version 4.5

1. Improved Visibility for Document Migrations

To provide clearer and more accurate reporting, Document Folders are now tracked as a separate item in the migration progress dashboard. This offers more granular insight into your project, distinct from the general “Documents” count.

2. Expanded Support for Microsoft Teams to Chat Migrations

For organizations moving from Microsoft Teams to Google Chat, Migrate 4.5 now includes full support for migrating attachments from private and shared channels, including content shared by non-migrating users.

Get Started

Cloud data migration should be a straightforward process, not a complex obstacle. With CloudM Migrate 4.5, we are making it easier than ever to move your most valuable collaboration data with confidence.

CloudM 2025

August 2025 Product Release: CloudM Backup and Automate Updates

August 2025 Release: Introducing Google Chat Backup & Advanced Automation Features

Our August 2025 release is here, bringing critical new data protection capabilities and powerful administrative enhancements to your Google Workspace environment.

CloudM Backup 1.10 introduces highly-requested support for Google Chat, ensuring your vital conversations are protected from data loss. Simultaneously, CloudM Automate 2.17 delivers major upgrades to email signature management, domain notifications, and user lifecycle workflows.

CloudM Backup 1.10: Secure Your Google Chat Conversations

As tools like Google Chat become central to team collaboration, the data within them becomes a critical business asset. Accidental deletion or malicious activity can disrupt workflows and lead to the permanent loss of important information.

To address this, CloudM Backup now extends its comprehensive protection to Google Chat. This update allows you to securely back up and quickly restore:

1-to-1 direct messages
Group direct messages
Reactions, links, and file attachments within conversations

This new capability integrates seamlessly with our existing protection for Gmail, Google Drive, Shared Drives, Calendar, and Contacts, providing a more complete data safety net for your entire Google Workspace.

CloudM Automate 2.17: More Flexibility and Control

This release introduces several powerful new features and enhancements to streamline your administrative tasks.

Dynamic Email Signatures for Multiple Roles

One of our most requested features is now a reality. Administrators can now create and assign multiple email signatures to a single user. The secondary “alias” signature is applied dynamically based on which email address the user is sending from, making it perfect for individuals with different roles or group memberships.

Accelerated Email Signature Sync

We’ve significantly reduced the sync time between CloudM and your Google Domain. Now, any updates made to email signatures are reflected for your users within minutes, ensuring brand consistency and timely changes.

Streamlined Domain Notifications

We have redesigned the Domain Settings page to give you more granular control over notifications. The opt-in process is now simpler, and it’s easier to select the specific types of notifications you want to receive, reducing noise and highlighting important alerts.

Flexible Google Calendar Transfers

To reduce manual work during user transitions, we’ve introduced more flexible modes for transferring calendars. This gives administrators greater control over how calendars, invites, and events are migrated to a new user, simplifying the offboarding process.

CloudM 2025