This guide walks through migrating from ITGlue to Hudu. There are two supported paths: the ITGlue → Hudu migration script (run via a guided Windows app or raw PowerShell) and CSV export/import. It covers preparation, what each method brings over, and how to validate the result. It's written for teams who have already decided to move to Hudu.
Related: Migration to Hudu: Overview & Best Practices, Importing Data, and Understanding Integrations.
The migration script is maintained in Hudu's GitHub repository: ITGlue-Hudu-Migration. The repository README is the authoritative, most up-to-date reference for supported data, the minimum Hudu version, and run instructions — it is updated more often than this article, so check it before you begin.
Guides
Before you begin
- Hudu — a Hudu instance (cloud or self-hosted) and an API key with appropriate access (including password access, see below).
- ITGlue — API access, which requires the ITGlue Enterprise plan (or a legacy plan with API access).
- Workstation — a Windows machine. The guided app requires Windows 10+ (x86_64); the raw PowerShell script requires PowerShell 7+.
Large migrations can take several hours. Run on a Windows Server, or a machine with Windows Update and Sleep disabled, so the process isn't interrupted.
Option 1 — The migration script
You can run the migration two ways, both from the same repository:
-
Guided Windows app (recommended) — download
ITGlue-Hudu-Migration-GUI.exefrom the repository and follow the on-screen setup. It runs the migration scripts behind a simple UI. - Raw PowerShell — clone the repository and run the script directly if you prefer to drive the flow yourself.
Prepare your Hudu instance
- Start with a fresh Hudu install with no integrations set up. Sync companies/contacts from your PSA and configurations from your RMM after the migration.
- Don't create custom asset layouts beforehand — let the migration create the initial assets and layouts.
- Be on a current, supported Hudu version. The repository README lists the required minimum (updated over time), so confirm it there before running.
- Self-hosted only (optional): raise the rate limit to speed things up, then restart:
echo "RATE_LIMIT_REQUESTS=9999999" >> ~/hudu2/.env
Cloud/Hudu-hosted instances don't need this — the script automatically waits and retries if it hits the rate limit.
- Optional fresh start: if you have no important data yet, reset to a clean instance. Self-hosted:
cd ~/hudu2/ && docker compose down --volumes && docker compose up -d
For a cloud-hosted reset, contact Hudu support. Resetting is optional and not required to complete the migration.
Prepare your ITGlue instance
- Clean up first — remove duplicate records and delete old data you don't want to migrate.
- On each Flexible Asset Layout, make sure no two fields share the same name (e.g. two "Pre-Shared Key" fields on a Wireless asset) — rename one to prevent script errors.
- Rename any organizations that contain commas — the ITGlue API doesn't support commas.
- Give every client a unique name. ITGlue allows duplicate organization names but Hudu doesn't, so duplicates fail with a "Name already taken" error.
- Fill or remove blank passwords — a blank password causes that password to fail on import. Ensure your API key has password access, and that important passwords have values.
- Companies
- Contacts
- Locations
- Configurations
- Domains
- Flexible Asset Layouts
- Flexible Assets
- Documents (with folder structure)
- Passwords
- Document links
- Checklists — supported via a secondary script run after the main migration (confirm current behavior in the repository README).
- SSL certificates — not migrated.
- Permissions — not migrated (folders, companies, passwords, KBs, etc.). Set up groups and permissions in Hudu afterward.
- Password relations to articles and SSL certificates — these relationships aren't exposed by the ITGlue API, so they aren't included by default. A follow-up relation script is used to populate password relationships after the main run.
Run the migration
- Collect your ITGlue API key (with password access) and your Hudu API key.
- (Optional) Export a full ITGlue tenant ZIP for attachments and references.
- Launch the guided Windows app, or clone the repository and dot-source the script in PowerShell 7:
. .\ITGlue-Hudu-Migration.ps1
- Follow the prompts to select which data types to migrate. Long migrations can run unattended.
- (Optional) Post-run helpers: set layouts active, run the relation helper to populate missing relationships, and add attachments via the API if needed.
Option 2 — CSV export/import
For a more manual path, import data with Hudu's CSV importer. This is useful for selective migrations, cleanup projects, or when you only need certain assets or KB articles.
CSV import is good for:
- Importing structured data into assets (via Hudu's CSV templates).
- Bulk-creating records with spreadsheet workflows.
- Importing knowledge base articles via CSV (plain-text content).
Requirements: files must be .csv and follow Hudu's template headers exactly, be under 1 GB, use YYYY-MM-DD dates, and be saved as CSV UTF-8 (Comma delimited) to preserve special characters.
Visit Importing Data for templates and full formatting details.
Choosing between the script and CSV
- Script — best for a fuller, automated migration (companies, contacts, configs, domains, flexible assets and layouts, documents, passwords, links).
- CSV — best for selective imports, cleanup, or when you want to control exactly which assets/KBs come over and how fields map.
After you migrate: validation checklist
- Spot-check several clients for completeness (assets, documents, passwords).
- Confirm Flexible Asset Layouts exist and are active.
- Review relationships and links, and re-run the relation helpers if needed.
- Set up groups/permissions and confirm staff have the access they expect (permissions aren't migrated).
FAQ
API access is required, which means the ITGlue Enterprise plan or a legacy plan that includes API access.
Yes. The repository includes a guided Windows app (ITGlue-Hudu-Migration-GUI.exe, Windows 10+ x86_64) that walks you through setup and runs the scripts for you. Use raw PowerShell only if you prefer to drive the flow manually.
It depends on the size of your ITGlue instance — large instances can take several hours. Run it on a machine that won't sleep or restart mid-run (a Windows Server, or a workstation with Windows Update and Sleep disabled).
Checklists are supported via a secondary script run after the main migration. Permissions are not migrated — plan to set up groups and permissions in Hudu afterward. Confirm the current behavior for both in the repository README.
Yes. If you'd like assistance, open a support ticket or reach out to Hudu's team to discuss your source data and timeline.
Troubleshooting
ITGlue allows duplicate organization names but Hudu doesn't — the first succeeds and duplicates fail. Give every ITGlue organization a unique name before migrating.
The ITGlue API doesn't support commas. Rename any organizations containing a comma before running the migration.
When prompted, use a prefix such as ITG- for migrated layouts to avoid collisions with layouts that already exist in Hudu.
A blank password causes that entry to fail. Fill or remove blank passwords in ITGlue before migrating, and make sure the ITGlue API key you're using has password access.
Cloud/Hudu-hosted instances automatically wait and retry. On self-hosted, either raise the rate limit (see "Prepare your Hudu instance") or simply let the script handle the waits automatically.
Those relationships aren't exposed by the ITGlue API, so they aren't brought over in the main run. Use the follow-up relation script to populate password relationships after migrating, or add the critical ones manually.
Support
If you get stuck, open a support ticket with logs attached. Include your environment details (Hudu version, cloud or self-hosted), the import method used, and any error messages.