Migrate from FastTrack to HighLevel

FastTrack contacts map directly to HighLevel contacts. FastTrack stores the company as a nested company_id on the contact; FastTrack AI resolves this by creating the Organization in HighLevel first, then linking each contact to that Organization via organizationId. Tags on the FastTrack contact migrate as-is into HighLevel's tags array.

FastTrack company records map to HighLevel Organization records. FastTrack stores domain, industry, employee count, and address fields — these map to HighLevel's organization field equivalents (website, industry, numberOfEmployees, address fields). Multi-company affiliations that FastTrack supports via a separate junction table collapse to a primary OrganizationId on each contact in HighLevel.

FastTrack deals map to HighLevel Opportunities. The FastTrack deal amount maps to HighLevel's monetaryAmount field. The FastTrack pipeline and stage on the deal determine which HighLevel pipeline the opportunity is assigned to and which stage label is used — stage names are mapped value-by-value at migration time based on a pre-agreed mapping table.

FastTrack pipelines are migrated as HighLevel Pipelines. Each FastTrack pipeline creates a corresponding HighLevel pipeline with the same name and a default set of stages. FastTrack stage names are applied to HighLevel stage entries in order. If the FastTrack pipeline uses custom stage probabilities, those are stored as metadata and applied manually after migration during the configuration pass.

FastTrack tags are flat string tags on contact records. These migrate as-is into HighLevel's tags array on each contact. Tags applied by FastTrack automations (if the contact was touched by a workflow) migrate as static tags — the automation logic is not transferred, but the resulting tag state is preserved so contact segmentation is intact on day one in HighLevel.

FastTrack engagement records (calls, emails, meetings, notes) with timestamps, owners, and linked record IDs are mapped to HighLevel Tasks (for calls and emails) and Notes (for note-type engagements). Original timestamps are preserved in a custom datetime field on the HighLevel task so historical activity context is not lost. FastTrack meeting records with duration and attendees map to HighLevel Tasks with type=Meeting.

FastTrack custom objects (defined via the FastTrack GraphQL API with custom field schemas) map 1:1 to HighLevel Custom Objects. Each custom object's fields are mapped to HighLevel Custom Object fields with type-aware transformations — string to text, number to number, date to date, pick-list to pick-list. Custom object relationships that FastTrack stores as foreign-key IDs are created as relationship fields in HighLevel's Custom Object schema.

FastTrack custom fields on standard objects migrate to HighLevel custom fields on the equivalent object. Each FastTrack custom field definition is read from the GraphQL schema response, its data type is identified, and a corresponding HighLevel custom field is created in the destination sub-account before the data migration writes begin. Multi-select pick-list fields from FastTrack become multi-select custom fields in HighLevel.

FastTrack ownerId on deals and contacts is resolved by email match against the HighLevel user list. FlitStack AI retrieves the FastTrack user list (name and email) and the HighLevel user list, then creates a lookup table. Records with unmatched owners are flagged before migration; the customer assigns a fallback HighLevel user before the full run commits so no record lands without an owner.

FastTrack automation rules (workflow triggers and actions defined in FastTrack's automation builder) do not migrate because HighLevel's Workflow Builder uses a completely different trigger-action model. FlitStack AI exports all FastTrack workflow definitions as JSON for your HighLevel admin to reference during rebuild. The export includes trigger events, conditions, and action sequences so the rebuild mirrors the original logic.

FastTrack file attachments linked to contacts, companies, or deals are downloaded and re-uploaded to HighLevel's file storage. File size limits apply (HighLevel's per-file upload limit is 25MB for direct upload; larger files use a different upload method). File names and original upload timestamps are preserved as metadata on the HighLevel attachment record.

FastTrack's internal record IDs are stored in a custom field (Source_ID__c) on every migrated record in HighLevel. This serves two purposes: traceability back to the source FastTrack record, and de-duplication support during delta-pickup runs where FastTrack IDs allow FlitStack to identify and update records already migrated rather than creating duplicates.