Migrate from Simple Sales Tracking to HighLevel

Simple Sales Tracking contacts map directly to HighLevel contacts. Standard fields including name, email, phone number, address, and job title transfer as-is to the corresponding HighLevel contact fields. Any custom properties attached to contacts in Simple Sales Tracking migrate to HighLevel contact custom fields specifically — not opportunity custom fields — to maintain person-level data scoping and ensure these fields appear correctly in Smart List filters that evaluate contact attributes.

Simple Sales Tracking companies map to HighLevel companies. Company name, domain, industry, employee count, and annual revenue fields transfer directly. Phone and address fields map to HighLevel's company phone and address fields respectively. Parent-child company relationships in Simple Sales Tracking map to HighLevel's company hierarchy feature if that configuration is enabled in the destination account.

Simple Sales Tracking leads do not have a separate object in HighLevel — they merge into the Contact object. We preserve lead status by adding a tag (e.g., 'Lead') and setting a custom contact field for lead_source. Any lead-specific custom fields become contact custom fields in HighLevel.

Simple Sales Tracking opportunities map to HighLevel opportunities (deals in a pipeline). Deal name, amount, stage, close date, and owner transfer. Stage names require value mapping against HighLevel pipeline stages. Probability values transfer if Simple Sales Tracking stores them; otherwise we set defaults per stage in HighLevel.

Each Simple Sales Tracking pipeline becomes a HighLevel Pipeline. Pipeline-level settings like stage order and probability percentages map to HighLevel pipeline configuration. If Simple Sales Tracking uses multiple pipelines, we create corresponding pipelines in HighLevel — a 1:N mapping in favor of HighLevel's multi-pipeline model.

Stage names map value-by-value from Simple Sales Tracking to HighLevel pipeline stages. Stage display order transfers. Probability and forecast category values apply per HighLevel's stage configuration. HubSpot-style stage-entered timestamps are not available in Simple Sales Tracking — no historical stage timing to preserve.

Simple Sales Tracking tasks map directly to HighLevel tasks, transferring subject line, description text, due date, assigned user, and completion status. Task status values (pending, completed) map to corresponding HighLevel task status field values. Overdue task calculations recalculate automatically based on due date in HighLevel — no historical overdue flags transfer since HighLevel computes overdue status dynamically from the current date.

Simple Sales Tracking appointments map to HighLevel calendar events. Event title, start time, end time, location, assigned user, and linked contact or opportunity transfer. Recurring appointment patterns in Simple Sales Tracking do not have a native HighLevel equivalent — single occurrences migrate; recurring rules are documented for manual setup.

Simple Sales Tracking notes map directly to HighLevel notes, preserving the full note body text, original creation date, and author attribution. Notes linked to contacts or opportunities in Simple Sales Tracking re-link to the corresponding migrated records in HighLevel using API relationship IDs captured during the export phase. If a linked record was not found during migration, the note attaches to a fallback contact with a note indicating the broken relationship.

Simple Sales Tracking files attached to contacts, companies, or opportunities re-upload to HighLevel's document storage and link to the corresponding record. File names and upload timestamps are preserved. Files exceeding HighLevel's attachment size limits are flagged before the full migration runs.

Custom fields in Simple Sales Tracking attached to sales records need type-aware assignment in HighLevel. If the field tracks person-level data (e.g., preferred contact method, birthday), it becomes a contact custom field. If it tracks deal-level data (e.g., contract type, renewal date), it becomes an opportunity custom field. We determine type by inspecting the field's usage across records in Simple Sales Tracking.

Custom pipeline stages in Simple Sales Tracking map to HighLevel pipeline stages. Custom lead sources map to HighLevel tags on contacts. Tags preserve the source attribution without requiring a custom field — Simple Sales Tracking's lead_source property becomes a 'Source: [value]' tag on the contact.

Simple Sales Tracking's commission tracking fields (per rep or per deal) have no direct HighLevel equivalent. We migrate these as custom fields on the opportunity — typically a number field for commission amount or percentage. Your team assigns the field to the correct record type in HighLevel.

Simple Sales Tracking users and owners resolve by email match against HighLevel users. Unmatched users are flagged before migration. Records belonging to unmatched owners are assigned to a fallback user or held in a queue for your HighLevel admin to resolve before the full run.

Contacts created via Simple Sales Tracking's web-to-lead form integration carry a lead source tag in HighLevel. Form field values that were captured as custom fields map to contact custom fields. The web-to-lead integration itself needs to be rebuilt using HighLevel's form builder and connected to your website post-migration.