Migrate from SellingLane CRM to Twenty CRM

SellingLane Buyer records migrate as Twenty Person records. Bidder ID, registration date, and verification status transfer as custom fields on Person. We preserve bidder tier or standing as a custom picklist field. SellingLane's custom Buyer fields are discovered during the audit phase and mapped individually. Email uniqueness is validated before insert to prevent duplicate Person records in Twenty.

SellingLane Lots map to a Twenty custom object we create via the /metadata API before migration. Lot number becomes the custom object's name field, item description becomes a text field, and reserve price and starting bid transfer as numeric fields. Any reserve-status logic (met, not met, no reserve) migrates as a custom picklist. Custom fields on Lots require schema discovery during audit because SellingLane does not publicly document them; we query the field configuration endpoint, cross-reference against live Lot records, and flag any deprecated or silently dropped custom field definitions before final import.

Bid records are relational: each bid links a Buyer (Person) to a Lot (custom object) with a timestamp, amount, and bid type (floor, absentee, online). Bids cannot be imported before Lots because the Lot foreign key must be resolved at insert time. We export Lots first, then Bids, and include the lot_id reference in our staging schema before final import to avoid orphaned bid records. Bid type and timestamp migrate as typed fields on the Bid custom object. The bid stack ordering (which bid won the lot) is validated against SellingLane's final sale outcome before import.

SellingLane Auction Events group Lots and Bids by sale date, location, and catalog. Twenty has no native Events object, so we create a custom AuctionEvent object via the /metadata API. Events are imported as parent records before Lots, with event metadata (date, location, catalog reference) stored as fields. Lots and Bids then carry a lookup to their parent AuctionEvent. Alternatively, if the customer prefers a lightweight model, we tag Lots with event metadata using Twenty's label/tag capability and anchor event groupings by date range. The customer chooses the model during scoping.

Registration records include buyer ID, event ID, registration date, and payment method on file. These map to a Twenty custom Registration object with lookups to Person (buyer) and AuctionEvent. We export Registrations after Person and AuctionEvent records are present in Twenty so that the foreign-key lookups resolve at insert time. Payment method on file migrates as a text field or custom picklist depending on SellingLane's picklist configuration.

Post-sale payment records (amount, method, date, buyer association) migrate to a Twenty custom Payment object with a lookup to Person. Where SellingLane tracks trust-account balances, we migrate the most recent balance as a numeric field on the Buyer (Person) record and flag any trust-account carry-forward logic in the migration notes for the customer's admin to verify. Payment method maps to a custom picklist matching SellingLane's active values.

SellingLane auction workflow stages (Registered, Won, Lost, Paid, Closed) map to Twenty's Opportunities pipeline stages. We configure the stage values in Twenty during workspace setup, mapping each SellingLane stage to a named Opportunity stage with an appropriate probability percentage. Stage names are normalized to align with Twenty's terminology while preserving the original SellingLane stage label in a custom field for audit.

SellingLane staff assigned as lot owners or bidder managers map to Twenty Users. We validate email uniqueness across all owner records before import and flag any duplicate email addresses that would cause import failures. Users without a matching email in the destination are held in a reconciliation queue for the customer to provision before record import proceeds.

Item photos, condition reports, and registration documents attach to Lots and Buyers. We export attachments from SellingLane's file storage and re-associate them in Twenty using a naming convention that links files to their parent record (Lot or Person). The migration does not include attachment re-upload if SellingLane's file storage API is restricted; in that case, we deliver a file manifest with URLs or storage paths so the customer's team can manually re-associate attachments in Twenty.

Lots and Buyers may carry classification tags in SellingLane. We export all tag sets and apply them as Tags in Twenty, noting that tag-based automations in SellingLane do not transfer and must be documented for rebuild in Twenty's workflow layer or a third-party automation tool.