Migrate from Zoho Marketing Plus to HubSpot

Zoho contacts map directly to HubSpot contacts. Email is required on both platforms — records without an email address are flagged before migration and resolved by your team. The primary account link migrates as the Company association on the HubSpot contact record.

Zoho leads and contacts are separate modules; HubSpot uses a single Contact object with lifecycle_stage. We map all Zoho leads to HubSpot contacts, setting lifecycle_stage based on Zoho lead status (New → Subscriber, Working → Lead, Converted → Customer). Your admin configures the exact stage-mapping table before migration runs.

Zoho accounts map to HubSpot companies. Parent-account hierarchies in Zoho migrate as HubSpot parent-company lookup fields, preserving the original hierarchy depth. Multi-account associations on a single contact collapse to one primary company on HubSpot; additional accounts are stored as secondary company links. During migration, we validate that each primary company exists in HubSpot before linking contacts, ensuring foreign-key integrity and preventing orphaned records.

Zoho deals map directly to HubSpot deals with pipeline name, stage, amount, close date, and owner transferred. Each Zoho pipeline maps to a HubSpot pipeline, and stage names, probabilities, and forecast categories are mapped value-by-value against your HubSpot pipeline configuration. We verify each target pipeline and stage exist before moving deal data, preventing deals from landing in undefined pipelines and ensuring stage probabilities align with your sales process.

Zoho's product catalog and line-item associations on deals do not have a native HubSpot equivalent. We migrate product names, SKUs, quantities, and unit prices as a custom HubSpot object; deal-level product associations become records in that custom object linked to the deal via a lookup property.

Zoho campaigns map to HubSpot campaigns preserving campaign name, type, status, start and end dates, and budget information. Campaign member associations on contacts migrate as HubSpot campaign membership records, with UTM parameter data preserved in a custom campaign property for attribution continuity.

Zoho tasks, calls, and events migrate as HubSpot engagements on the associated contact or company timeline. Call logs migrate with duration and outcome; meetings migrate with start/end times and location; notes migrate as HubSpot notes with original timestamps and owner attribution preserved.

Zoho custom modules migrate as HubSpot custom objects on Enterprise plans. Custom field types (pick-list, multi-select, date, numeric, checkbox) map to their HubSpot equivalents. Modules with N:N lookups to other modules require a HubSpot junction object — we surface this in the pre-migration schema plan and your admin creates the destination-side schema.

Zoho attachments on records are downloaded and re-uploaded to HubSpot Files, linked back to the original record. Files attached to multiple Zoho records are uploaded once and linked to each associated HubSpot record. Standard HubSpot file-size limits (25MB per file) apply.

Zoho users are matched to HubSpot users by email address. Unmatched Zoho users are flagged before migration — your team either creates HubSpot user accounts for them first or assigns their records to a fallback HubSpot owner. No record lands without a valid HubSpot owner.

Zoho tags on contacts, accounts, and deals have no native HubSpot equivalent. We preserve tag values as a multi-select text property on the HubSpot record (Tags__c) so the data is accessible for segmentation — your team can rebuild dynamic lists or workflows from this property after migration.

Zoho notes with body text, timestamps, and owners migrate as HubSpot notes on the associated contact or company timeline. Rich-text formatting in Zoho notes is converted to plain text to avoid rendering issues in HubSpot's timeline note format. If a note contains embedded images, the image URLs are preserved as hyperlinks within the note body, ensuring that reference links remain functional after migration.