Migrate from SellingLane CRM to monday CRM

Buyer records migrate as Monday.com CRM Contacts. Bidder ID, registration date, and buyer verification status migrate as custom columns on the Contact item. Verification status is stored as a custom picklist column in Monday.com; we flag any buyer whose status was set to a deprecated value no longer in the active picklist. Bidder tier and trust-account standing migrate as text or number columns. We resolve duplicates by email match before insert.

Lots migrate as Items on a Lots board. Lot number maps to the Item name, item description to a text column, reserve price to a number column, and starting bid to a separate number column. Reserve-status logic (met, not met, or withdrawn) is a computed status that does not have a native equivalent in Monday.com; we map it as a Status column with values matched to the source enum. We create the Lots board before any Bid items so that Lot references resolve during Bid import.

Bid records are not standalone in SellingLane; each bid links a Buyer to a Lot with a timestamp and amount. Monday.com has no native Bid object, so we represent bids as Subitems attached to the Lot Item or as Items on a separate Bid board linked via a Connect board column. We preserve bid amount, bid type (floor, absentee, online), and timestamp as Subitem columns. Bid ordering is reconstructed by sorting Subitems by timestamp within each Lot. We sequence Lot import before Bid import and carry lot_id as a foreign-key reference in our staging schema.

SellingLane groups lots by Auction Event (sale date, location, catalog). Monday.com has no native Events object. We map Auction Events as Groups within the Lots board, anchored by an Event Date column and an Event Location text column. Alternatively, we create a separate Events board with one Item per event and link Lots via a Connect boards column. The customer selects the reconstruction strategy during scoping; we document the chosen approach in the migration manifest before any data moves.

Registration records include buyer ID, event ID, registration date, and payment method on file. We create a Registrations board and map these as Items with buyer and event references resolved from the imported Buyer and Auction Event data. Registration status (confirmed, pending, cancelled) maps to a Status column. We flag any registration record where the referenced buyer or event does not yet exist in the destination and hold those records for a second-pass resolution.

Post-sale payment records include amount, method, date, and buyer association. Monday.com has no native Payment object, so we create a Payments board with Items representing individual payment records. Amount and date migrate as number and date columns; method maps to a Status or dropdown column; buyer reference resolves to the imported Contact item via a Connect boards column. Trust-account balance carry-forward is not automatic; we document any trust-account logic as a custom column formula for the customer's admin to configure post-migration.

SellingLane supports custom fields on auction listings but the schema is not publicly documented. We discover custom field definitions during the audit phase by querying the platform's field configuration endpoint. We generate a complete field manifest and map each custom field to a corresponding Monday.com column type (text, number, date, status, checkbox, etc.). Any custom field with a deprecated or deleted definition in SellingLane can silently drop values; we cross-reference every custom field against live lot records to confirm data completeness before committing the migration.

SellingLane uses auction-specific workflow stages (Registered, Won, Lost, Paid, Closed). These do not have direct Monday.com equivalents. We map each SellingLane stage to a Monday.com Status column value on the relevant board. Stage automation triggers (e.g., auto-updates when a bid exceeds reserve) are documented separately as automations to rebuild; we do not migrate them as code.

Item photos, condition reports, and registration documents attach to Lots and Buyers in SellingLane. We export attachments via the platform's file storage and re-associate them in Monday.com using a file-upload column on the Item or a URL column pointing to the stored file. We use a consistent naming convention (Lot-BUYERID-ATTACHMENTTYPE) to maintain the relationship between attachments and parent records.