The Workspace Data Importer is currently an experimental feature. Contact your Customer Success Manager for more details.
The Ardoq Workspace Data importer allows you to copy workspaces, components, and references from one organization to another — as long as you are an administrator user in both organizations.
This importer is particularly useful for copying component and reference data from a sandbox (or staging) environment to a production environment.
Note: The data transfer is only possible as long as your organizations exist in the same data center. That is, you cannot transfer from EU to US data centers or vice versa.
Once enabled on your account, you can find this integration by going to Home > Import and integrations and selecting Ardoq Importer.
Configuring the Importer
The Connections tab will be pre-populated with all existing organizations where you have administrator privileges.
Select one of these connections when creating a new import and you'll be presented with a list of tables that represent the data and data models of the workspace, as well as tables that represent the references between workspaces.
In other words, you'll have a table with the name of your workspace, tables with references from the workspace to other workspaces, and two additional tables as follows:
Data model: The data model stores all the component and reference types that exist in the named workspace.
Workspace fields: This table stores metadata about the fields used in the workspace, including the field label and field type.
These secondary tables can be used to provide context for your existing workspace configuration, but do not need to be mapped and can be safely ignored.
Example
As an example, an original import configured three tables:
New Applications
New Business Units
New Business Units → New Applications
When importing those same tables using the Workspace Data Importer, you'll see the following tables related to the original import:
Workspace Table
The table for the existing workspace you are importing from another organization will look just like any other tabular import except that it has two additional columns:
Existing Ardoq OID: This is the Ardoq OID that was generated for the component the first time it was created in its original workspace. This will also be the OID used in the references tables.
Data source field: The data source field will show the organization name and the workspace name separated by a colon. For example: usertesting: New Applications. This column only provides context and can be safely ignored.
Finishing the Import
At this point, you can proceed with the import in the normal way. In the current implementation the mapping is manual and the pre-existing mapping from the workspaces you are importing will not be applied automatically. Refer to the Data Model and Workspace fields tables if you want to preserve the original configuration.