Migrate from SellingLane CRM to Odoo CRM

SellingLane Buyers with a Won bid map to Odoo Contact records attached to an Account. Buyers registered for an auction event but without a winning bid map to Odoo Lead records. We run the split using the presence of a bid record with status Won as the discriminator. Bidder ID from SellingLane becomes a custom field bidder_id__c on the Contact/Lead. Registration date and verification status (a SellingLane custom field) migrate to contact creation date and a custom verification_status__c picklist field.

SellingLane Lots map to Odoo Product records with type=service for intangible auction items or type=product for tangible lots. Lot number becomes the product default_code (SKU field). Item description becomes the product name, reserve price becomes product.list_price, and starting bid becomes product.standard_price. Lot-specific custom fields from SellingLane (which are not schema-documented) require pre-migration field discovery via the SellingLane field configuration endpoint; we create equivalent Odoo Studio fields on product.template before import.

SellingLane Bids are not standalone records; each bid links a Buyer to a Lot and carries timestamp, amount, and bid type (floor, absentee, online). We reconstruct the bid stack as Odoo Opportunity records where the Opportunity name references the Lot and the Opportunity amount references the winning bid. For multi-bid auctions, we preserve the full bid stack in a custom model crm.auction.bid with fields buyer_id, lot_id, amount, timestamp, and bid_type, linked to the parent Opportunity. The Lot-to-Buyer relational link is preserved through Many2one references rather than a flat CSV export that would lose context.

SellingLane Auction Events group lots and bids by sale date, location, and catalog. Odoo CRM has no native Auction Event object, so we reconstruct event groupings as Odoo Tags on the Product records (Lots), with the tag name formatted as the sale title and the tag description carrying the sale date. For auction houses that use Odoo Marketing, we optionally map Auction Events to Odoo Campaign records so that email follow-ups to registered buyers can be tracked against the Campaign. The customer decides the reconstruction strategy during scoping.

SellingLane Registration records link a Buyer to an Auction Event with registration date and payment method on file. Winning-bidder registrations (Buyer has a Won bid) link to the Contact record as a Task with subject 'Registration for [Event Name]' and registration date in the task date. Non-winning registrations link to the Lead record as a Task. Payment method on file migrates to a custom contact field payment_method__c.

Post-sale payment records from SellingLane (amount, method, date, buyer association) map to Odoo Account Move (Invoice) records. We create a Customer Invoice for each winning bidder with the Lot purchase as the invoice line, and the buyer payment as a customer payment linked to the invoice. Trust-account balances require a manual reconciliation step because SellingLane trust-account logic (a compliance feature) does not map directly to Odoo's standard accounting; we flag the carry-forward balance for the customer's accountant to post in Odoo Accounting.

SellingLane custom fields on auction listings are not schema-documented and must be discovered during the audit phase by querying the platform's field configuration endpoint. We generate a complete field manifest for all active lots, cross-reference each custom field against live lot records to confirm data completeness, and map the definitions to Odoo Studio fields on product.template. Any custom field with a deprecated or deleted definition in SellingLane is flagged for manual review before migration because it can silently drop values.

Item photos, condition reports, and registration documents attach to Lots and Buyers in SellingLane. We export attachments via the platform's file storage using the original filename as the naming key. In Odoo, we re-associate attachments to the corresponding Product (for lot photos) or Contact (for buyer documents) records using the ir.attachment model. Odoo's attachment storage requires a configured filestore path; we coordinate with the customer's Odoo instance admin to ensure the import uses the correct storage location.

SellingLane auction-specific stages (Registered, Won, Lost, Paid, Closed) map to Odoo CRM Stage records within the default sales team pipeline. We create a stage mapping during migration scope: Registered maps to New, Won maps to Won, Lost maps to Lost, Paid maps to Won with an invoice issued flag, and Closed maps to Won with all payments received. Stage probability percentages transfer to Odoo Stage probability fields.

SellingLane staff assigned as lot owners or bidder managers map to Odoo Res Users. We validate user email uniqueness across the destination Odoo instance and flag any duplicates before import. Active SellingLane users without a matching Odoo user go to a reconciliation queue for the customer's admin to provision. Owner assignments on Lots and Buyers transfer to the related Odoo record's user_id field.

Classification tags on SellingLane Lots and Buyers migrate to Odoo Forum Tags on product.template and res.partner respectively. Tag-based automations in SellingLane do not transfer because Odoo automation rules are structured differently; we document each SellingLane tag that has an associated automation as part of the automation inventory delivered post-migration.

Bidder verification status in SellingLane (approved, pending, suspended) is stored as a custom property on the Buyer record rather than a native enumerated field. We map this to a custom verification_status__c selection field on the Odoo Contact and Lead models, with the same picklist values preserved. Any buyer's verification status set to a deprecated value no longer in the active picklist is flagged for manual resolution during staging migration.