Migrate from StreetSmart to HubSpot

StreetSmart students map directly to HubSpot Contacts. Each student record carries personal info, email, phone, and program enrollment status. The HubSpot Contact becomes the primary record for the student-person entity. Enrollment metadata (program name, cohort, completion date) migrates as custom properties on the Contact record.

StreetSmart's nested enrollment object (program_id, start_date, completion_date, status, skill_badges) merges into multiple custom properties on the HubSpot Contact: Program_Name__c, Enrollment_Date__c, Completion_Date__c, Completion_Status__c, and Skill_Badges__c (multi-select). This preserves the enrollment timeline without requiring a separate custom object, enables cohort segmentation in HubSpot workflows, and supports reporting on completion rates and skill acquisition across programs.

Mentors exist as users in StreetSmart with profiles linked to assigned students. We migrate mentor contacts to HubSpot Contacts with a Mentor_Flag__c custom property set to true. The student-to-mentor relationship maps to a custom junction object (Student_Mentor_Relationship__c) storing session_count, last_session_date, and feedback_score so the mentorship history is preserved in HubSpot.

Each student application to an employer becomes a HubSpot Deal. The Deal Name is auto-generated as '{Student Name} → {Employer Name} — {Role Title}'. The Deal Stage maps to StreetSmart application status: Applied → 'Applied', Interviewing → 'Interview', Offer Extended → 'Offer', Hired → 'Closed Won', Rejected → 'Closed Lost'. Employer Company links as the Deal's primary Company association.

StreetSmart employer profiles (company_name, industry, open_roles, hiring_criteria, interview_rounds) map to HubSpot Companies, with direct mapping of company_name, industry, and website to HubSpot's native fields. Open role details migrate as custom properties: Open_Roles__c, Primary_Hiring_Criteria__c, and Interview_Rounds__c. If multiple students apply to the same employer, their applications become separate Deals all linked to the Company record, allowing placement managers to view the full applicant pipeline from the employer page and update role availability.

StreetSmart assessment results (quiz scores, competency ratings, portfolio reviews) migrate as custom Number or Currency fields on the HubSpot Contact: Assessment_Overall_Score__c, Competency_Rating__c. Original assessment dates preserved in a companion datetime field. These properties enable segmentation by skill level in HubSpot workflows.

StreetSmart interview records (interview_date, interviewer_name, interview_type, outcome, feedback) translate to HubSpot Meetings or Tasks. Interview type (phone_screen, technical, behavioral) maps to HubSpot engagement type. Outcome and feedback notes attach as custom properties on the Engagement record and as a note linked to the corresponding Deal.

StreetSmart users (placement advisors, program managers) resolve to HubSpot users by email match. Each student record's owner field links to the matching HubSpot user by email lookup. Unresolved owners (email no match) are flagged before migration — teams either invite the user to HubSpot or reassign records to a fallback owner.

StreetSmart custom fields (internship_preference, visa_status, salary_expectation, target_industry) have no native HubSpot equivalent. We create custom properties with matching data types: visa_status as a pick-list, salary_expectation as a number, internship_preference as a boolean. Field-level mapping is validated against HubSpot's property-type constraints before migration.

Student resumes and portfolio documents attached to StreetSmart profiles re-upload to HubSpot Files associated with the Contact record. File size limits (25MB per file in HubSpot) apply. Documents exceeding the limit are flagged for chunked upload or alternate storage with a link property on the Contact.

StreetSmart notes (advisor notes, mentor feedback, interview debriefs) migrate as HubSpot Notes on the Contact record with original timestamps and owner attribution preserved. Rich-text formatting in StreetSmart notes is preserved where HubSpot's note engine supports it; complex formatting falls back to plain text with a reference to the source system.

StreetSmart's course content, video modules, quizzes, and learning paths do not migrate. These require a separate content strategy: HubSpot's CMS for public-facing content, a Learning Management System integration for structured curricula, or rebuild of key materials as HubSpot-measured assets. We document the content inventory for your team to plan the rebuild.