Hudu Migration

Import your IT documentation from Hudu into Ascent so you can switch without re-keying your knowledge base, passwords, and infrastructure records. The migration is read-only and one-directional — nothing is ever written back to your Hudu tenant.

The importer brings over your Hudu documentation: companies, folders, knowledge-base articles, passwords, websites (domains), networks, and your custom asset layouts and assets (Hudu's "Flexible Assets"). (Hudu users and Magic Dash cards are not imported — Ascent user accounts are created and invited separately, and dashboard cards have no Ascent equivalent.)

Asset links. Custom-asset fields that point at another asset or password (Hudu's "AssetTag" / "AssetLink" fields) come over as text so you don't lose the information; they'll be upgraded to real clickable links in a later update.

Who can run a migration

Running a migration is available to the organization Owner and Admins by default. Because it is controlled by the same migrations permission as the other importers, you can also create a custom role that grants migration access to specific people. It handles raw source credentials and bulk-creates records (including passwords), so grant access deliberately.

Before you start

In Hudu, go to Admin → API Keys and create an API key with read access. You'll need two values:

• Host — your Hudu address, e.g. acme.huducloud.com (or your self-hosted host). A full URL is fine — Ascent normalizes it.
• API Key — the key string Hudu generates.

Connecting and running

1. Go to Admin → Hudu Migration.
2. Enter your Host and API Key.
3. Click Test connection. Ascent runs an authenticated probe against your tenant. A clear error is shown if the credentials are rejected.
4. (Optional) Turn on Include attachments to also download images and files embedded in your Hudu articles and rehost them in Ascent. See Embedded images & attachments below for why this matters.
5. Click Create migration. Your credentials are validated and stored encrypted at rest; they are never shown again or written to logs.
6. Press Start. The import runs in the background and you can watch per-entity progress (pulled / loaded / skipped / failed).

Embedded images & attachments

Hudu articles often contain images and file links that point back at your Hudu site. If they're left pointing there, they keep working only as long as your Hudu tenant is online — the day you shut Hudu down, every embedded image in your imported articles breaks.

Turning on Include attachments prevents this. For each article, Ascent downloads the images and linked files hosted on your Hudu tenant, stores them in Ascent, and rewrites the article so it points at the Ascent copies. After that your articles no longer depend on Hudu being online.

• It's off by default. Leaving it off imports the article text but leaves embedded images pointing at Hudu — they'll break once Hudu is gone.
• It's slower, because every embedded file is downloaded (within the same gentle rate limit, so it won't disrupt your live Hudu).
• It's safe to re-run: already-rehosted files aren't downloaded again, and an image that fails to download is noted in the run report without stopping the rest of the migration. Files larger than 50 MB are skipped and logged.
• Only files hosted on your Hudu tenant are rehosted; images you embedded from other websites are left as-is.

How it works

• Throttling — every call goes through a single conservative rate limiter that stays well under Hudu's request threshold and backs off on 429, so a migration can never throttle your live Hudu API access.
• Idempotent — each Hudu record is matched to its Ascent record by source id. Re-running a migration updates existing records instead of creating duplicates.
• Resumable — progress is tracked per entity. If a run is interrupted, starting it again skips anything already fully imported and re-imports the rest from the start. Because the import is idempotent, re-importing never creates duplicates — it simply fills in what was missing.
• Reported — each run produces per-entity counts plus a log of skips and any records that failed (with the raw payload retained for review).

What is mapped

Hudu	Ascent	Notes
Companies	Clients	The company name becomes the client name; archived companies import as Inactive. The Hudu company id is kept as the client's reference number. The company's country and website are imported too, and the company type maps to the matching client type when it's a recognized one.
Folders	Folders	Your knowledge-base folder tree, with parents preserved.
Articles	Documents	The article body imports as a document; a company article links to that client, a global article imports org-wide. Shared articles are marked client-visible. With Include attachments on, embedded images and linked files are rehosted into Ascent (see above).
Asset Passwords	Credentials	Imported into the credential vault and encrypted at rest, including any one-time-password (TOTP) secret, linked to the company when present.
Websites	Domains	The website's address becomes a domain record, linked to its company. If Hudu has an SSL expiry, a certificate record is created and linked to the domain. A website with no matching company is skipped and logged.
Networks	Networks	The CIDR address imports as the network's subnet, linked to its company. (Networks are optional: if your Hudu plan or tenant doesn't expose the Networks / IP Address Manager module, the importer skips them and notes it in the run report — the rest of your migration still completes.)
Asset Layouts	Asset Layouts	Your custom asset types and their fields. Each Hudu field type (text, rich text, checkbox, website, list select, password, date, number, asset link, …) maps to the matching Ascent field type; an unfamiliar field type is imported as plain text and noted in the run report so nothing is lost. (Like Networks, Asset Layouts are optional: if your Hudu plan or tenant doesn't expose the endpoint, the importer skips the whole resource and notes it in the run report — the rest of your migration still completes.)
Assets	Assets	Your custom asset records, linked to their layout and (when present) their company, with every field value carried over. An asset whose layout didn't import is skipped and noted in the run report. (Also optional in the same way — if the Assets endpoint isn't available on your tenant, they're skipped and noted rather than failing the run.)

Anything the importer can't map cleanly is surfaced in the run report rather than dropped or silently defaulted. A few Hudu fields have no place to live in Ascent yet — a company's parent company, a folder's description/icon and its company scoping, an article's permalink, a password's type, and a website's DNS/WHOIS monitoring toggles — so instead of disappearing, each is recorded as an unmapped entry in the run report for that record.

Cleaning up

Deleting a migration run removes its staging data, id map, logs and the stored encrypted credentials — use it once a migration is complete.