Migrating from IT Glue or Hudu
Connect with an API key and bring organizations, devices, flexible assets, passwords and documents across, with a preview first.
Go to Admin → Export & import → Migrate. You need the Import data permission and access to all organizations. Admins have both.
1. Create an API key
IT Glue
- In IT Glue, go to Account → Settings → API Keys and click Generate API Key.
- Turn on Password Access if you want password values to come across. Without it, passwords arrive with their names, usernames and URLs only.
- In Knowpoint, choose your IT Glue region (United States, Europe or Australia) and paste the key.
Hudu
- In Hudu, go to Admin → API Keys and create a new key.
- Leave it unrestricted (not limited to one company) and allow password access.
- In Knowpoint, enter your Hudu address, for example
https://yourcompany.huducloud.com, and paste the key.
Click Connect. Knowpoint lists your organizations and layouts. Nothing is copied yet.
2. Choose what comes across
- Sections: locations, contacts, devices, flexible assets, passwords, documents and articles, and domains and websites.
- Include password values: only available if your role can reveal passwords. Values are encrypted as soon as they arrive.
- Organizations: all of them, or only the ones you choose.
- Layouts:
- Hudu: choose what each asset layout becomes: Devices (assets), Contacts, Locations, a Flexible asset type with the same fields, or Don't migrate. Knowpoint suggests a choice for each layout.
- IT Glue: configurations always become devices. Each flexible asset type can be migrated or skipped.
Click Read data and preview. The data is read in the background, which can take a few minutes for large accounts. You can leave the page and come back.
3. Preview and import
The preview shows how many items will be added and how many already exist, plus any warnings. Nothing has changed yet.
- Change choices takes you back to step 2.
- Import adds everything. You get a notification when it's done.
- Cancel deletes the API key and the data that was read.
What maps to what
| IT Glue | Hudu | Knowpoint |
|---|---|---|
| Organizations | Companies | Organizations |
| Locations | Company address | Locations |
| Contacts | People layouts | Contacts |
| Configurations | Computer and device layouts | Assets, in the matching asset type (Server, Workstation, Network device…) |
| Flexible assets | Other asset layouts | Flexible assets, with the same fields |
| Passwords | Asset passwords and password fields | Passwords, linked to their asset |
| Documents | Articles (global articles go to the Knowledge Base) | Client documents |
| Domains | Websites | Domains |
Fields that have no equivalent in Knowpoint are added to the item's notes, so nothing is lost. Tag fields that point at other items become related items.
Running it again
Migration uses the same matching as file imports. Organizations, types and tags with the same name are reused, and items that already exist are skipped, never overwritten. You can run a migration again, for example after a final sync before you switch over, and only what's new is added. See Matching and avoiding duplicates.
Security
- The API key is encrypted while the migration runs, and deleted when it finishes or is cancelled.
- Knowpoint only reads from IT Glue or Hudu. It never changes anything there.
- Every step is recorded in the audit log.
Troubleshooting
- The key was refused: check the key, the region (IT Glue) or the address (Hudu), and that the key isn't limited to one company.
- Passwords came across without values: turn on password access for the API key, then start a new migration. Passwords that already exist are skipped, so delete them first if you want them re-imported with values.
- Some IT Glue documents have no content: the IT Glue API doesn't return every document's content. They link back to the original, so you can copy them over by hand.
- Self-hosted Hudu on a private network: Knowpoint must be able to reach your Hudu address over the internet.