About This Page
"I want to adopt HubSpot, but what should I do with my current WordPress site?" "Should I migrate to HubSpot CMS?" "I just want to use the forms..."
We answer frequently asked questions about website integration.
Common Requests
When You Have an Existing Site
- "I don't want to break my WordPress site"
- "Migrating to HubSpot seems like a lot of work"
- "I want to use HubSpot partially"
When Creating a New Site
- "Should I build it on HubSpot CMS?"
- "Which is better, WordPress or HubSpot?"
- "I want to consider future scalability"
Conclusion: You Don't Need to Force a Migration
The first thing to know is that you don't need to migrate your existing site to HubSpot CMS to use HubSpot.
"HubSpot = Build everything in HubSpot" → I have to migrate WordPress to HubSpot CMS!
You can use HubSpot for just "customer management & marketing." Website (WordPress) + HubSpot (CRM & MA) combination works fine
Three Options
There are three main patterns for the relationship between HubSpot and your website.
Pattern 1: Existing Site + Some HubSpot Features
The easiest approach. Keep your existing website as is and use only some HubSpot features.
Available features:
- Forms (inquiries, resource requests)
- Chatbots
- Pop-ups
- Tracking (visitor behavior analysis)
Benefits:
- No changes to existing site needed
- Very easy to implement (just embed a tag)
- Keep costs low
Pattern 2: Existing Site + HubSpot Blog
Keep your website as is, run only the blog on HubSpot CMS Hub.
Configuration example:
- Main site: WordPress (example.com)
- Blog: HubSpot (blog.example.com or example.com/blog)
Benefits:
- Full use of HubSpot's SEO features
- Content marketing and CRM are integrated
- Minimal impact on existing site
Pattern 3: Full Site on HubSpot CMS
Build the entire site on HubSpot CMS Hub.
Benefits:
- Everything is in HubSpot
- Smoothest CRM integration
- Full use of personalization features
Considerations:
- Migration costs involved
- Some design flexibility limitations
- Increased HubSpot dependency
Which Pattern Should You Choose?
Decision Flow
No → Go to Q3 (decide based on whether you'll focus on content marketing)
Yes → Consider Pattern 3 (rebuild on HubSpot CMS)
Pattern 1 (existing site + HubSpot features) or Pattern 2 (existing site + HubSpot blog)
Comparison Table
| Aspect | Pattern 1 | Pattern 2 | Pattern 3 |
|---|---|---|---|
| Ease of adoption | ◎ | ○ | △ |
| Impact on existing site | None | Minimal | Full migration |
| CRM integration | ○ | ◎ | ◎ |
| Content marketing | △ | ◎ | ◎ |
| Cost | Low | Medium | High |
Learn More
We cover website integration in detail across three articles.
1. Using WordPress and HubSpot Together
Answers the question "If using both, how do you divide roles?" Explains how to leverage the strengths of both WordPress and HubSpot together.
→ Using WordPress and HubSpot Together
2. Deciding Whether to Migrate to HubSpot CMS
Summarizes the criteria for "Should I migrate or stay as is?" Covers pros and cons of migration, including the option not to migrate.
→ Deciding Whether to Migrate to HubSpot CMS
3. Using Forms Only
For those who "just want to use HubSpot's form feature." Explains how to embed HubSpot forms in your existing site, plus benefits and considerations.
Benefits of Leveraging Your Existing Site
1. Lower Risk
Migrating to a new CMS often causes unexpected issues. Leveraging your existing site minimizes risk.
2. Gradual Adoption
"First just forms" "Then chatbots" "If effective, the blog too"—you can gradually expand HubSpot usage.
3. Don't Waste Your Investment
Leverage the cost and time already invested in your existing site. If something works well, there's no need to force a change.
Summary
Key points about HubSpot and website integration:
- Forced migration not needed: You can adopt HubSpot while leveraging your existing site
- Start gradually: Partial adoption like forms only, blog only
- Multiple options exist: Choose the optimal pattern for your situation
If you're unsure "what to do with your current site," we recommend starting with Pattern 1 (existing site + HubSpot features).