Before you begin
- The Starter plan or higher (importing is blocked while Atlas Vault is read-only on the Community plan)
- An administrator role in Atlas AVD
- An IT Glue Administrator account, which IT Glue needs to create an API key
- A commercial Atlas AVD deployment. The import is not available in GCC High (see Availability below)
Create an IT Glue API key
- Sign in to IT Glue and open Account → Settings → API Keys.
- Under Custom API Keys, generate a new key and give it a name you will recognise, such as Atlas Vault import.
- To bring password fields across, turn on Password Access for the key. Without it, the rest of each asset still imports, but password fields arrive empty.
- Copy the key. IT Glue shows it only once.
Atlas uses the key only for the import you are running. It is sent with each request, never saved, and cleared from the dialog as soon as the import finishes. Revoke the key in IT Glue once you are done if you do not plan to import again.
Run the import
- In Atlas AVD, open Atlas Operations → Vault and go to Assets.
- Choose Import from IT Glue at the top of the asset list.
- Under IT Glue region, pick where your IT Glue account lives: United States (itglue.com), Europe (eu.itglue.com) or Australia (au.itglue.com). It matches the address you sign in to IT Glue at.
- Paste the API key and choose Load asset types.
- Atlas lists every flexible asset type in the account, all selected. Each row shows how many fields the type has, whether it Creates a new template or Adds to the existing template of the same name, and any fields that will not be imported. Clear the types you don't want.
- Leave Assign each asset to the company named after its IT Glue organization on to file each asset under that client. Atlas creates any company it doesn't find yet.
- Leave Import password fields (stored encrypted) on to bring passwords across, or turn it off to leave them out.
- Choose Import selected types. Atlas imports the types one at a time and shows each one's result as it finishes: how many assets were created, updated and failed.
Keep the dialog open until every type has finished. A large IT Glue account can take a few minutes, and each type is imported on its own, so one slow type never holds up the result of the others.
How IT Glue fields come across
Each IT Glue field becomes a field on the Vault template, in the same order and with the same name and hint. The field kinds map like this:
- Text becomes a text field, and Textbox becomes a multi-line text field. Rich-text formatting is flattened to plain text, keeping line breaks and bullet points.
- Number and Percent become number fields, Date becomes a date field, and Checkbox becomes a yes/no field.
- Select becomes a dropdown. Its options are the field's IT Glue options plus any value an asset still uses after its option was removed. A dropdown with more than 100 options comes across as a text field.
- Tag becomes a list of the names of the tagged records, such as the configurations or contacts the asset links to.
- Password becomes an encrypted Password field, shown only when you choose Reveal.
- Header becomes a section heading.
- Upload fields are not imported. Download any files you need from IT Glue and add them in Vault.
Imported fields are never marked required, so an older asset that has no value for a field still imports. A template holds up to 60 fields; fields beyond that are listed as not imported.
Importing into a template you already have
When Atlas Vault already has a template with the same name as an IT Glue type, the import adds to it instead of creating a second one. The rows on the type list say Adds to the existing template so you know before you start.
- Fields you already have are kept as they are. An IT Glue field fills an existing field with the same name and type, and any field the template lacks is added at the end.
- Nothing is removed, renamed or retyped on your template. A dropdown only gains the options the imported assets need.
What each imported asset gets
- The asset's name is its IT Glue name.
- With company assignment on, the asset is filed under the company with its IT Glue organization's name.
- An asset archived in IT Glue arrives archived in Vault. Select Archived above the asset list to see it.
- Every imported asset carries the itglue tag, so you can filter to them.
Read the results
When a type finishes, its row shows how many assets were created, updated and failed, and these notes when they apply:
- Passwords IT Glue didn't return: the API key does not have Password Access. Turn it on in IT Glue and import again; the assets are updated in place.
- Values left out because they didn't fit the field: a value that a field cannot hold, such as a date IT Glue stored as free text, was left out. The rest of the asset still imported.
- Only the first 50,000 assets of this type were imported: the type is larger than one import covers.
- A failed asset is listed with the reason, for example when it was already imported into a different template.
If you see IT Glue rejected the API key, check the key, that the region matches your IT Glue account, and that the key isn't restricted to other IP addresses. If IT Glue is rate-limiting the key, wait a few minutes and try again.
Run the import again
You can run the import as often as you like, for example to pick up changes while you move from IT Glue to Atlas Vault. Running it again updates the assets it created before instead of making copies.
- For the fields that came from IT Glue, IT Glue's current values win, including a value someone cleared in IT Glue.
- Fields you added to the template in Vault keep their values.
- New flexible assets in IT Glue are added as new Vault assets.
Once you have moved over, make your changes in Atlas Vault and stop re-importing. A re-import overwrites edits you made in Vault to the fields that came from IT Glue.
Availability
Every import is recorded in the audit log with how many assets were created, updated and failed. The import connects to IT Glue's commercial service, so it is not available for GCC High deployments or GCC High tenants: Atlas refuses the request rather than send your API key outside the GCC High boundary.