You could be using WordPress, Adobe Marketo Engage, Drupal, or any other CMS, the standardized process of understanding, preparing, and migrating your website and data to HubSpot CMS is the same. Take it as a blueprint.
Understanding the types of Assets that need to be transferred
The first step is to document all the assets and categorize them for easy understanding. Create a digital inventory that is subjected to move to HubSpot. You could use a paid tool or Google spreadsheet to document and share with team members who work with you on the migration project.
Here’s the list of assets and their properties to document
Pages: Website pages, landing pages, their content, design templates, link structures.
Emails: Document email layouts, templates, content, and take notes on subscription types that you want to replicate in HubSpot as well.
Workflows: Write steps, triggers, contact lists, workflow names, and each detail to set up workflows in HubSpot CRM.
Forms: If your forms are part of workflows and marketing campaigns, then save these as well and replicate those in HubSpot.
Domains and URLs
You can use tools such as Screaming Frog, Ahrefs, and Semrush to crawl your entire website and gather all accessible URLs. Export the URLs, metadata, canonicals, and other relevant information in the crawled data and save it into a spreadsheet.
Website Themes and Templates
Create a theme file if you want to continue with the existing theme and achieve the same in HubSpot. Ask the HubSpot developer to convert those themes into HubSpot Templates once the theme is customized or uploaded. Create custom modules to match your brand’s tone.
Users
If you have an existing CRM and want to continue with the same user permissions and accounts. Save each user’s record and permissions to avoid reworking all the user accounts.
Testing
HubSpot users can set up a Sandbox account and synchronize the assets. It is a safe environment for testing changes and running experiments before deploying them into a live production account.