Migrate from SellingLane CRM to HighLevel

SellingLane Buyer records map to GoHighLevel Contacts with bidder ID preserved as a custom Contact field (bidder_id__c). Registration date maps to a custom date field (registration_date__c). Buyer verification status (approved, pending, suspended) is a custom property in SellingLane and migrates to a GoHighLevel custom picklist field (verification_status__c). Bidder tier or standing maps to a custom picklist field (bidder_tier__c). We validate email uniqueness during import and flag any duplicate Buyer records for admin resolution before final load.

SellingLane Lots map to a GoHighLevel Custom Object named Lot. Lot number becomes the name field, item description maps to a text field, reserve price and starting bid map to currency fields. Reserve status logic (met, not met, no reserve) migrates to a picklist field (reserve_status__c). We build the Lot custom object schema in GoHighLevel before migration, including all standard fields and any custom lot-specific attributes discovered during the audit phase. Custom fields on lots are undocumented in SellingLane; we query the field configuration endpoint during audit to generate a complete field manifest.

Bid records are linked to Buyer and Lot in SellingLane and do not exist as standalone rows. Each bid carries bid amount, timestamp, and bid type (floor, absentee, online). We extract bid data and create a GoHighLevel Bid custom object with a lookup relationship to the Lot custom object and a lookup to the Contact record (mapped from the Buyer). Bid order is preserved by setting a sequence number field on each Bid record. For bid records with no linked buyer or lot, we flag orphaned rows during audit and present them to the customer for resolution.

SellingLane Auction Events group lots and bids by sale date and location. GoHighLevel has no native Auction Event object, so we build a Custom Object named Auction Event with fields for event_name, sale_date, location, and catalog_description. Lots link to Auction Events via a lookup field (auction_event__c) on the Lot custom object. We extract all Auction Event records from SellingLane and create corresponding GoHighLevel custom object records before importing Lots. If the customer prefers lots to remain independent, we tag lots with event metadata in a custom text field and skip the parent event reconstruction.

Registration records include buyer ID, event ID, registration date, and payment method on file. We map these to a GoHighLevel Registration custom object with lookups to the Contact (from Buyer) and Auction Event (from Event). Registration date migrates as a date field, and payment method on file migrates as a text field. If the destination does not require Registration as a standalone object, we can alternatively nest registration data as custom fields on the Contact record.

Post-sale payment records include amount, method, date, and buyer association. We map these to a GoHighLevel Payment custom object with a lookup to Contact. Trust-account balance carry-forward is preserved in a currency field (trust_balance__c) if applicable. Where GoHighLevel's built-in Invoice or Payment features are sufficient, we map to those native objects instead and flag the decision during scoping.

SellingLane uses auction-specific workflow stages (Registered, Won, Lost, Paid, Closed). We map these to GoHighLevel Pipeline stages and create a Pipeline in GoHighLevel with matching stage names and order. Each SellingLane stage becomes a GoHighLevel Deal stage. If SellingLane stages have custom automation triggers, we flag these in the automation rebuild inventory because triggers do not migrate.

SellingLane staff assigned as lot owners or bidder managers map to GoHighLevel Users. We resolve by email match. Any SellingLane Owner without a matching GoHighLevel User is held in a reconciliation queue for the customer to provision before record import resumes. User active status, role, and team assignment are preserved as GoHighLevel User fields.

Lots and Buyers may carry classification tags in SellingLane. We export tag sets and apply them as GoHighLevel Tags on the respective records. Tag-based automations in SellingLane do not migrate; we list them in the automation rebuild inventory for the customer's admin to implement in GoHighLevel Workflows.

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 GoHighLevel using naming conventions that link files to the correct record (Lot ID or Contact ID in filename). Large attachment sets require staging in an intermediate storage location before batch upload to GoHighLevel.