Migrate from StreetSmart to Odoo CRM

StreetSmart contacts map directly to Odoo res.partner records. Set partner's is_company = False. Use Odoo's address fields (street, city, state_id, country_id, zip) to match StreetSmart's address properties. Email and phone map to standard contact fields. Ensure that each contact's timezone is captured in a custom field if needed for reporting, and set the partner's type to 'contact' to distinguish from company records.

StreetSmart companies map to Odoo res.partner with is_company = True. Parent-child company hierarchies in StreetSmart map to Odoo's parent_id on res.partner — the parent company record must migrate first to avoid circular-reference errors. If a company lacks a parent, assign it to a root-level placeholder partner to maintain referential integrity and simplify downstream reporting.

StreetSmart deals migrate as Odoo crm.lead records. Set type = 'opportunity' for deals with active revenue; set type = 'lead' for pre-revenue pipeline entries. The crm.lead.name maps from StreetSmart deal name. Ensure that the deal amount is stored in the planned_revenue field, and map any custom probability values to the probability field, preserving the original sales forecasting data.

StreetSmart pipelines become Odoo crm.team records, one per pipeline. Each pipeline's stage set becomes crm.stage records linked to that team via team_id. This allows Odoo's kanban view to display pipeline-specific stages correctly. If multiple pipelines share identical stage names, FlitStack still creates distinct stage records per team to maintain uniqueness and avoid stage-id conflicts in the kanban layout.

Stage names map value-by-value per pipeline. Odoo requires stage sequence ordering and optional probability values per stage. Preserving StreetSmart stage-entered timestamps requires a custom datetime field on crm.lead. Map each StreetSmart stage label to an Odoo stage with the correct sequence index and assign the corresponding probability percentage to align forecasting expectations.

StreetSmart activity sub-records map to Odoo mail.message records attached to the parent crm.lead or res.partner via res_model and res_id. Use mail.message.subtype_id to classify activity type (email, call, meeting) and preserve original timestamps. If an activity lacks a subtype mapping, assign the generic 'Note' subtype to keep the record visible in Odoo's activity stream without losing historical context.

StreetSmart file attachments and inline notes re-upload to Odoo's ir.attachment model linked to the parent record. Odoo's attachment storage (filestore or external) must be confirmed before migration. Inline note content migrates as mail.message with empty subtype. Verify that the storage location has sufficient capacity for all uploaded files and set appropriate access rights to protect sensitive documents during the transition.

StreetSmart owner_id on each record resolves by email match against Odoo res.users. Unmatched owners are flagged before migration runs; assign them to a fallback Odoo user or invite them to Odoo first. No record lands without an Odoo user owner.

StreetSmart custom fields on contacts require Odoo custom field creation via Odoo Studio or direct ir.model.fields writes before data loads. Field type mapping: text → char, number → float, pick-list → selection, date → date. Track field creation as a pre-migration step.

StreetSmart deal-level custom properties migrate as Odoo custom fields on crm.lead. Priority flags, deal sources, and custom scoring fields require pre-creation in Odoo before migration data is loaded. Note that Odoo Enterprise offers field-level access rules; Community edition treats all custom fields as universally visible.

StreetSmart N:1 contact-to-company associations map to Odoo's child_ids on the company res.partner record. Contacts without a primary company in StreetSmart attach to a designated 'Unassigned Contacts' res.partner stub record. Ensure the stub partner is marked as inactive to prevent it from appearing in active partner searches, and set its name to 'Unassigned Contacts' for clear identification in reports.

StreetSmart lead status values map to Odoo crm.stage via value mapping per pipeline. New, Contacted, Qualified, Lost, Won — each maps to an Odoo stage with appropriate sequence position and probability percentage. If a lead status does not have a direct Odoo counterpart, create a custom stage with a neutral probability and label it to preserve the original categorization.

Store StreetSmart's internal record ID as a custom char field (e.g., x_source_id) on each Odoo record. This enables delta-run de-duplication, rollback traceability, and cross-referencing during reconciliation. Populate x_source_id with the original StreetSmart identifier before any transformations, and index the field in PostgreSQL for fast lookups during incremental syncs.