Bridges are used by the Transformation Suite to migrate data from source Connections to target Connections. Bridges are created from a source Connection, a target Connection, a Settings Template, a set of Value Maps, and a set of Value Lists.
Please consult the following guides for specific instructions on configuring migrations:
Source system type
Target system type
|G Suite (formerly Google Apps)||G Suite||Migrate - G Suite to G Suite|
|Microsoft SharePoint||G Suite||Migrate - Microsoft SharePoint to G Suite|
|Microsoft Exchange||G Suite||Migrate - Microsoft Exchange to G Suite|
|File shares||G Suite||Migrate - File shares to G Suite|
|Box.com||G Suite||Migrate - Box.com to G Suite|
|Dropbox||G Suite||Migrate - Dropbox to G Suite|
|Citrix ShareFile||G Suite||Migrate - Citrix ShareFile to G Suite|
|Egnyte||G Suite||Migrate - Egnyte to G Suite|
Bridges have a number of attributes used to track configuration, status, and results:
|Name||The name of the Bridge.|
|Group||An deprecated attribute. If you believe you need to use a Bridge Group, please email AppBridge support at firstname.lastname@example.org.|
The current state of the Bridge. Please consult the Action States documentation for detailed information.
The Transformation Server that will be used to execute Bridge Actions. Choosing a Transformation Server from the drop down menu will only be saved if the Bridge is executed.
Best Practice: Select the Automatic entry in the drop-down menu to allow the Transformation Suite to automatically manage the Transformation Server infrastructure.
|Source||The source Connection for the Bridge.|
|Target||The target Connection for the Bridge.|
|Settings Template||The Settings Template in use by this Bridge. Can be edited to change the Settings Template, Value Maps, and Value Lists in use by this Bridge.|
|Started||The start time of the most recent Bridge execution.|
|Completed||The completion time of the most recent Bridge execution.|
|Transaction Summary||Summary of Transaction results for the selected Bridge. Click the document icon to view.|
|Transaction Log||A log of every Transaction processed during the Bridge Action execution. Click the document icon to view.|
|Execution Log||Summary of Bridge Action steps, and any catastrophic failures during service creation. Click the document icon to view.|
|Run History||A list of all previous Bridge executions and the corresponding logs. Click the Expand+ button to view.|
Please consult the Bridge Logs documentation for detailed information.
You can manage Bridges at any time from the Transformation Suite user interface:
- Sign into an authorized Transformation Suite administrator account.
- Click the Bridges link in the pages navigation tabs.
- Manage Bridges from the Bridges list.
Adding a Bridge
For specific instructions on each type of Bridge please refer to the section Migrate with Transformer.
The following general settings are configurable when adding Bridges:
|Source Connection||The source Connection for the Bridge. Data will be migrated from this Connection.|
|Target Connection||The target Connection for the Bridge. Data will be migrated to this Connection.|
|Conversion Map||The Conversion Map for the Bridge. Settings for this Conversion Map can be edited by clicking the edit icon beside the Conversion Map selection drop down menu.|
|Start Bridge Immediately||If this option is selected, a Bridge Action will immediately be added to the Action Queue for each generated Bridge.|
|Server||Specifies the Transformation Server or Server Group that this Bridge will be executed on. Leaving this setting on Automatic will allow the Transformation Suite to automatically assign this Bridge to the next available server.|
Executing Bridge Actions
Bridge Actions can be executed in three ways:
Using the Run Action to execute Bridge Actions will validate every source object with the target Connection to guarantee existence. To execute the Run Action:
- Select the checkbox beside each Bridge you would like to Run.
Click the Run button on the Bridges toolbar.
Note: Using the Run Action will not create duplicates, even if used multiple times. Using Run will ensure the existence of data, and is useful if data has been deleted or moved on the target since the previous migration.
Using the Delta Action to execute Bridge Actions will execute Bridge Actions incrementally, providing significantly faster performance than the Run Action, and only migrating what is new or changed since the previous execution. To execute the Delta Action:
- Select the checkbox beside each Bridge you would like to run incrementally.
Click the Delta button on the Bridges toolbar.
Note: On the first migration, the Run Action and the Delta Action are identical.
Using the Retry Failures Action will attempt toremigrateevery object that failed to migrate in previous migrations. It does not crawl the entire source Connection, it will only crawl previously failed objects.
- Select the checkbox beside each Bridge you would like to Retry Failures.
Click the Retry Failures button on the Bridges toolbar.
Note: Using the Retry Failures Action can be significantly faster than using the Delta Action, as it will only crawl and retry the objects that failed, instead of all objects within the Bridge scope.
Bridge Actions can be started at a later date by using the scheduling functionality built into Plans. Bridges can be scheduled at two times:
Scheduling - New Bridge
- Click the Add button on the Bridges toolbar.
- At the bottom of the Add Bridge card there is a scheduling section. Configure the Bridge schedule based on the Configuration - Scheduling documentation and your requirements.
Scheduling - Existing Bridges
- Select the checkbox beside each Bridge you would like to schedule.
- Configure the Bridge schedule in the Schedule Bridge card based on the Configuration - Scheduling documentation and your requirements.
- Select the checkbox beside each Bridge you would like to stop.
Click the Stop button on the Bridges toolbar.
- Select the checkbox beside each Bridge you would like to delete.
Click the Delete button on the Bridges toolbar.
Importing Bridges has been replaced by automatic Bridge partitioning. Please consult the migration guides documentation for specific details on how to partition your Bridges.
If you believe you need to import Bridges by CSV, please email AppBridge support at email@example.com.
Deleting Historic Logs
Caution: Deleting Historic Logs will delete all identity tables for processed objects. This will remove the link between the Transformation Suite and any previously migrated objects.
If you believe you need to delete historic logs for a Bridge, please email AppBridge support at firstname.lastname@example.org.