Google Currents is migrating to Spaces in Google Chat. This article aims to help you prepare by providing details on the migration and upcoming new Spaces features, sharing resources, and answering frequently asked questions.
The goal is to provide a smooth migration experience and to mitigate risk for you and your community members.
If you have any questions that aren’t addressed in this article, please leave a comment below and someone from the Community or Google Workspace team will be happy to help.
The Google Workspace Community came together in February for a live learning and Q&A session on the Google Currents migration to Spaces, led by Google Workspace leaders, Jackson Hsieh, Chelsea Fischbach, and Kristina Nielsen. Check out the recording here and use the time stamps in the YouTube description to jump to the topics you care about most.
Stay up-to-date with the latest information and key dates regarding the transition here.
Currents will be placed in export-only mode beginning July 5, 2023 and all Currents data will be deleted beginning August 8, 2023. We strongly recommend you to export your organization’s Currents data using Google Takeout well ahead of these dates to ensure all data is preserved in the export.
Some organizations need more granular control when exporting their user-generated data. Instead of a complete dataset, these organizations need a subset of user content, such as content generated by a specific department. As an administrator, you can select the organizational unit or group to export data from in one of three ways: by individual user, by entire domain, or by groups or organizational units.
I want to export by… |
Benefits |
Limitations |
|
|
|
|
|
|
(Enterprise Plus Customers Only) |
|
|
See the Takeout guide here.
The following covers the most commonly-asked features of Currents that will NOT be migrated to Spaces. Read further below in the feature comparison table for additional details.
Currents was great for community building, but lacked enterprise-grade admin tools and the ability to quickly create user spaces. With Spaces in Chat, we aim to:
Learn more about what’s possible with Chat here.
The below table provides an overview of key features and capabilities in Google Currents and what the equivalent or difference are in Spaces, including whether it will be part of the migration or not.
See the complete list of Currents to Spaces feature comparisons here.
Currents feature |
Included in migration? |
Spaces feature |
Communities: A group of users with shared interests. Posts in a community are shared with all members in the community. |
Yes |
Space: A space members have access to. Messages in a space are shared with all members of the space. |
Non-Restricted Community: Communities with members from outside your organization. |
Yes |
Space: A space that includes users outside of your organization. Make sure Google Chat has external access enabled in the admin settings. Spaces allows for users from one domain to access a space hosted on a separate domain. These are guests. If you have a non-restricted community, the community is migrated to a space with this feature only if external access is turned on for Chat. If not, your external users won’t be able to access the migrated space. To ensure that external spaces are active, read Set external chat options. |
Shared Community: A community with owners from multiple domains. |
No |
No complementary feature: Spaces doesn’t allow users from external domains, called guests, to be Space managers. Spaces has support for communities with multiple managers, but it doesn't allow multiple managers to be from different domains. If you have a community that’s shared with multiple owners from different domains, you need to decide which domain the migrated space will be sent to. |
Community settings: Private—Only invited members can access the community’s content. |
Yes |
Restricted space: Undiscoverable spaces to which only users who are directly added or invited have access to. Private is a setting for communities. A private community is one that only select users can access. During migration, these communities become restricted spaces, to which only select users have access. For details, see Use Spaces in Google Workspace. |
Community settings: Domain visible—All members in the domain can access the community’s content. |
No |
Restricted space: Only directly added or invited users can access the space’s content. During migration, these communities become restricted spaces. You can convert the space to a discoverable space post migration. For details, see Use Spaces in Google Workspace. |
Community settings: Ask to join—Whether users must ask to join a community. |
No |
No complementary feature |
Community notification settings: Where and how often a user is notified when a community is updated. |
Yes |
Space notification: Communities with notifications enabled will have the default space setting set to Following. |
Community content control settings: Controls if posts should be held for review, or have stronger content filters and controls |
No |
No complementary feature |
Community settings: Hold post for review—Whether members can post directly in the community. If restricted, moderators review and publish posts submitted by members. |
No |
No complementary feature. The community will be migrated to a Space where all members will be allowed to post and engage with content. |
Community members: The members of a community. |
Yes |
Space members: The members of a space. Members of a space from the domain the space exists in are users, while members from outside of the space’s domain are guests. |
Community groups: A group of users who are a part of a community. |
Yes |
Space members: A group of users in Currents will be added as individual members in a space. External members will become guests. |
Community owners: The owners who control the community. |
Yes |
Space managers: The managers who control the space. |
Community moderators: A unique member of a community who moderates post content in the community, but isn’t an owner. |
No |
No complementary feature: Community moderators will be migrated as members of the space. |
Archived, abusive, and banned users: Users who don’t have access to Currents. Archived users are archived by admins, abusive users are removed by Currents automatically, and banned users are removed from Currents by admins. |
No |
No complementary feature: Archived and abusive users will not be migrated. Banned users will be migrated, but banned users will have access to spaces that aren’t private. |
Post: A post made in Currents with replies and likes. |
Yes |
Inline thread: A comment thread with replies and reactions. If there are more than 200 replies on a comment thread, only the first 200 replies will be migrated. |
Categories: Topics of discussion within a community that a post can be a part of. |
No |
No complementary feature |
Reshared post: A post by another user reshared. |
No |
Will not be migrated. The original post will be migrated as part of the community it was created in. |
Posts in draft: Posts that haven’t been posted. Organizational posts: Organization-wide posts. Personal posts: Posts made to a user’s personal stream. Public posts: Posts shared externally that aren't a part of a Community. Posts held for review: A post that is still under review in Communities with hold posts for review enabled Abusive and spam posts: Posts that have been flagged as abusive Inactive User posts: A post made by an inactive user account, such as archived, deleted or suspended accounts Banned User posts: A post made by a banned user account, either banned at the community level or marked as abusive at the domain level. Blocked User posts: A post made by a user that is blocked by (or has blocked) a community owner. Google+ posts: A post made before the July 2020 Google Currents launch. Posts outside of your Chat retention policy: Posts made outside of the Chat retention window for your domain that are not in a legal hold. |
No |
Will not be migrated |
Posts owned by Guests: Posts made by external members |
Yes |
Guest replies will appear in Spaces as anonymous if Chat for external guests is disabled in the external member’s domain. |
Muted notifications: A post that gives no notification when it’s updated. |
No |
Will not be migrated. By default, users will be notified for all threads they follow in Spaces and for @mentions. To learn more about notifications in Chat and Spaces, read Manage chats. |
Read state: Whether a post has been read or not. |
No |
No complementary feature |
Attached images: An image attached to a post. |
Yes |
Images: An image attached to a comment. Images that exceed 200 MB will not be migrated. |
Attached videos: A video attached to a post. |
No |
Will not be migrated. Videos can be attached to messages in Spaces, but due to size limitations they will not be migrated. While the video attachment will not be migrated, links to videos (if available) will be migrated. |
Links: A hyperlink in a post. |
Yes |
Links: A link in a thread. |
Attached polls: A user poll attached to a post. |
No |
No complementary feature. As an alternative, you can ask people to leave an emoji reaction to your message. For example, if you ask “Should we have coffee or tea?” in the space, people can use the coffee or tea emojis to respond. You’ll see the number of times the emoji is used in response to your question. |
Pinned posts: A post pinned to a community. |
No |
Will not be migrated. The pinned thread feature is not available in Spaces. The content of the pinned posts will be migrated as regular posts. |
Disabled comments: A post that does not allow comments. |
Yes |
No complementary feature. These posts will be migrated, but as there is no locked thread feature in Spaces, they will be migrated as normal messages. Subscribe to the Google Workspace Updates blog to stay informed on the availability of Announcement Spaces. |
Leadership spotlight: Organizational posts that are highlighted in Currents. |
No |
No complementary feature. Spotlight posts are organizational posts which are not going to be migrated. |
Streams: A selection of posts that appear on the main Currents screen. |
No |
No complementary feature. Streams will not be migrated, however posts that appear in streams will be migrated in the communities they were originally posted in. |
Owner and moderator badges: A marking next to the owner or moderator of a community. |
Yes |
Space manager badge: A marking next to the manager of a space. Community owners will be migrated as space managers, and will get a space manager badge. Community moderators will be migrated as space members, and won’t get a badge. |
Circles: Users whose posts will appear in your Currents stream. |
No |
No complementary feature |
Blocked users: Users that are blocked by another user. |
Yes |
Blocked users: Users that are blocked by another user. A user that is blocked by a community owner, or who blocks a community owner, may not be migrated to the spaces created from those communities. |
Muted users: Users that are muted by another user. |
No |
No complementary feature |
External users: Users are not part of the domain owning the Community |
Yes |
Guest users: Guest users will be migrated as an invited guest in the space |
Spaces has a limit on how many users can access a single Space. Because of this limit, communities with more than 25,000 users won’t have all users of the community migrated to the Space (all posts made to the community will be migrated, as detailed in the table above). All active users who have created posts or engaged with the post will be migrated as members of the Space. All inactive users will be invited to the migrated Space and can join up to the limit of 25,000 users.
The below provides an overview of what the Google Workspace team is working on for future Google Chat and Spaces capabilities. Subscribe to the Google Workspace Updates blog to stay informed on the latest updates.
What’s on the roadmap:
What’s not currently on the roadmap: