IT Glue to Hudu migration: choose the tool and validate documentation

At a glance

Hudu provides an official IT Glue migration tool and a selective CSV alternative. Check the current repository before choosing a method, preserve a source export, and validate documentation and access before ending IT Glue service.

Compare Hudu's official IT Glue migration tool with selective CSV imports, verify prerequisites, and reconcile records, relationships and access.

Published Updated

On this page

Choose the official tool or a selective import

The Hudu import/export comparison helps you choose between selected CSV records and the migration tool.

Hudu's migration article links its maintained tool and describes GUI, PowerShell and CSV options. For selected spreadsheet records, follow the Hudu data import guide. For broader documentation transfer, evaluate the Hudu-owned migration repository, rather than treating every similarly named community fork as current official guidance.

Check prerequisites and source exports

Use Hudu 2.45.0 or newer, PowerShell 7+ on Windows x64, the required API keys and an IT Glue export. IT Glue API access is plan-dependent. Follow the repository's Data Export instructions and keep the source export for your pilot.

For general source-file validation, use the data export checklist. Keep the export unchanged and separately document any cleanup or field mapping.

Match required records to documented coverage

The tool covers companies, contacts, locations, configurations, domains, flexible layouts/assets, documents and passwords. Permissions and share links must be recreated separately. Check layout names and SSL relationships during the pilot. Ask Hudu about a supported checklist transfer if those records are essential.

Use the linked repository for the tool's current setup and transfer options. Keep a list of records that need separate handling before starting the full move.

Validate a representative client

Create a checklist from the records your technicians actually need. Compare counts and sample fields, open migrated articles, follow links, inspect attachments and relationships, and verify access using ordinary technician roles. Keep failures separate from records intentionally omitted. A completed migration job is not sufficient evidence for every field or attachment.

Expand the migration after the sample records, relationships and technician access checks pass. Use the migration checklist for source-access dates, reconciliation and cutover ownership.

Preserve Hudu records after the transition

RMMBackup has a Hudu integration; it does not currently offer an IT Glue backup connection or execute this migration. Use the official source export for IT Glue. After validating Hudu, capture supported destination records and inspect the successful backup before relying on it.

The Hudu export guide explains native exports and RMMBackup downloads. Optional password/file capture and plan history limits affect what remains available. The migration use case explains how previously captured information can answer later client questions.

Official source

Migrate Data from ITGlue to Hudu

Related Hudu integration

Review current Hudu backup coverage and availability.