Migrate from TeamSystem CRM to HubSpot

TeamSystem custom fields require HubSpot custom property pre-creation

HubSpot requires custom properties to be created in Settings before records can import values into them. TeamSystem's custom fields have no enforced naming convention, so each field must be audited, typed (text, number, pick-list), and created individually in HubSpot before the migration run. Teams with more than 50 custom fields should budget extra planning time for this step — property creation is sequential per type, and pick-list values need to be mapped one-by-one to HubSpot's pick-list format. FlitStack delivers a property creation checklist as part of the migration plan.

Opportunity category-to-pipeline mapping requires pre-built HubSpot pipelines

HubSpot deal pipelines are first-class objects — each pipeline must exist before a deal can be assigned to it. If TeamSystem uses opportunity categories or types to group deals by business unit or product line, each category becomes a separate HubSpot pipeline. Teams with five opportunity types in TeamSystem end up needing five pipelines in HubSpot, each with its own stage configuration. We deliver a pipeline design plan before migration so the HubSpot admin can pre-create the structure; deals cannot land in the correct pipeline without it.

Activity associations require re-link after import via HubSpot's association API

HubSpot engagements (calls, emails, meetings) store their association to contacts, companies, and deals via an association object rather than a foreign key on the engagement itself. TeamSystem activity logs reference the parent record ID directly. During migration, activities are imported first, then re-associated using HubSpot's bulk association endpoint. If the parent contact or company ID changes during import (due to de-duplication), associations can break — we validate association integrity after import and re-link any orphaned activities.

HubSpot lifecycle_stage does not exist in TeamSystem — manual assignment or historical inference needed

HubSpot's lifecycle_stage property drives marketing contact billing and is required for lead routing into the correct marketing nurture track. TeamSystem does not have an equivalent native property, so migrating historical contacts without a lifecycle value means they land as blank. Teams that want lifecycle stage continuity must define a mapping rule (e.g., opportunity stage = closed won maps to 'Customer') or accept manual assignment post-migration. We surface this as a migration plan decision before the run.

Multi-currency amounts in TeamSystem require currency conversion before HubSpot import

TeamSystem Enterprise supports multi-currency opportunities with per-record currency codes. HubSpot stores deal amounts as a single decimal field without a native currency property in the base CRM object. We extract the currency code as a custom property and apply the conversion rate at migration time using a rate table agreed upon with the client. Currency divergence between TeamSystem and HubSpot's base currency must be resolved before records land or reports will be inaccurate.