Migrate Teams members from Apigee to Drupal portal

This page describes how to migrate existing Apigee (formerly referred to as "Apigee X") or Apigee hybrid developers to your Drupal portal as Teams members. Once migrated, Teams members can be associated to Apigee AppGroups.

Migration/Synchronization Steps

The migration process involves these steps:

1. Create appropriate roles in your Drupal portal to match Apigee roles for the members to be migrated. (e.g., admin). The default role is member if no other team member roles are created in the Drupal portal.
2. Run the Teams Sync process to migrate the developer email ids and roles to the Drupal portal. See below for instructions to synchronize Teams members.

Teams member synchronization:

• Stores all the team member details in the cache table.
• Migrates the member information from Apigee or Apigee hybrid to the Drupal portal database by retrieving the member information from the  '__apigee_reserved__developer_details'  attribute and then storing it in the Drupal team_member table.

Note:

• If matching roles are not present in the Drupal during migration, the role for migrated developers is member (default).
• If the developer email id doesn’t already exist for a Drupal portal Teams member, that developer receives an invite for membership and the email id displays on the Pending Invitations tab.

You can synchronize Teams members from Apigee to the Drupal developer portal either of the following methods:

Migrate Teams members from Apigee using the Drupal admin panel

To migrate Apigee developers using the Drupal admin panel, follow these steps:

1. Log in to your portal as a user with Apigee administrator privileges.
2. Select Configuration > Apigee > Teams.
3. Click the Sync tab.
4. Click one of the following buttons:
    

   Button	Description
   Run team member sync	Sync the team member in real-time, as a synchronous operation. The sync operation must complete before you can perform any other operations or close the browser.
   Background team member sync	Sync the team member as a background task. The team member sync operation is queued for execution with the Drupal core cron. Note: Because the team member sync operation may not complete in a single cron job, depending on the number of members and your scheduled cron configuration, you can run the entire queued cron job as a dedicated background process using the Drush Queue Handling module.

If the synchronization fails, a message is logged with information describing the problem.

Migrate Teams members from Apigee using the CLI

To migrate Teams members using the CLI, use one of the commands below.

1. If you are using Drush, run the following command:
   

   drush apigee-edge:teams-sync

2. If you are using Drupal, run the following command:
   

   drupal apigee-edge:teams-sync

Note: You can automate the synchronization process by configuring it to run in cron.