Migrate from CASH to HighLevel

CASH contacts migrate directly to HighLevel contacts. HighLevel stores contacts with a flat property set; all CASH standard fields (name, email, phone, address) map 1:1. Custom contact properties map as HighLevel custom fields — the field data type in CASH determines the field type created in HighLevel (text, number, picklist, date).

CASH companies map to HighLevel companies. Company name, domain, industry, employee count, and annual revenue transfer as standard HighLevel company fields. Multi-company associations (if CASH supports a contact linked to multiple companies) map to HighLevel's secondary company link feature with a primary designation preserved from the CASH record.

CASH deals migrate as HighLevel Opportunities. Deal name, amount, expected close date, owner, and stage all transfer. CASH stage names map to HighLevel pipeline stage values — if CASH uses a single-pipeline model, a default HighLevel pipeline is created; if CASH has named pipelines, each becomes a separate HighLevel pipeline.

Each CASH deal stage name maps to a corresponding HighLevel pipeline stage. Probability percentages attached to stages in CASH are stored as stage-level notes in HighLevel since HighLevel sets probability per stage in the pipeline builder. Stage order and display sequence are preserved.

CASH call logs, logged emails, and meeting records migrate as HighLevel Tasks. Original timestamps, call duration (if captured), owner, and associated contact/company link are preserved. HighLevel stores these under the contact's activity feed and the Tasks list view. This includes any notes added during the call or meeting that were logged in CASH's activity record.

CASH notes migrate as HighLevel notes attached to the relevant contact or company record. Note body text transfers with original create date and owner preserved. HighLevel notes support plain text — any rich-text formatting from CASH is flattened to plain text to avoid rendering issues.

Any CASH custom property on contacts that has no direct HighLevel equivalent is created as a HighLevel custom field on the Contact object. Field type is matched: CASH text → HighLevel text, CASH picklist → HighLevel dropdown, CASH number → HighLevel number. Custom field API names in HighLevel follow the platform's naming rules.

CASH custom properties on companies that do not have a HighLevel standard equivalent are created as custom fields on the Company object. Type-aware mapping applies — date fields, numeric fields, and pick-list fields each get the matching HighLevel field type.

CASH deal-level custom fields migrate as custom fields on the HighLevel Opportunity object. This preserves any deal-specific metadata such as deal source, product line, or internal tracking IDs that CASH stored as custom properties. All custom field types are matched type-by-type during migration to ensure data fidelity in HighLevel.

CASH owner and user records are resolved by email against HighLevel users. If a CASH owner email matches an existing HighLevel user, records are assigned to that user. If no match exists, unmatched owners are flagged before migration and you choose to either create the user in HighLevel first or assign records to a fallback owner.

CASH contact tags migrate as HighLevel tags. Tags are a flat namespace in HighLevel — if CASH uses hierarchical tag groups, we flatten them to a single tag string per contact using a separator convention you define, so the tag data is searchable after migration.

CASH file attachments linked to contacts, companies, or deals are downloaded and re-uploaded to HighLevel's file storage, then linked back to the migrated record. File size limits apply — HighLevel's file upload limit is 50MB per file; larger files are flagged for manual handling.