Tag Archives: Migration

Migrate users and data between G Suite environments more easily

Quick launch summary 

G Suite Migrate, currently available in beta, helps admins assess, plan, and migrate large amounts of content directly into G Suite. It already supports Microsoft Exchange, Microsoft SharePoint, Microsoft OneDrive, file shares, and Box migrations. With this launch, you can now also migrate between G Suite environments. Specifically, you can: 
  • Selectively migrate Gmail, Calendar, Drive, and more data between G Suite environments. 
  • Choose to migrate all users from one environment to another. 
  • Selectively migrate specific user data (organizational units, users, or subsets of data) between G Suite environments. 

Getting started 

Rollout pace 

Availability 

  • Available to G Suite Business, G Suite Enterprise, G Suite Enterprise for Education, and G Suite Essentials customers 
  • Not available to G Suite Basic, G Suite for Education, and G Suite for Nonprofits customers 

Resources 

Migration of Drive DLP rules to new system

What’s changing 


Now, we’re going to migrate any rules you created in the legacy DLP system to this new system. After this migration, you should use the new DLP system to create and manage your organization’s DLP rules for Drive. There are three key things to know: 
  • You can manually migrate your rules to the new system any time before August 10. 
  • Starting on August 10, we’ll automatically move any unmigrated rules to the new system. 
  • These migrations relate to rule management in the Admin console only. There’s no change in how the rules will be enforced for end users. 

Use our Help Center to learn more about the migration, and see more details below. 


Who’s impacted 

Admins with privileges to manage DLP rules. 


Why it’s important 

By bringing all your rules into the new DLP system, we’re making it easier to manage your DLP rules and take advantage of the improvements that the new system offers. 


Additional details 

Learn more about the new DLP system 
The new Drive DLP system offers more advanced policies, additional admin insights, and more flexible deployment than the legacy system. The new Drive DLP functionality can be found at Admin console > Security > Data Protection. 

To learn more, see our launch announcement for the new DLP system or visit our Help Center to learn more about the new DLP for Drive. You can also visit our Help Center to learn more about the migration to the new DLP system. 


User-controlled migration available now 
Currently, you can manually migrate your rules to the new UI by manually creating a new rule in the new Drive DLP and then deleting the legacy DLP rule. During that time, you won’t be able to update your rules, but they will still be in effect for end users. 

Note that on August 3, customers who have yet to create any legacy Drive DLP rules will not be able to create rules in the legacy system. Existing customers can continue to create and modify rules up until their migration. Rules can be created in the new system at any time. 

Before migration takes place, you’ll see a banner about the upcoming changes 


Automatic migration will start on August 10 
If you haven’t manually migrated your rules by August 10, we’ll start to automatically migrate them to the new system. Migration is expected to complete for most customers by the end of August 2020. A small subset of customers will be migrated in September 2020. Once started for your domain, the migration process can take up to 24 hours, and during that time you won’t be able to modify rules in the legacy system. 

Once the migration is completed for your domain, you will see a banner announcing that your DLP rules have moved when you go to the legacy rules location at Admin console > Security > Rules. At that point, you will no longer be able to create DLP rules in the legacy system. 

When migration is complete, you’ll see a notification banner in the Admin console 

Getting started 

Rollout pace 

Automatic rule migration: 
  • Rapid and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on August 10, 2020. Migration is expected to complete for most customers by the end of August 2020. A small subset of customers will be migrated in September 2020. 

Availability 

  • Available to G Suite Enterprise, G Suite for Education, and G Suite Enterprise for Education customers. 
  • Not available to G Suite Basic, G Suite Business, and G Suite for Nonprofits, G Suite Essentials, and G Suite Enterprise Essentials customers. 

Resources 

Sunsetting the creation of target spend field for Maximize Clicks strategies in Google Ads API

On July 31st, 2019 we will begin to sunset the target spend field for Maximize Clicks bidding strategies in the API. This will affect all versions of both the AdWords API and Google Ads API. The following behaviors will be blocked:
  • Populating the target spend field on existing standard and portfolio strategies.
  • Attaching portfolio strategies that have the deprecated field set to campaigns.
Later this year, our systems will start ignoring the target spend field and instead use your daily budget to manage spend. In order to prepare for this change, you should start using your budgets to specify how much you’d like to spend for Maximize Clicks bidding strategies and migrate your campaigns off this field today.

