What types of assets can be migrated to HubSpot and what has to be rebuilt from scratch?

Website pages, blog posts (including categories, tags, authors, and metadata), forms, and media files like images and PDFs can be migrated into HubSpot. Templates, custom themes, WordPress plugins, database-driven content, e-commerce functionality, multi-step forms, and gated content with login systems must be rebuilt from scratch.

Blog content is the most straightforward migration. HubSpot offers a WordPress Connect feature that pulls posts via REST API, preserving titles, SEO titles, authors, publish dates, and metadata. Standard web pages transfer at the content level, but their layouts get recreated using HubSpot's drag-and-drop editor or custom-coded modules. Media files (images, documents) upload to HubSpot's file manager. The rebuild requirement applies to anything that relied on platform-specific code: WordPress themes cannot be lifted into HubSpot, so visual design gets recreated in HubSpot's template language. Plugin functionality (contact forms, popups, analytics tracking, chat widgets) gets replaced by HubSpot's built-in equivalents. Custom functionality like calculators, configurators, or member portals needs development work in HubSpot's environment.