Migrate from StreetSmart to HighLevel

This is a direct 1:1 mapping for contacts. HighLevel mandates a primary CompanyId on every contact, so any StreetSmart contact that lacks a linked company is linked to a default placeholder company record or is remapped according to a primary‑company selection rule you provide. This ensures that each contact in HighLevel has a valid parent company, preventing orphaned records and maintaining referential integrity throughout the migration.

This is a direct 1:1 mapping for companies. StreetSmart parent‑/subsidiary hierarchies map to HighLevel’s Parent CompanyId field, preserving the original corporate structure. When a single StreetSmart contact references multiple companies, the primary company becomes the HighLevel primary CompanyId, while any secondary companies are recorded as tags or custom‑field entries, ensuring no relationship data is lost. All company records are loaded before contacts to satisfy referential integrity checks.

StreetSmart jobs become HighLevel Opportunities. Job status (Scheduled, In Progress, Completed, Cancelled) maps to a custom Opportunity field (Job_Status__c) with value‑by‑value mapping to align with your pipeline stages. Job type is stored as a custom pick‑list (Job_Type__c), and line items become Opportunity Products with quantity and price. Original timestamps are kept as custom datetime fields, and you can optionally create a Service Record custom object for rich technical data.

If your StreetSmart jobs carry rich technical data (e.g., service history, technician notes, equipment serial numbers tied to the job), we recommend a Custom Object named 'Service Record' in HighLevel to avoid bloating the Opportunity record. This requires pre-creation of the object schema in HighLevel before migration.

StreetSmart assets have no direct HighLevel equivalent. We create a Custom Object named 'Asset' with custom fields for serial number, location, maintenance schedule, and linked contact/company lookups. The Asset-to-Contact relationship is stored as a custom lookup field on the Asset object.

Estimates translate to Opportunities in the earliest pipeline stage (e.g., 'Quote Sent'). Estimate total and line items map to Opportunity Amount and Products. If the estimate converts to a job in StreetSmart, the corresponding Opportunity advances to the appropriate stage automatically during migration.

Every StreetSmart custom property (per-contact, per-company, per-job, per-asset) is recreated as a HighLevel Custom Field. Pick-list values are mapped one-by-one. Multi-select StreetSmart properties become HighLevel multi-select fields. Custom field API names are auto-generated by HighLevel and stored in our mapping manifest for reference during rebuild.

StreetSmart notes attach to the parent object in HighLevel — Contact, Company, Opportunity, or Asset — preserving the original body text, timestamps, and owner. Attachments are re-uploaded to HighLevel Files and linked to the parent record. File size limits apply (HighLevel's standard file size cap).

StreetSmart owner IDs are matched to HighLevel users by email address. Unmatched owners are flagged before migration commits; your team either invites them to HighLevel or assigns records to a fallback user. No record migrates without a resolved HighLevel owner.

StreetSmart tickets that are separate from jobs become a 'Ticket' Custom Object in HighLevel with fields for subject, status, priority, and description. Tickets linked to jobs reference the migrated Job (Opportunity) ID via a custom lookup field. HighLevel's inbox routing for tickets requires a separate workflow to be configured post-migration.