Read on to see how this will affect your API usage.
Affected Target Spend Fields
Google Ads API campaign.target_spend.target_spend_micros
bidding_strategy.target_spend.target_spend_micros
AdWords API Campaign.BiddingStrategyConfiguration.TargetSpendBiddingScheme.spendTarget
SharedBiddingStrategy.TargetSpendBiddingScheme.spendTarget


Change Description
Any mutate operations that set a target spend field for the first time will return an error. You will be able to update a target spend field that currently contain a value, but you cannot set previously empty fields to a new value. Additionally, any operation attaching a bidding strategy to a campaign, where that bidding strategy has a value set for a target spend field, will throw an error. To manage Target Spend on any new campaigns, we recommend using a campaign budget. In each of these disallowed cases an error will be thrown.

Performing any of the disallowed actions above will generate one of the following errors:
  • OPERATION_NOT_PERMITTED_FOR_CONTEXT
  • UNSUPPORTED_FIELD_IS_SET
If you have any questions about this change or any other API feature, please contact us via the forum.
- Cory Liseno, Google Ads API Team

Introducing the Google Ads Query Builder tool

Today we are excited to announce that the Google Ads Query Builder tool is now available on the Google Ads API Developer Site.

The Google Ads API has a robust reporting system that utilizes our new Google Ads Query Language. The language’s syntax allows you to select from all the resources that are available for reporting, and also filter or sort the result set on the server before they are returned to your application.

This tool provides a friendly web interface for you to explore our API’s reporting capabilities, and generate queries that you can copy and paste right into your applications. You can visit the site and try out the tool today!

Example usage of the Google Ads Query Builder: A screenshot showing a sample usage of the Google Ads Query Builder UI, including both filtering and ordering. Happy reporting!
- Cory Liseno, Google Ads API Team

Saying Goodbye to the GData Admin Settings API

Posted by Shashank Gupta, Product Manager, Google Apps for Work and Wesley Chun, Developer Advocate, Google Apps

Back in 2013, we launchedthe Google Apps Admin SDK, and later announced as a result that several outdated Apps Admin APIs would be deprecated and shut down in April 2015. Today, we are continuing this effort of removing older, less-used functionality by announcing the deprecation of the GData Admin Settings API. Some GData API functionality will find a replacement from an Admin SDK counterpart, while other features will be discontinued. The following table summarizes which features will be retained (and where to access replacement functionality) and which won’t:

Admin Settings API

Endpoint

Post-Deprecation Replacement (if any)

General Settings

/defaultLanguage

Customer API

/organizationName

Customer API

/currentNumberOfUsers

no replacement / discontinued

/maximumNumberOfUsers

no replacement / discontinued

Account Settings

/accountInformation/supportPIN

no replacement / discontinued

/accountInformation/customerPIN

no replacement / discontinued

/accountInformation/adminSecondaryEmail

Customer API

/accountInformation/edition

no replacement / discontinued

/accountInformation/creationTime

Customer API

/accountInformation/countryCode

Customer API

Appearance Settings

All endpoints

no replacement / discontinued

Verification Settings

All endpoints

no replacement / discontinued

Single Sign-on (SSO) Settings

All endpoints

replacement API coming soon

Gateway and Routing Settings

All endpoints

no replacement / discontinued

To summarize, the GData Admin Settings API is being deprecated today and will remain operational for one year to give developers time to migrate. This means that on August 16, 2017, this deprecated API will be shut down. At that time, all calls to the API and any features in your applications that depend on it will no longer work. Please migrate as soon as possible.

Updated version of Google Apps Migration for Microsoft Exchange®

An updated version of Google Apps Migration for Microsoft Exchange® (GAMME) is now available:

What’s New
  • Service Accounts and OAuth 2.0 tokens are now used for data migration authorization. This replaces the deprecated OAuth 1.0 protocol.
  • GAMME now uses the Gmail API for mail migration and label creation, replacing the Email Migration API v2 and Email Settings API, respectively.
  • Reserved labels are now prefixed with an underscore to ensure proper nesting in the Gmail web interface. For example, a folder named "Inbox/Receipts" is migrated as "_Inbox/Receipts."
  • If the migration user list includes a user that doesn't exist or there's an authorization issue, GAMME now detects the problem in all cases and doesn't try to migrate that user. Previously, GAMME would try each message individually and the failure would take a longer time.
  • Minor UI and logging improvements.

