Migrate from Spiro to HubSpot

Spiro contacts map directly to HubSpot contacts. HubSpot requires an email address for contact creation; Spiro contacts without emails are flagged before migration and can be assigned a placeholder or excluded based on your preference. If duplicate email addresses exist across records, FlitStack merges them using Spiro's contact ID to preserve all associated activity and relationship data.

Spiro companies map directly to HubSpot companies. HubSpot supports company hierarchies via parent-company association — if Spiro uses parent-child company relationships, those map to HubSpot's parent company field on the company record. If multiple Spiro companies share the same name, FlitStack resolves duplicates using Spiro's company ID and associates them with the appropriate HubSpot company, ensuring that each business entity remains distinct.

Spiro opportunities map to HubSpot deals. The opportunity name becomes the deal name, amount maps directly, and close date transfers as the deal close date. Owner resolution happens by email match to HubSpot portal users. Spiro opportunity stages are mapped to the designated HubSpot deal stage, and any custom fields on the opportunity become HubSpot deal custom properties, preserving the full opportunity context in the new system.

Spiro custom fields on contacts (beyond standard fields like name, email, phone) require HubSpot custom properties to be pre-created in the portal before migration. FlitStack delivers a custom property creation plan based on Spiro's field inventory. The plan includes data type mapping, default values, and pick-list options so your HubSpot admin can provision each property accurately and avoid import mismatches.

Spiro company-level custom fields migrate as HubSpot company custom properties. Data type mapping applies: text fields map to single-line text, number fields to number properties, date fields to date properties, and pick-list fields to single-option or multi-option enumeration properties. If a Spiro pick-list contains values not yet defined in HubSpot, FlitStack flags them so your team can create the corresponding options before import to prevent data loss.

Spiro opportunity custom fields map to deal custom properties in HubSpot. If Spiro tracks specific product lines or manufacturing identifiers on opportunities, those fields are created as HubSpot deal properties before migration begins. These custom deal properties can be included in HubSpot's reporting views, deal dashboards, and automation triggers, allowing your team to maintain visibility into product-specific metrics after the transition.

Spiro stores an owner on every contact, company, and opportunity. Owners resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — teams either invite them to the HubSpot portal or assign records to a fallback HubSpot user.

Spiro auto-captured activities map to HubSpot engagement records. Call logs become HubSpot calls, emails become HubSpot email engagements, and notes become HubSpot notes. Original timestamps and associated contacts or companies are preserved in the migration. Engagement records also retain the owner information from Spiro, and any linked activity details such as call duration or email subject lines are transferred to the corresponding HubSpot engagement properties.

Spiro meeting records with subject, date, time, and associated contacts map to HubSpot meetings. The meeting link or location field from Spiro migrates to the HubSpot meeting body or a custom property depending on format. If the Spiro meeting includes attendees beyond the primary contact, FlitStack records those attendees in the HubSpot meeting's invitees list, preserving the full participant context.

Spiro's relationship intelligence data — including last contacted date, contact frequency, and relationship score — does not have a native HubSpot equivalent. FlitStack preserves these values as custom contact properties for reference after migration. These custom properties can be used in HubSpot lists, workflows, and reports to trigger follow-ups based on historical engagement, allowing your team to maintain relationship context without rebuilding data manually.

Spiro links contacts to companies (a contact can be associated with multiple companies). HubSpot handles primary company association via the contact's associated company field, with secondary associations managed through the company contact associations feature. If a contact has multiple primary relationships in Spiro, FlitStack maps the most recent or highest-revenue company as the primary HubSpot association, while preserving other links for reference.

Spiro links opportunities to contacts as part of its relationship model. These links migrate as HubSpot deal-contact associations — if Spiro tracks the contact's role on the opportunity, that role is preserved as a contact role on the deal. Contact roles such as decision maker, influencer, or technical lead are transferred to HubSpot, enabling accurate deal forecasting and targeted communication workflows based on each stakeholder's function.