Migrate email data from one Google Workspace account to another, available in open beta

What’s changing

Beginning today, a new data migration experience is available: you can migrate your users’ email data from one Google Workspace account to another in a more reliable and efficient manner. You can configure your data migration for up to 100 users at a time and also run delta migrations, which smartly brings over any newly generated data from the source without duplicating previously migrated content.

This feature is available as an open beta, which means admins can use it without enrolling in a specific beta program.


Additional details

You can find more information in our Help Center about migrating other forms of data from different types of source accounts.

Getting started

  • Admins: Visit The Help Center to learn more about the new data migration service and migrating email.
  • End users: There is no end user action required


Rollout pace

  • This feature is available now in open beta.

    Availability

    • Available to Google Workspace Business Starter, Business Standard, and Business Plus; Enterprise Standard and Enterprise Plus; Education Fundamentals, Education Standard, Teaching and Learning Upgrade, and Education Plus; Essentials Starter, Essentials, Enterprise Essentials, and Enterprise Essentials Plus, and Nonprofits customers

      Resources

        What web creators should know about our March 2024 core update and new spam policies

        Today we announced the March 2024 core update. This is designed to improve the quality of Search by showing less content that feels like it was made to attract clicks, and more content that people find useful. We also shared that we have new spam policies to better handle the practices that can negatively impact Google's search results. In this post, we'll go into more detail for creators about both the update and the spam policies.

        Embracing Android 14: Meta’s Early Adoption Empowered Enhanced User Experience

        Posted by Terence Zhang – Developer Relations Engineer, Google; in partnership with Tina Ho - Partner Engineering, TPM and Kun Wang – Partner Engineering, Partner Engineer

        With the first Developer Preview of Android 15 now released, another new Android release that brings new features and under-the-hood improvements for billions of users worldwide will be coming shortly. As Android developers, you are key players in this evolution; by staying on top of the targetSDK upgrade cycle, you are making sure that your users have the best possible experience.

        The way Meta, the parent company of Instagram, Facebook, WhatsApp, and Messenger, approached Android 14 provides a blueprint for both developer success and user satisfaction. Meta improved their velocity towards targetSDK adoption by 4x, and so to understand more about how they built this, we spoke to the team at Meta, with an eye towards insights that all developers could build into their testing programs.

        Meta’s journey on A14: A blueprint for faster adoption

        When Android 11 launched, some of Meta’s apps experienced challenges with existing features, such as Chat Heads, and with new requirements, like scoped storage integration. Fixing these issues was complicated by slow developer tooling adoption and a decentralized app strategy. This experience motivated Meta to create an internal Android OS Readiness Program which focuses on prioritizing early and thorough testing throughout the Android release window and accelerating their apps’ targetSDK adoption.

        The program officially launched last year. By compiling apps against each Android 14 beta and conducting thorough automated and smoke tests to proactively identify potential issues, Meta was able to seamlessly adopt new Android 14 features, like Foreground Service types and send timely feedback and bug reports to the Android team, contributing to improvements in the OS.

        Meta also accelerated their targetSDK adoption for Android 14—updating Messenger, Facebook, and Instagram within one to two months of the AOSP release, compared to seven to nine months for Android 12 (an increase of velocity of more than 4x!). Meta’s newly created readiness program unlocked this achievement by working across each app to adopt latest Android changes while still maintaining compatibility. For example, by automating and simplifying their SDK release process, Meta was able to cut rollout time from three weeks to under three hours, enhancing cooperation between individual app teams by providing immediate access to the latest SDKs and allowing for rapid testing of new OS features. The centralized approach also meant Threads adopted Android 14 support quickly despite the fast-growing new app being supported by a minimal team.

        Reaping the rewards: The impact on users

        Meta's early targetSDK adoption strategy delivers significant benefits for users as well. Here's how:

          • Improved reliability and compatibility: Early adoption of Android previews and betas prevented surprises near the OS launch, guaranteeing a smooth day-one experience for users upgrading to the latest Android version. For example, with partial media permissions, Meta's extensive experimentation with permission flows ensured “users felt informed about the change and in control over their privacy settings,” while maximizing the app's media-sharing functionality.

          • Robust experimentation with new release features: Early Android release adoption gave Meta ample time to collaborate across privacy, design, and content strategy teams, enabling them to thoughtfully integrate the new Android features that come with every release. This enhanced the collaboration on other features, allowing Meta to roll out Ultra HDR image experience on Instagram within 3 months of platform release in an “Android first” manner is a great example of this, delighting users with brighter and richer colors with a higher dynamic range in their Instagram posts and stories.
        Meta's adoption of Ultra HDR in Android 14 brings brighter colors and dynamic range to Instagram posts and stories.
        Meta's adoption of Ultra HDR in Android 14 brings brighter colors and dynamic range to Instagram posts and stories.

        Embrace the latest Android versions

        Meta's journey highlights the compelling reasons for Android developers to adopt a similar forward-thinking mindset in working with the Android betas:

          • Test your apps early: Anticipate Android OS changes, ensuring your apps are prepared for the latest target SDK as soon as they become available to create a seamless transition for users who update to the newest Android version.

          • Utilize latest tools to optimize user experience: Test your apps thoroughly against each beta to identify and address any potential issues. Check the Android Studio Upgrade Assistant to highlight major breaking changes in each targetSDKVersion, and integrate the compatibility framework tool into your testing process to help uncover potential app issues in the new OS version.

          • Collaborate with Google: Provide your valuable feedback and bug reports using the Google issue tracker to contribute directly to the improvement of the Android ecosystem.

        We encourage you to take full advantage of the Android Developer Previews & Betas program, starting with the newly-released Android 15 Developer Preview 1.

        The team behind the success

        A big thank you to the entire Meta team for their collaboration in Android 14 and in writing this blog! We’d especially like to recognize the following folks from Meta for their outstanding contributions in establishing a culture of early adoption:

          • Tushar Varshney - Partner Engineering, Partner Engineer
          • Allen Bae - Partner Engineering, EM
          • Abel Del Pino - Facebook, SWE
          • Matias Hanco - Facebook, SWE
          • Summer Kitahara - Instagram, SWE
          • Tom Rozanski - Messenger, SWE
          • Ashish Gupta - WhatsApp, SWE
          • Daniel Hill - Mobile Infra, SWE
          • Jason Tang - Facebook, SWE
          • Jane Li - Meta Quest, SWE

        Secure by Design: Google’s Perspective on Memory Safety

        Alex Rebert, Software Engineer, Christoph Kern, Principal Engineer, Security Foundations


        Google’s Project Zero reports that memory safety vulnerabilities—security defects caused by subtle coding errors related to how a program accesses memory—have been "the standard for attacking software for the last few decades and it’s still how attackers are having success". Their analysis shows two thirds of 0-day exploits detected in the wild used memory corruption vulnerabilities. Despite substantial investments to improve memory-unsafe languages, those vulnerabilities continue to top the most commonly exploited vulnerability classes.


        In this post, we share our perspective on memory safety in a comprehensive whitepaper. This paper delves into the data, challenges of tackling memory unsafety, and discusses possible approaches for achieving memory safety and their tradeoffs. We'll also highlight our commitments towards implementing several of the solutions outlined in the whitepaper, most recently with a $1,000,000 grant to the Rust Foundation, thereby advancing the development of a robust memory-safe ecosystem.


        Why we’re publishing this now

        2022 marked the 50th anniversary of memory safety vulnerabilities. Since then, memory safety risks have grown more obvious. Like others', Google's internal vulnerability data and research show that memory safety bugs are widespread and one of the leading causes of vulnerabilities in memory-unsafe codebases. Those vulnerabilities endanger end users, our industry, and the broader society. We're encouraged to see governments also taking this issue seriously, as with the U.S. Office of the National Cyber Director publication of a paper on the topic last week.


        By sharing our insights and experiences, we hope to inspire the broader community and industry to adopt memory-safe practices and technologies, ultimately making technology safer.


        Our perspective

        At Google, we have decades of experience addressing, at scale, large classes of vulnerabilities that were once similarly prevalent as memory safety issues. Our approach, which we call “Safe Coding”, treats vulnerability-prone coding constructs  themselves as hazards (i.e., independently of, and in addition to, the vulnerability they might cause), and is centered around ensuring developers do not encounter such hazards during regular coding practice.


        Based on this experience, we expect that high assurance memory safety can only be achieved via a Secure-by-Design approach centered around comprehensive adoption of languages with rigorous memory safety guarantees. As a consequence, we are considering a gradual transition towards memory-safe languages like Java, Go, and Rust.


        Over the past decades, in addition to large Java and Go memory-safe codebases, Google has developed and accumulated hundreds of millions of lines of C++ code that is in active use and under active, ongoing development. This very large existing codebase results in significant challenges for a transition to memory safety:


        • We see no realistic path for an evolution of C++ into a language with rigorous memory safety guarantees that include temporal safety.

        • A large-scale rewrite of all existing C++ code into a different, memory-safe language appears very difficult and will likely remain impractical.




        We consider it important to complement a transition to memory safe languages for new code and particularly at-risk components with safety improvements for existing C++ code, to the extent practicable. We believe that substantial improvements can be achieved through an incremental transition to a partially-memory-safe C++ language subset, augmented with hardware security features when available. For instance, see our work improving spatial safety in GCP's networking stack.


        Our investments in memory-safe languages

        We are actively investing in many of the solutions outlined in our whitepaper and in our response to the US Federal Government’s RFI on Open Source Software Security.


        • Android has written several components in Rust over the last few years, leading to compelling security improvements. In Android’s Ultra-wideband (UWB) module, this has improved the security of the module while also reducing the memory usage and inter-procedural calls. 


        • Chrome has started shipping some features in Rust; in one case, Chrome was able to move its QR code generator out of a sandbox by adopting a new memory-safe library written in Rust, leading to both better security and better performance.


        • Google recently announced a $1,000,000 grant to the Rust foundation to enhance interoperability with C++ code. This will facilitate incremental adoption of Rust in existing memory-unsafe code bases, which will be key to enabling even more new development to occur in a memory-safe language. Relatedly, we are also working on addressing cross-language attacks that can occur when mixing Rust and C++ in the same binary.



        We know that memory safe languages will not address every security bug, but just as our efforts to eliminate XSS attacks through tooling showed, removing large classes of exploits both directly benefits consumers of software and allows us to move our focus to addressing further classes of security vulnerabilities.


        To access the full whitepaper and learn more about Google's perspective on memory safety, visit https://research.google/pubs/secure-by-design-googles-perspective-on-memory-safety/

        New enhancements in the Space Management Tool For admins: add multiple members or groups, review settings and details

        What’s changing 

        We’re introducing several updates for the Space Management Tool in the Admin console, including an improved user interface and additional management capabilities. We’ve introduced several more ways to manage a single space, including: 
        • Adding multiple members and groups to a space at once 
        • Review detailed space settings 
        • Review invited members

        Space Management Tool for Admins provide visibility into all spaces in an organization




        Groups are now included in the list of Space members


        Admins can now see detailed information regarding space settings, including those defined by space managers, who can access the space, post new messages, and more.



        Admins can now see detailed setting information


        Who’s impacted

        Admins


        Why it’s important

        Spaces in Google Chat are an essential part of collaboration and community building across organizations of all sizes. As such, it’s important for admins to easily view and manage their spaces to keep them productive and safe. This update makes it easier for admins to execute space management tasks and view more information about spaces.


        Finally, you’ll notice that we’ve aligned the look-and-feel of the interface and workflows for individual space management across Google Chat on the web and the Admin console for a more consistent experience.


        Getting started

        Important note: Both Super admins and Delegated admins must have Google Chat turned on for their account in the Google Chat service settings. Visit the Help Center to learn more about turning on Google Chat.