Migrate from StreetSmart to Pipedrive

Audit StreetSmart data and design Pipedrive schema

We connect to StreetSmart's export API (with scoped read credentials you provide) and pull a full data dump: all students, clubs, mentors, applications, and membership records. We audit record counts, custom property types, and relationship cardinalities. Simultaneously, we design the Pipedrive target schema: create the pipeline with stages matching your application statuses, create all custom fields via the Pipedrive API, and define the mentor-person vs. mentor-organization approach. You approve the schema plan before any data moves.

Resolve owners and pre-invite users to Pipedrive

StreetSmart user IDs and email addresses are matched against Pipedrive users via the GET /users endpoint. We generate a match report: matched users map directly; unmatched owners require pre-invitation to Pipedrive before migration so their email is registered. No record migrates without a valid Pipedrive owner — unmatched records are held in a staging report until resolved. Club admin users and mentor users receive invitations in the same step.

Migrate organizations and parent hierarchies first

Pipedrive requires Organizations to exist before Deals can link via org_id. We migrate Clubs to Organizations first, preserving parent_org_id links for nested club hierarchies. Circular references (Club A → Club B → Club A) are flagged in the audit and resolved manually before migration. Mentor records (if mapped as Organizations) are migrated in this step alongside clubs.

Migrate people and resolve student-club deal splitting

Students and mentors migrate as Pipedrive Persons. Student IDs are stored as custom fields (Source_Record_ID__c) on each Person for delta-run traceability. For students in multiple clubs, we generate the deal-per-club split plan and present it for your approval. Each split deal links to the student's Person record and the club's Organization record via person_id and org_id foreign keys. Profile images are re-uploaded to Pipedrive file storage and attached in this step.

Run sample migration with field-level diff

A representative slice — typically 200–500 records across students, clubs, applications, and mentors — migrates to Pipedrive first. We generate a field-level diff showing source value vs. destination value for every mapped field, flagging any transformation anomalies. You review the diff in Pipedrive directly and approve or request corrections before the full migration commits. Stage mapping, owner resolution, and image attachment are validated at this step.

Full migration with delta-pickup and rollback capability

The full dataset migrates against Pipedrive's production environment. A delta-pickup window (typically 24–48 hours) captures any records created or modified in StreetSmart during the migration run so Pipedrive reflects the final state at cutover. Every operation is logged in FlitStack's audit trail. If reconciliation fails, one-click rollback reverts Pipedrive to its pre-migration snapshot. We conduct a final count validation comparing migrated record totals against StreetSmart export totals before sign-off.