Migrate from SellingLane CRM to HubSpot

SellingLane contact records map 1:1 to HubSpot contacts. Since SellingLane has no Lead object, all records land as HubSpot contacts. We derive lifecycle_stage by auction outcome: winning bidder → Customer, active bidder → Lead, registered-only → Subscriber. Duplicate email handling and data validation steps are applied before import to ensure contact records are clean and correctly associated with companies.

SellingLane company records map to HubSpot companies. Company-Contact associations are preserved via HubSpot's company association model. If a contact has no associated company, it lands as an unassociated HubSpot contact with a custom property noting the standalone status. We also flag any domain mismatches for review.

SellingLane deal records represent auction lots. We map each deal to a HubSpot deal, using the lot identifier as the deal name. The deal amount maps to the winning bid amount. Pipeline and stage mapping is value-by-value based on SellingLane's auction lifecycle stages.

SellingLane's auction pipeline maps to a HubSpot pipeline. We create a HubSpot pipeline named after the SellingLane auction or category, preserving the stage-order sequence. Multiple SellingLane pipelines each become separate HubSpot pipelines if the portal plan allows. The pipeline name includes the auction identifier for straightforward identification in reports.

SellingLane auction stages (Registered, Active Bidding, Won, Lost, Payment Pending) map to HubSpot deal stage pick-list values. We define the mapping before import and apply stage-probability defaults from HubSpot's standard stage configuration. Stage-entry timestamps become custom datetime fields on the deal.

SellingLane bid records contain timestamp, bidder, amount, and lot reference. We create a HubSpot engagement record (Type: Call, Subject: Bid on Lot {id}) for each bid event and store the full bid log as a custom multi-line text property on the contact for reference continuity.

SellingLane buyer registration records include buyer tier, registration date, and verification status. These map to HubSpot contact properties created as custom fields (Buyer_Tier__c, Registration_Date__c, Verification_Status__c). The registration date populates the HubSpot contact create date when no better source timestamp is available.

SellingLane custom contact fields (buyer tier, payment status, preferred auction type) require pre-creation as HubSpot custom properties. We enumerate every SellingLane custom field in the discovery phase and deliver a HubSpot property creation checklist before the import phase begins. Each property includes the recommended field type, label, and any pick-list values to configure.

SellingLane deal-level custom fields (lot condition, reserve price, auction type, buyer's premium percentage) map to HubSpot deal properties. Each requires creation in HubSpot before the deal import runs. Field type matching (text, number, currency, date) is verified during mapping. We also provide a validation script to check that all values conform to the selected field types prior to import.

SellingLane user records resolve to HubSpot owners by email match. Unmatched users are flagged before migration — your team either creates HubSpot user accounts first or assigns those records to a fallback owner. No record lands without an owner assignment.

SellingLane document attachments (listing photos, condition reports, bidder agreements) are re-uploaded to HubSpot Files and associated with the relevant contact, company, or deal record. File size limits per HubSpot's import constraints apply — large files are flagged for manual re-upload if needed.