What’s Fixed
  • Multiple labels with names more than 225 characters long could cause a crash. 
  • Messages in subfolders of Deleted Items were not being correctly marked as Trash in Gmail.
  • Messages migrated from Exchange Public Folders to Google Groups show sender as "[email protected]."
  • GAMME would crash if any command line flag or setting content included "%s."
  • GAMME would fail to migrate the sender SMTP address in some rare cases.
  • IMAP commands and responses in the logs were sometimes truncated.

Launch Details
Release track:  
Launching to both Rapid release and Scheduled release

Rollout pace: 
Full rollout (1-3 days for feature visibility)

Impact: 
Admins only

Action:
Admin action suggested/FYI

More Information
What’s New in GAMME

Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Updated version of Google Apps Migration for Microsoft Outlook®

An updated version of Google Apps Migration for Microsoft Outlook® (GAMMO) is now available:

What's New

  • Click-To-Run editions of Outlook 2013 and Outlook 2016 are now supported.
  • Windows 10 is now supported.
  • Migrates email using the Gmail API.
  • Removed deprecated 2-legged OAuth command line options -- google_consumer_key and --google_consumer_secret.
  • Support Service Account authentication to migrate on behalf of a user from command line using --service_account_json_path option. See Run migration from command line for details.
  • Optionally collect and report crash data.

What's Fixed

  • Email migration is more resilient to throttling and network or server failures with improved retries with exponential backoff.
  • Empty email folders on the source are migrated as labels to Gmail.
  • Messages in Outlook’s Deleted Items now are correctly migrated to Trash.
  • GAMMO now allows graceful cancellation of a running migration.
  • Other minor UI issues.

Launch Details
Release track:  
Launching to both Rapid release and Scheduled release

Rollout pace: 
Full rollout (1-3 days for feature visibility)

Impact: 
Admins only

Action:
Admin action suggested/FYI

More Information
What’s New in GAMMO


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

New version of Google Apps Migration for IBM Notes (GAMIN) (v 5.0)

A new version (v 5.0) of the Google Apps Migration for IBM Notes (GAMIN) tool is now available for download. GAMIN was formerly known as Google Apps Migration for Lotus Notes (GAMLN).

Here’s what’s new:

  • Service Accounts and OAuth 2.0 tokens are now used for data migration
  • GAMIN now uses the Gmail API for mail migration and label creation, replacing the Email Migration API v2 and Email Settings API respectively
  • Flattened and simplified architecture:
    • Deprecated the multiple site/replicated admin database deployment option
    • Setup and Site profiles merged into a single System Setup profile
    • No longer necessary to specify mail/database servers as part of the system setup
    • Added a 5 step Quick Setup wizard
    • Option to auto-update Domino directory Server and Configuration document settings required for migration

Launch Details
Release track:  
Launching to both Rapid release and Scheduled release

Rollout pace: 
Available now for download

Impact: 
Admins only

Action:
Admin action suggested/FYI

More Information
Help Center


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Updated version of Google Apps Migration for Microsoft Exchange®

Google Apps Migration for Microsoft Exchange® v4.1 is now available with the following new features:
  • Google Apps Migration for Microsoft Exchange® Email migrations now uses the latest Email Migration API  (version 2).

  • Google Apps Migration for Microsoft Exchange® now uses latest Admin SDK API (version 1) for user validation and group creation.

  • Google Apps Migration for Microsoft Exchange® now uses the latest Contacts API  (version 3)

  • Administrators can choose to have message content that can not be migrated due to file size restrictions or blocked file types written to a user specific mbox file.

See what's new in this release for more details.

Note: All customers running previous versions of GAMME must upgrade to GAMME 4.1 before April 20, 2015. Older versions will stop functioning after this date.

Release track:
Rapid release and Scheduled release

Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Updated version of Google Apps Migration for Microsoft Outlook®

Google Apps Migration for Microsoft Outlook® v3.0 is now available with the following new features:
Release Track:
Rapid release and Scheduled release
For more information:

Note: all launches are applicable to all Google Apps editions unless otherwise noted

whatsnew.googleapps.com
Get these product update alerts by email
Subscribe to the RSS feed of these updates