This article gives a clear, practical overview for migrating your documentation into Hudu. It's written for teams who have already decided to move to Hudu and want a structured approach to preparing the environment and importing data. It covers what to do before you start, whether to connect integrations first, the tools available for importing, and a suggested phased flow.
Related: Importing Data, Understanding Integrations, and the Migrate Data from ITGlue to Hudu guide. Community-maintained migration scripts are available in the Hudu Community script library.
Guides
Before you begin
Start by gathering a clear picture of what you're moving and where it's going:
- Where your current documentation is stored.
- What export options those systems provide.
- The types of items you plan to bring into Hudu.
- How you want your documentation organized going forward.
This is the ideal time to clean and standardize your existing content — remove outdated items and align naming conventions before you import, so you're not migrating clutter.
Connecting integrations first
In most cases, if you use a PSA or RMM that supports company synchronization, connect that integration before migrating data. When integrations are connected first, Hudu can automatically create or sync companies from your PSA or RMM, which helps ensure:
- Company names match exactly.
- Duplicate companies are avoided.
- Future synchronization works smoothly.
- Imported items map cleanly to the correct companies.
After connecting, review the synced companies and confirm they match your expectations. You can add any internal or non-PSA companies manually or import them with the CSV importer.
When you might wait
Connecting integrations upfront isn't always ideal. You may want to hold off if:
- You're using a testing or sandbox environment and don't want production companies synced yet.
- You prefer to build your company structure manually before introducing automated sync.
- Your PSA or RMM doesn't include all the companies you want to manage in Hudu.
- You're performing a custom migration where companies need to be created or imported in a specific order.
In those cases, create companies manually or use the CSV importer first, then connect integrations later.
The migration flow (phased)
A phased migration keeps things organized and reduces rework.
1. Prepare your Hudu environment
- Add or import companies.
- Create or adjust asset layouts.
- Configure permission groups.
- Enable SSO (optional).
- Connect PSA/RMM integrations if appropriate.
Preparing your structure first ensures incoming data maps correctly.
2. Migrate in stages
Many teams follow this order, validating each area before moving on:
- Companies
- Asset types and assets
- Passwords
- Knowledge base articles
- Attachments and files
- Additional internal or team-specific documentation
3. Review and organize
- Spot-check companies and assets.
- Confirm relationships and linking.
- Organize article categories.
- Standardize naming conventions.
This leaves your environment consistent and ready for daily use.
Tools
Hudu supports several import methods — use any combination depending on your source system and export formats.
The Hudu community maintains scripts for many commonly used documentation platforms. These can help import companies, assets, passwords, and knowledge base articles, depending on what the source platform exposes.
Browse the script library in the Hudu Community.
Hudu's built-in CSV importer makes it easy to bring in structured data from spreadsheets. It supports companies, assets (mapped to your configured layouts), passwords, and knowledge base articles. This is a fast, straightforward option when your current system can export clean CSV files. Download Hudu's template for the record type, match your data to it exactly, and select the corresponding import type when uploading.
Visit Importing Data for additional information on templates and formatting.
For teams with technical resources, or structured data that doesn't fit CSV import, the Hudu API offers full flexibility for automated, repeatable migration workflows — useful for custom field mapping or large-scale imports. API documentation is available in your instance under Admin >> API Keys.
Some documentation is easiest to bring over by hand — especially content that benefits from reformatting or restructuring. Manual migration works well for articles, procedures, attachments, and freeform notes.
FAQ
Companies, assets (mapped to your configured asset layouts), passwords, and knowledge base articles. Hudu provides generic templates for companies, KB articles, and passwords, and each custom asset layout you create generates its own import template.
No. Imports do not update existing records — re-importing the same data creates duplicates. Import into a clean environment, and avoid re-running a file to "fix" records already in Hudu.
A few rules keep imports clean:
- Use Hudu's downloaded template and follow the headers exactly.
- Save as CSV UTF-8 (Comma delimited) to preserve accented and special characters.
- Keep the file under 1 GB and in
.csvformat. - Format dates as YYYY-MM-DD.
Yes. The community maintains migration scripts for many common source platforms, and Hudu's team offers migration assistance for teams moving from other documentation tools. If you'd like hands-on help, reach out to Hudu to discuss your source system and timeline.
Troubleshooting
Imports create new records rather than updating existing ones, so duplicates usually come from re-running an import or from company names not matching. To avoid this:
- Connect your PSA/RMM first so company names sync and match exactly.
- Import into a clean environment and don't re-run the same file to correct records.
- Confirm a company doesn't already exist (via sync or a prior import) before importing it again.
This is almost always an encoding issue. Re-save the file as CSV UTF-8 (Comma delimited) — particularly if you edited it in Microsoft Excel — and re-import.
Check the file against Hudu's requirements:
- The column headers match the downloaded template exactly.
- You selected the correct Import Type (Companies, Passwords, Knowledge Base Articles, or the specific asset layout).
- The file is
.csv, under 1 GB, with dates in YYYY-MM-DD format.
Visit Importing Data for template details.
Asset imports map to asset layouts, so the layout must exist first. Create and activate the asset layout in Admin >> Asset Layouts — Hudu then generates a matching import template for it. Import your assets against that template.