Migrate from Sierra Interactive to HubSpot

Sierra's Lead object maps directly to HubSpot Contact. All standard lead fields (name, email, phone, address, lead source) transfer as HubSpot contact properties. The lead's original create date is preserved in a custom datetime property since HubSpot's standard Createdate is set at import time.

Sierra lead status values (New, Contacted, Qualified, etc.) map to HubSpot lifecycle stage values. A value-by-value mapping table is created during discovery. If Sierra uses statuses that don't map cleanly to HubSpot's predefined lifecycle stages, they migrate as a custom pick-list property on the contact.

Sierra Company records transfer as HubSpot Company records. Company name, domain/website, industry, and employee count map directly. Additional fields such as phone, address, city, state, and postal code also transfer. HubSpot's association model links companies to contacts; a contact without a primary company in Sierra lands as an unassociated HubSpot contact, and your team can link it to a company record manually after migration if needed.

Sierra deals map to HubSpot deals with pipeline and stage mapping. Each Sierra deal pipeline maps to a HubSpot deal pipeline. Stage names map value-by-value to HubSpot deal stage pick-lists. Deal amount, close date, and owner transfer directly. The deal's original create timestamp is preserved in a custom datetime property.

Sierra tasks (calls, follow-ups, phone tasks) transfer as HubSpot tasks. Task subject, due date, completion status, and owner are preserved directly. Completed tasks carry their original completion timestamp. Task type (call, email, SMS) maps to HubSpot's hs_task_type property. Associated notes or comments are preserved in the HubSpot task's notes field.

Sierra notes on leads or deals transfer as HubSpot engagement notes. Original note text, author, and create timestamp are preserved. Notes associated with a lead land on the corresponding HubSpot contact. Notes tied to deals attach to the HubSpot deal record.

Sierra's saved listings (listing IDs and property addresses a lead has bookmarked) have no native HubSpot equivalent. We create a custom multi-line-text or list-type property on the contact record to store saved listing data in a pipe-delimited or JSON-formatted string. Managers can use HubSpot's list filtering or a custom report to surface leads with saved listings.

Sierra Lead Ponds (virtual segmentation buckets) map to a custom pick-list property on the contact record. If the team uses Lead Ponds as dynamic routing groups, we also create static HubSpot contact lists that match the pond membership and update them via workflow after migration. Your admin chooses the approach during discovery.

Sierra Action Plans (automated email, SMS, voicemail, and task sequences) do not migrate as active automations. Individual action-plan events (emails sent, texts delivered, voicemails dropped, tasks created) transfer as HubSpot tasks and engagement history records so the contact's timeline reflects the sequence of outreach that occurred.

Sierra's lead source tags and tagging taxonomy map to a custom text or multi-checkbox property in HubSpot. Tags with consistent naming across the source system are consolidated into HubSpot's built-in contact property system where possible to leverage HubSpot's native filtering.

Sierra user records are resolved by email address against HubSpot user accounts. Unmatched owners are flagged before migration; your team either creates HubSpot users for them or assigns their records to a fallback HubSpot user. No record lands without a valid HubSpot owner.

Sierra saved searches (saved IDX search criteria per lead) have no HubSpot equivalent. We preserve the saved search URL or criteria string as a custom text property on the contact record for reference. Dynamic list behavior based on saved searches requires a HubSpot workflow to be designed and built post-migration.