Migrate Data from ITGlue to Hudu

This guide walks you through migrating from ITGlue to Hudu. It covers two supported paths: (1) PowerShell migration script, and (2) using CSV export/import. It also explains what each method brings over, known limitations, and troubleshooting.

Before you begin

  • Hudu: Have a Hudu instance (cloud or self-hosted) and an API key with appropriate access.
  • ITGlue: You’ll need ITGlue API access (Enterprise or legacy plan with API).
  • Workstation: Windows machine with PowerShell 7+ for running the script.
  • You'll want to make sure your Hudu instance is prepared for migration and that your machine designated to run this script is also properly prepared.
    • Depending on the size of your ITGlue instance, the migration script can take several hours to run. As such, it's highly recommended to run the migration script on a Windows Server or a machine that has Windows Update and Sleep disabled

Option 1: Use the Hudu fork of the ITGlue → Hudu migration script

Repository: https://github.com/Hudu-Technologies-Inc/ITGlue-Hudu-Migration

Prerequisites - Hudu Instance:

It's recommended to have a fresh Hudu install with no integrations setup. You'll want to sync things like companies and contacts from your PSA and configurations from your RMM after the migration is completed. Don’t setup any custom Asset Layouts and let the migration create the initial assets.

  • 1. Make sure you are on a known-compatible Hudu version

    • At this point in time (August 27, 2025), the ideal version to be on when using this fork is at least 2.37.1 image. Up to 2.39.0 has been tested to be stable thus far.

  • 2 (optional). If you're self hosted, It's best to set ratelimit to be high. 

    • To do so, you can add this to your .env file and perform a docker compose down/up. If you're Cloud/Hudu hosted, the script will automatically wait if it hits the rate limit and will continue automatically.

 echo "RATE_LIMIT_REQUESTS=9999999" >> ~/hudu2/.env

 

  • 3 (optional). If you're just starting out of Hudu and don't have any important data in Hudu, it's best to start with a fresh instance.

Self-hosted reset:

cd ~/hudu2/ && docker compose down --volumes && docker compose up -d

Cloud-hosted reset: Contact Hudu support support@hudu.com and we can reset your instance for you.

Resetting your instance is completely optional and not necessary to complete the migration

Prerequisites - ITGlue Instance

It's highly encouraged to perform a clean up of you IT Glue environment. Such as removing any duplicate records and deleting any old data you don’t want to migrate.

Check that your Flexible Layouts don’t have any fields named the same thing on the same layout. For example, if you have two fields called Pre-Shared Key on the "Wireless" asset (One for primary one for guest), rename one of them to prevent script errors.

The ITGlue API doesn't support the use of commas "(,)". To prevent issues, rename any organizations with commas.

ITGlue allows for more than one client to exist with the same Name but Hudu does not. This will cause issues during the migration as the first client will succeed and subsequent clients with the same name will fail with "Name Already Taken" error from Hudu's API. Make sure any client is at least named with a unique name so that the migration can complete successfully.

Blank passwords in ITGlue will cause issues on import and cause the entire password to fail.

Make sure the API Key you're using has password access, and that all passwords have values if they're important.

What the script migrates

  • Companies
  • Contacts
  • Locations
  • Configurations
  • Domains
  • Flexible Asset Layouts
  • Flexible Assets
  • Documents (with folder structure)
  • Passwords
  • Document Links

What the script does not migrate

  • Checklists (API/export limitations)
  • SSL Certificates
  • Permissions (folders, companies, passwords, KBs, etc.)

Known notes and limitations

  • Password relations to Articles and SSL Certificates are not included by default (ITGlue API constraints). A follow-up step may be required for those relationships.
  • ITGlue allows duplicate organization names; Hudu does not. Ensure unique client names to avoid “Name already taken” errors.
  • Commas in ITGlue organization names can cause issues—rename before migrating.

High-level steps

  1. Collect ITGlue API Key (with password access) and Hudu API Key.
  2. (Optional) Export a full ITGlue tenant ZIP for attachments and references.
  3. Download/clone the migration repo locally.

  4. Open PowerShell 7 and dot-source the script:

    . .\ITGlue-Hudu-Migration.ps1
  5. Follow prompts to select which data types to migrate. You can run unattended for long migrations.
  6. (Optional) Post-run helpers:
    • Set layouts active
    • Run helpers to populate missing relations
    • Add attachments via API if needed

Troubleshooting common errors

  • Duplicate/Conflicting layout names: Use a prefix (e.g., ITG-) when prompted to avoid collisions with existing Hudu layouts.
  • Duplicate client names: Rename duplicates in ITGlue before migration.
  • Blank passwords: Blank passwords fail import—fill or remove before migration.
  • Rate limiting: Cloud Hudu automatically waits/retries; for self-hosted, ensure a sufficiently high rate-limit setting or simply allow the script to auto-handle waits.

Option 2: CSV export/import into Hudu

If you prefer or need a more manual path, you can import data using Hudu’s CSV importer. This is helpful for selective migrations, cleanup projects, or when you only need certain assets or KBs.

What CSV import is good for

  • Importing structured data into Assets (via Hudu’s CSV templates)
  • Bulk-creating or updating records using spreadsheet workflows
  • Importing Knowledge Base articles via CSV (plain text content)

CSV import requirements (summary)

  • Files must be .csv and follow Hudu’s template headers exactly.
  • Total size under 1 GB.
  • Dates in YYYY-MM-DD format.
  • Save as CSV UTF-8 (Comma delimited) to preserve special characters.

See: Hudu Support — Importing Data

Choosing between the script vs CSV

  • Script: Best for a fuller, automated migration from ITGlue (companies, contacts, configs, domains, flexible assets + 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.

Validation checklist

  • Spot-check a few clients for completeness (assets, documents, passwords).
  • Confirm Flexible Asset Layouts exist and are active.
  • Review relationships/links and re-run relation helpers if needed.
  • Ensure staff have expected access (permissions are not migrated by the script).

Support

If you get stuck, open a support ticket with logs attached. Include environment details (Hudu version, Cloud/Self-Hosted), import method, and any error messages.

Was this article helpful?
1 out of 1 found this helpful