Migrate from StreetSmart to Salesforce Sales Cloud

StreetSmart customer contact records map directly to Salesforce Contact. StreetSmart contact name, email, phone, address, and job title translate to Salesforce FirstName, LastName, Email, Phone, MailingAddress, and Title. Salesforce requires AccountId on Contact — StreetSmart customers without a primary company association attach to a default 'Unassigned Account' or get linked based on a parent-company identifier.

StreetSmart company and business-profile records map to Salesforce Account. Name, website, industry, employee count, annual revenue, and billing address on StreetSmart translate to Account.Name, Website, Industry, NumberOfEmployees, AnnualRevenue, and BillingAddress. StreetSmart parent-company or franchise hierarchy maps to Account.ParentId when the hierarchy is defined.

StreetSmart work orders are the primary operational record — they include job description, scheduling window, assigned technician, status, priority, and service type. In Salesforce, these map to Case with custom fields capturing StreetSmart-specific attributes like service_type__c, scheduled_start__c, scheduled_end__c, technician_id__c, and route_sequence__c. Case Origin, Status, Priority, and Description map from StreetSmart work order fields.

StreetSmart tracks service history per customer location or equipment asset — each service visit, repair, and maintenance record. In Salesforce, Asset stores equipment or product history linked to an Account. Service events map as Case records linked to the Asset, preserving the original service date, description, and technician who performed the work. Serial number, install date, and status from StreetSmart become Asset.SerialNumber, InstallDate, and Status.

StreetSmart inventory records — parts, materials, equipment — do not have a direct Salesforce equivalent at the standard-object level. We map StreetSmart inventory items to Salesforce Product2 for items that map to billable products, and create a custom Inventory_Item__c object for parts and materials that are internal to field operations. SKU, unit cost, quantity on hand, and reorder level from StreetSmart map to custom fields on each target object.

StreetSmart scheduling records capture job windows, technician assignments, route order, and travel time. Salesforce does not have a native scheduling object in core Sales Cloud. We map scheduling data as custom fields on Case (Scheduled_Date__c, Technician__c, Route_Sequence__c, Travel_Time_Minutes__c) and deliver a Scheduler_Config__c reference object with exported route sequences for rebuilding in Salesforce Scheduler or an AppExchange field-service app.

StreetSmart time tracking entries and activity logs — technician time on job, travel, breaks — map to Salesforce Task with custom fields for hours_spent__c, activity_type__c (on-site, travel, administrative), and start_time__c. The original timestamp, technician owner, and linked Case or Contact are preserved so service-activity reports in Salesforce show the full labor history.

StreetSmart captures electronic signatures for work-order confirmation. Salesforce has no native signature field. We map the signature image or hash as Signature_Data__c (Long Text Area) on Case and re-upload the original image file to Salesforce Files linked to the Case record, preserving the audit trail that the signature was collected and attached to the work order.

StreetSmart attachments — photos, forms, documents, and signature images — migrate to Salesforce Files (ContentDocument/ContentVersion model). Files are re-uploaded to Salesforce and linked to the corresponding Account, Contact, Case, or Asset record using ContentDocumentLink. Original filenames and upload timestamps are preserved in ContentVersion metadata.

StreetSmart captures GPS coordinates for customer locations, technician routes, and job sites. Salesforce custom geolocation fields (Location__c of type Geolocation) store latitude and longitude on Account or Asset. We map StreetSmart location coordinates to Location__Latitude__s and Location__Longitude__s for use in Salesforce Map, Einstein Analytics, or any AppExchange mapping tool your team enables.

StreetSmart customizable forms generate custom fields per deployment — these have no Salesforce native equivalent. We inventory every StreetSmart custom form field during discovery, create matching Salesforce custom fields (suffix __c) on the appropriate object (Account, Contact, Case, or Asset), and apply the correct data type (text, picklist, number, date, checkbox). Custom form definitions are exported as a rebuild reference document.

StreetSmart team member and technician records map to Salesforce User. Owner resolution happens by email match — StreetSmart technician email addresses are matched against Salesforce User email. Unmatched technicians are flagged before migration; the team either creates Salesforce User records for them first or assigns their records to a fallback owner so no Case or Task lands without an owner.

StreetSmart customer portal accounts do not have a direct Salesforce equivalent. We map portal user records to Contact with a flag portal_enabled__c and export the portal user list and permission settings as a rebuild reference for Salesforce Experience Cloud or your chosen portal solution. The customer contact data migrates cleanly; the portal access configuration must be rebuilt.