Migrate from SellingLane CRM to Mailchimp

SellingLane Buyer records map to Mailchimp contacts (subscribers) within a designated Audience. The bidder ID becomes a merge field (BIDDERID) for record matching. Email address is the required identifier for Mailchimp import. First name, last name, phone, and address fields map directly. Buyer verification status (approved, pending, suspended) maps to a merge field VERIFYSTATUS. We validate email deliverability before import using a bounce-risk check and flag hard bounces for suppression.

SellingLane custom fields on Buyer records (beyond standard bidder attributes) map to Mailchimp merge fields. Mailchimp allows up to 40 merge fields per Audience; if the Buyer record exceeds this, we prioritize the fields flagged by the customer during scoping and document the remainder in the written inventory. Date fields convert to Mailchimp date-typed merge fields where supported. Multi-select values convert to pipe-delimited text strings.

SellingLane classification tags on Buyer records map directly to Mailchimp Tags on the contact record. Tags do not trigger automations in Mailchimp automatically; we document the source tag set and note that any tag-based automation logic in SellingLane must be rebuilt in Mailchimp Customer Journeys post-migration. Duplicate tag names are deduplicated during import.

SellingLane Registration records (buyer_id, event_id, registration date, payment method) do not have a native Mailchimp object. We flatten Registration data by tagging the contact with the event identifier (e.g., TAG: auction-fall-2024) and adding registration date as a merge field (REGDATE). This preserves the fact of registration without the relational structure. Customers who need full registration history intact should evaluate a CRM rather than Mailchimp.

SellingLane Lot records (lot number, item description, reserve price, starting bid, auction event association) have no Mailchimp equivalent. Mailchimp does not store inventory, items, or product catalog records as standalone objects. We do not migrate Lots. If the customer needs to communicate lot results to buyers post-sale, we recommend exporting Lot results as a CSV and using Mailchimp's batch email feature or a third-party merge tool to send custom winner/loser notifications.

Bid records in SellingLane are relational (buyer_id linked to lot_id with timestamp and amount). Mailchimp has no bid, transaction, or engagement-history object at the record level. We do not migrate Bid records. We recommend the customer export bid history as a CSV for their own records if audit or dispute-resolution history is required.

SellingLane Auction Events group lots and buyers by sale date and location. Mailchimp has no Event object. We map Auction Event metadata by tagging relevant contacts (attendees, registered bidders) with event-identifier tags or by creating a Mailchimp Audience segment filtered by the REGDATE merge field. Event groupings requiring hierarchical date and location filtering are documented as a segmentation strategy recommendation, not a direct migration.

Post-sale payment records (amount, method, date, buyer association, trust-account balance) map partially. We extract buyer_id, payment amount, and payment date as merge fields PAYMENTAMT and PAYMENTDATE on the contact record. Payment method and trust-account balance have no Mailchimp field and are excluded. We recommend the customer maintain payment records in their accounting platform (QuickBooks, Xero) and reference them externally.

SellingLane auction staff assigned as lot owners or bidder managers have no Mailchimp User equivalent. Mailchimp does not have an internal user-assignment or staff CRM layer. We document the staff user list in the written inventory for the customer's admin to map to Mailchimp account roles if needed.

SellingLane auction-specific stages (Registered, Won, Lost, Paid, Closed) have no Mailchimp equivalent. Mailchimp tracks campaign-level performance (opens, clicks, unsubscribes) but not record-level pipeline progression. We document the stage set in the written inventory and recommend a Customer Journey rebuild strategy if the customer wants post-sale automated emails.