What gets imported, and what should I check after import?

Everything in your documentation. Every article, in every format. Every element inside an article: headings, lists, callouts, tables, code blocks, screenshots, and embedded videos. Your folder and category structure comes over as it is. If it exists in your current docs, it comes across.

Do internal links still work after the import?

Yes. We rewrite your internal links so they point to the new article locations inside HappySupport. You do not end up with a pile of dead links aimed back at your old tool. Cross-references between articles keep working.

Are screenshots and videos kept?

Yes. Screenshots are imported as part of each article. Embedded videos come over too. We recommend to re-record your article then with HappySupport's AI Article Recorder so your screenshots look better and stay aligned with our actual app.

What about HubSpot imports?

If you are importing from HubSpot, your category and subcategory structure is preserved. A few things to check:

• Private articles: Private HubSpot content may be missing or inaccessible after import. Review your article list to confirm everything you expected is there.
• Article dates: Most HubSpot articles show the import time as their last-modified date rather than their actual edit date. HubSpot does not provide reliable per-article timestamps.

What is the first thing to do after import?

Review your imported content to make sure everything came through as expected. If you want freshness monitoring, connect your documentation source or code repository. Once connected, our AI agents can flag which articles your recent changes have already made out of date. You get a punch list of stale guides on day one, instead of finding them later through customer complaints.

Can I find gaps in my documentation right away?

Yes, if you have support history. Share your historic support tickets and we can analyze them against your imported articles. The tickets show the questions customers actually ask. Lining those up against your content surfaces the gaps: the topics people need help with that your docs do not cover yet. You start improving from real demand, not guesswork.