Migrate from REIPro to Odoo CRM

REIPro contacts map to Odoo res.partner records. The contact's name, email, phone, and address fields transfer directly. REIPro contacts without a company link create res.partner records with no company_id set, which Odoo handles natively. After migration, each res.partner appears in the contact list and can be linked to opportunities, invoices, or projects as needed.

REIPro company records map to res.partner with company_type set to 'company'. Property owner information stored as REIPro companies transfers as vendor or customer partners depending on the relationship type captured in the source. During the migration, each company partner receives a unique id and can be assigned to relevant purchase or sales orders, allowing Odoo's purchase and sales modules to track vendor contracts and customer accounts.

REIPro property records with deal status map to Odoo crm.lead opportunities. The property address, estimated value, and rehab costs become custom fields on crm.lead. Odoo requires partner_id on crm.lead, so the associated REIPro contact or company must resolve to a res.partner first.

REIPro's 10-step workflow tracker has no native Odoo equivalent. We create a custom selection field (Workflow_Step__c) on crm.lead with the 10 step names from REIPro's pipeline configuration. The current step per property/deal migrates as the field value at migration time.

REIPro's workflow stage names (e.g., 'Lead', 'Under Contract', 'Rehab', 'Sold') map to Odoo crm.stage records. Each stage requires value mapping since REIPro stage names are user-defined text strings. We match by stage sequence order when exact name matching fails. If your pipeline includes custom stage colors or team-specific stages, we create separate crm.stage entries per crm.team and configure stage probabilities to match your historical close rates.

REIPro logged calls, emails, and notes attach to crm.lead records via Odoo's mail.message model. Original timestamps and owner information are preserved. The activity type (call, email, note) maps to mail.message.message_type for Odoo chatter display. All migrated messages appear in the lead’s chatter, allowing team members to view the full communication history directly on the opportunity form without switching screens.

REIPro's built-in direct mail engine has no Odoo CRM equivalent. Mail campaign history and postcard tracking data migrate as a custom text field on crm.lead. Odoo Marketing Automation is available for rebuilding outbound mail sequences post-migration. To continue direct mail efforts, you can configure Odoo’s Email Marketing app, integrate with third‑party services such as Mailchimp or SendGrid, or use Odoo’s custom fields to store campaign identifiers for external processing.

REIPro provides skip-trace enrichment data (owner phone numbers, emails) that Odoo does not store natively. We migrate this as custom fields on res.partner (SkipTrace_Phone__c, SkipTrace_Email__c). Data freshness depends on when REIPro's last skip-trace credit was used. After migration, these fields appear on the contact form and can be used in Odoo’s phone and email templates. For skip-trace services, you can connect Odoo to providers via custom API modules or Zapier.

REIPro property images and documents attach to crm.lead records via Odoo's ir.attachment model. Files re-upload to Odoo's filestore. Size limits apply — Odoo defaults to 25MB per file. We flag oversized files before migration for manual handling. After migration, attachments appear in the lead’s document tab, where you can preview images and download files. If any file exceeds the 25 MB limit, FlitStack alerts your admin to handle it manually.

REIPro tracks lead sources (absentee owner, pre-foreclosure, etc.) as deal or contact properties. These map to Odoo's campaign and utm.source tracking via crm.lead.source_id. New Odoo campaign records are created if matching sources don't exist in the destination. During migration, each source value is matched to an Odoo utm.source record; if none matches, FlitStack creates a new source entry, ensuring that lead source reporting remains accurate in Odoo’s dashboard and analytics.

REIPro workflow owners map to Odoo res.users by email match. Unmatched owners are flagged before migration. In REIPro Team Plan, team members without Odoo user accounts receive a fallback assignment or get invited to Odoo before the migration commits. If an owner’s email matches an Odoo user, the user_id is populated directly; otherwise, FlitStack creates a user record and your admin can merge it with the correct account after go‑live.

REIPro's After Repaired Value (ARV) estimates and MLS comp data have no native Odoo CRM fields. We create custom number fields (ARV_Estimate__c, MLS_Comp_Price__c) on crm.lead. The source of the estimate (REIPro data vs. user entry) is preserved as a note on the field.