Migrate from StreetSmart to Zoho CRM

StreetSmart contacts map directly to Zoho CRM Contacts. If a contact has no primary company in StreetSmart, it is attached to a placeholder 'Unassigned Account' created in Zoho to prevent orphan records. Owner is resolved by email match against Zoho Users.

StreetSmart companies map to Zoho CRM Accounts. Company hierarchies (parent/child) are preserved using Zoho's Parent Account lookup field. StreetSmart's company domain field maps to Zoho's Website field for web-based account identification. If a company has no parent, the parent field is left blank, and its address details are mapped to the Billing Address fields in Zoho for consistency.

StreetSmart deals map to Zoho CRM Deals as the core revenue-tracking object. The deal name, amount, expected close date, and owner transfer directly. Deal stage from StreetSmart's custom stage field becomes a Zoho custom pick-list that must be pre-created in the Deals layout before import.

StreetSmart tasks migrate to Zoho CRM Tasks preserving subject, status, due date, priority, and the related parent record (Contact, Account, or Deal). Original create timestamps are stored in a custom datetime field since Zoho's CreatedDate reflects migration insertion time. Task status values are mapped to Zoho's predefined Status picklist, ensuring consistent state representation across records.

StreetSmart meeting records migrate as Zoho CRM Events with the original start time, end time, location, and description preserved. Events are linked to the corresponding Contact or Deal record by Zoho's lookup relationship field. If the meeting includes attendees beyond the primary contact, Zoho's Additional Attendees field can be populated using a comma-separated list derived from StreetSmart's attendee records.

StreetSmart call logs migrate to Zoho CRM Calls with call direction, duration, subject, and disposition notes. Call ownership is resolved by matching the StreetSmart call owner's email to a Zoho User. Call-to-contact linkage is preserved via Zoho's related-record lookup. Call disposition codes from StreetSmart are mapped to Zoho's Call Result picklist, preserving outcome categorization.

StreetSmart notes migrate as Zoho CRM Notes, preserving the note body text, creation date, and the parent record it was attached to in StreetSmart. Rich-text formatting is stripped to plain text if the source note contains non-standard markup that Zoho's Note editor cannot parse.

StreetSmart record owners are matched to Zoho CRM Users by email address. Unmatched owners are flagged before migration with a fallback owner assignment report. Zoho User records must exist in Zoho before the migration runs; the migration plan includes a user-provisioning checklist.

StreetSmart custom properties are analyzed by data type and mapped to Zoho custom fields — text to Text, numeric to Number or Currency, date to Date, and pick-list values to Picklist. Multi-select StreetSmart fields map to Zoho multi-select pick-lists, which require the values to be pre-loaded in Zoho's field configuration.

StreetSmart tag arrays on contacts or companies convert to a Zoho multi-select pick-list field. The pick-list values are extracted from StreetSmart's unique tag values, created in Zoho's field designer, and then mapped during import. Tags with no matching pick-list value are recorded in a catch-all 'Other Tags' value for manual review.

StreetSmart file attachments are downloaded from the source, re-uploaded to Zoho CRM's Attachments section, and linked to the corresponding record by ID. Zoho's 25 MB per-file limit applies; files exceeding this are flagged for manual chunking or alternative storage before import.

StreetSmart workflows and sequences are not migrated. Each platform's automation engine is independent, and automation logic cannot be ported via data export. FlitStack AI exports the workflow definitions as a JSON reference document for the Zoho admin to use when rebuilding automations in Zoho Blueprint.

Reports and dashboards in StreetSmart do not transfer — the underlying data migrates, but the report configurations and visualizations are destination-specific. Zoho Analytics or custom report builders are used to recreate the reporting layer post-migration. The migration package includes a Zoho Analytics workspace template with pre-configured dashboards that replicate the key performance indicators tracked in StreetSmart, allowing quick recreation of reports after migration.

Third-party integrations connected to StreetSmart — email sync, calendar bridges, form connectors — must be rebuilt for Zoho CRM. Integration rebuild is documented as a post-migration step with a connectivity checklist delivered alongside the migration plan. The connectivity checklist enumerates each third-party service, the authentication method required, and the corresponding Zoho connector or Deluge script to re-establish integration after the cutover.