Migrate from StreetSmart to Freshsales

StreetSmart contact records map directly to Freshsales Contact objects. Freshsales Contact requires an AccountId (lookup to Account); StreetSmart contacts without a primary company receive a default placeholder account or get mapped as Freshsales Leads based on lifecycle status. If the contact has activity history but no company link, it is flagged for review to ensure correct Lead status assignment in Freshsales.

StreetSmart contacts marked as inactive or without engagement history route to Freshsales Lead rather than Contact. This split preserves Freshsales' distinction between raw leads and nurtured contacts, and prevents Freshsales lifecycle stage assignment on unqualified records. Records that lack a recent email, call, or meeting are automatically flagged as inactive, ensuring they do not consume Freshsales' contact tier quotas and remain available for reactivation if needed.

StreetSmart company records map to Freshsales Account. Freshsales Accounts support parent-child hierarchies via a Parent Account lookup. StreetSmart company associations (one-to-many contacts) map as Account-Contact relationships in Freshsales, preserving the primary-company designation. If a StreetSmart company has multiple locations, each location can be represented as a separate Account under the parent, allowing granular territory reporting and per-site deal tracking within Freshsales.

StreetSmart service records and deal entries transform to Freshsales Opportunity. Freshsales Opportunity requires a required AccountId and optional ContactIds via Opportunity Contact Roles. Pipeline and stage assignment follows the first matching Freshsales pipeline stage based on StreetSmart service status. If no stage matches, a default stage is used and flagged for manual review.

StreetSmart pipeline stages map to Freshsales pipeline stages via value-by-value mapping. Each StreetSmart stage receives a corresponding Freshsales stage name, probability percentage, and forecast category. We preserve the original stage-entry timestamp as a custom datetime field for historical continuity. This mapping ensures that deal history reflects the original progression, allowing managers to review historical win/loss trends without manual re-entry.

StreetSmart call logs, emails, and meeting records map to Freshsales Tasks and Events. Calls and emails become Tasks with Type='Call' or Type='Email'. Meetings become Events with start/end times preserved. Original activity timestamps and owner assignments carry over via custom fields.

Every StreetSmart custom property requires a corresponding Freshsales custom field created before migration. Field types are inferred from StreetSmart data (text, number, date, picklist). Picklist values are mapped value-by-value to Freshsales picklist options. Custom fields are scoped to the appropriate Freshsales module (Contact, Account, or Opportunity).

StreetSmart owner IDs resolve to Freshsales users by email match. Unmatched owners are flagged before migration; you either invite them to Freshsales first or assign records to a fallback owner. No record lands in Freshsales without a valid OwnerId. If a Freshsales user account is created after the initial migration, a delta-run updates OwnerId references to reflect the new user.

StreetSmart file attachments on contacts, companies, or deals are downloaded and re-uploaded as Freshsales Attachments. File size limits apply (Freshsales default 20MB per file for most plans). Inline images embedded in StreetSmart notes are extracted and rehosted separately. During re-upload, we preserve the original file name, MIME type, and upload timestamp, and we log each attachment in the migration audit trail for traceability.

StreetSmart internal record IDs are stored as a custom field on each Freshsales record for traceability, delta-run de-duplication, and cross-referencing. This allows FlitStack to identify which Freshsales record corresponds to which StreetSmart record during delta-pickup runs. We also use this ID mapping to generate reconciliation reports that compare record counts and field completeness between the source and destination after each migration phase.