Migrate from CASH to HubSpot

HubSpot Contact is the primary record for individuals. FlitStack maps every CASH contact property to a corresponding HubSpot contact property, creating any missing HubSpot properties as custom fields before the import. CASH contacts without email are imported with an email placeholder and flagged for review.

HubSpot Company maps directly from CASH company records. Company name, domain, industry, employee count, and annual revenue all have HubSpot native equivalents. Parent-child company hierarchies in CASH map to HubSpot's Parent Company field, requiring sequential migration to resolve foreign keys.

CASH deals migrate to HubSpot Deals tied to the target HubSpot pipeline. Each CASH pipeline maps to a corresponding HubSpot Pipeline object, with stage names mapped value-by-value to HubSpot stage values scoped to that pipeline. During migration, fields in CASH are transferred to HubSpot as properties, preserving stage data. If a CASH stage name does not match a HubSpot stage, FlitStack flags it for naming before import.

HubSpot allows multiple named pipelines per portal, each with independently scoped stage pick‑lists. FlitStack reads CASH pipeline names and creates matching HubSpot Pipelines before migrating deal records. Each pipeline's stage values are defined with probability weights and forecast categories. When a deal moves to a stage, HubSpot updates the probability based on the stage's settings. FlitStack also maps stage‑level properties, such as stage‑entered timestamps, to ensure continuity of deal history.

CASH stage names are mapped value-by-value to HubSpot stage names within the target pipeline. Probability weights and forecast category assignments are applied per stage based on HubSpot's stage configuration. CASH stage-entered timestamps are preserved as custom datetime fields. During migration, fields in CASH are transferred to HubSpot as properties, preserving stage data. If a CASH stage name does not match a HubSpot stage, FlitStack flags it for naming before import.

HubSpot has no native equivalent to CASH lifecycle or lead-status fields. FlitStack creates a lifecyclestage custom pick-list property on the Contact object in HubSpot and maps the source values exactly. If the source uses multiple lifecycle-like fields, each is mapped individually.

HubSpot engagement objects mirror CASH activity logging. Calls, emails, meetings, and notes migrate with original timestamps, owner attribution, and parent-record links preserved. HubSpot's engagement API requires activity associations to be set during import, so records are sequenced accordingly. Each (call, email, meeting, note) maps to HubSpot object, with data transferred. Owner is matched to a HubSpot user; unmatched get an owner. Timestamps kept in UTC and shown in time zone.

CASH custom fields on any object require pre-creation of matching HubSpot custom properties before data import. FlitStack reads CASH field type metadata and creates HubSpot equivalents (single-line text, multi-line text, number, date, pick-list, etc.). Field type mismatches are flagged and resolved before migration.

CASH owner IDs are resolved by email against HubSpot users. Unmatched owners are flagged before migration — the team either invites them to HubSpot first or assigns their records to a fallback HubSpot user. No record lands without a resolved HubSpot owner.

CASH file attachments linked to contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. File associations to records are recreated in HubSpot using the Files API. Large files (>25MB) are flagged for manual review due to HubSpot's default file size limit.

CASH N:N contact-to-company associations merge into HubSpot's primary Company association plus Contact-to-Company secondary links. FlitStack migrates the most-recently-modified company as the primary association and surfaces additional companies as secondary links. The full association graph is preserved for admin review. During migration, each contact's company associations are evaluated; the most recently updated company becomes primary, others are added as secondary links. This preserves the relationship hierarchy for admin review in HubSpot.

If CASH tracks a marketing-contact distinction, HubSpot has no native equivalent that preserves the billing semantics. FlitStack preserves the flag as a custom Boolean property on the contact record for reference, but HubSpot's marketing-contact billing is controlled by list membership and portal-level settings, not by a data field.