Migration Guide

Moving your datato Corksy

We handle the heavy lifting. Here's a plain-English breakdown of what gets moved, what doesn't, and a few questions we need you to answer.

Ready to start your migration?

Start the migration questionnaire

Products

Your Products

We grab your entire product catalog from your current system (Commerce7, OrderPort, etc.) and convert it into a spreadsheet for you to review. You can rename things, change prices, or remove products you no longer sell. Once you're happy with it, we upload it on your first onboarding call.

What gets moved in a basic migration

  • All your wine products and variants
  • SKU numbers
  • Product names and product types
  • Prices
  • Brand names
  • Bottle sizes
  • Alcohol percentages
  • Active or draft status
  • Weight info

Plus the following in a full-service migration

  • Any custom product mapping or transformation beyond what the spreadsheet allows

What doesn't move in any migration

  • Product images (you'll re-upload these in Corksy)
  • Custom product descriptions
  • Inventory counts (entered fresh in Corksy)
  • Bundles

Good to know

  • You get a Google Sheet to review before anything goes live.
  • You can delete rows to remove products, change SKUs, edit prices, update product types, and more.
  • All edits need to be done before your first onboarding call.
Customers

Your Customers

We pull all your customer records — names, emails, phone numbers, addresses, and more. We also bring over their saved credit cards and full order history so nothing gets lost. There are a few cleanup decisions we'll need your input on.

What gets moved in a basic migration

  • First name and last name
  • Email addresses
  • Phone numbers
  • Notes and tags
  • Primary shipping address
  • All other addresses (from order history)
  • Date of birth
  • Primary credit card on file
  • All other saved credit cards
  • Full order history
  • Account creation date

Plus the following in a full-service migration

  • Custom mapping rules (e.g., unique subsets of customers)
  • Unsubscribe list handling
  • Adding manual notes for changed customer IDs or removed club info
  • Cleaning up bounced or invalid emails
  • Uploading a secondary email as a spouse or note
  • Converting tasks into notes
  • Managing marketing email subscription status
  • Merging accounts and databases

What doesn't move in any migration

  • Old passwords (customers will set new ones)
  • Spouse information
  • Order notes from your old system
  • Tasks from your old system
  • Only one cancelled record is kept

Good to know

  • If an email address is invalid or badly formatted, that customer gets mapped to a guest account. We'll give you a list of bad emails so you can fix them.
  • If two customers share the same email: if one has a club membership, all orders merge into the club account. If neither has a club, orders go to the one with the most orders.
  • Customers are first loaded to a staging (test) account, then moved to your live account on go-live day.
Club Members

Your Club Members

All your wine club members and their details come over — who they are, what club they're in, whether they get shipments or pick up in store, and when they joined. If your Corksy clubs won't match your old clubs exactly, we'll need you to tell us where each member should go.

What gets moved in a basic migration

  • Member name and date of birth
  • Shipping and billing addresses
  • Club sign-up date
  • Sales associate who signed them up
  • Delivery method (pickup or ship)
  • Cancellation reason (if cancelled)
  • Pickup location (if pickup and you have multiple locations)

Plus the following in a full-service migration

  • Manually mapping spouse information
  • Changing delivery methods for club members in bulk (e.g., switching 100 members from pickup to ship)

What doesn't move in any migration

  • Spouse information (most systems can't export this)
  • Notes (they get added to the customer profile instead)
  • Gift club notations
  • Club gift messages

Good to know

  • We'll send you a list of any duplicate club members — someone listed twice in the same club. You'll need to fix these in your current system, otherwise the duplicate comes over as-is.
  • If a member's notes exist, they go on their customer profile, not the club record.
  • If your old clubs don't have a 1-to-1 match in Corksy, we'll create the club for you if you don't give us direction. You'll be responsible for re-mapping later if it's wrong.
  • If a club member has a bad email for billing or shipping, we'll assign a placeholder email like 400guest@yourwinery.com. This can be edited in Corksy at a later date.
Orders

Your Order History

We bring over up to 5 years of order history so your team and customers can still look up past purchases. This includes order numbers, dates, payment status, and what was ordered. We'll need you to decide what to do with any unfinished or abandoned orders.

What gets moved in a basic migration

  • Order number and order date
  • Paid date and fulfilled date
  • Future ship dates
  • Payment status (paid, unpaid, or refunded)
  • Fulfillment status (fulfilled, unfulfilled, or restocked)
  • Customer info tied to each order
  • Billing and shipping addresses (also added to customer profiles)
  • SKU data for items ordered

Plus the following in a full-service migration

  • Bringing over orders based on specific custom criteria
  • Remapping order statuses (e.g., changing paid to unpaid for certain orders)
  • Remapping order statuses for orders that were 'shipped externally' or don't require shipping
  • Orders in 'sent to fulfillment' or future ship status

What doesn't move in any migration

  • Orders older than 5 years
  • Some discount names or total discount amounts
  • SKU data in the customer profile view (coming soon to Corksy)

Good to know

  • If an order total is negative or the order number is negative, we mark it as refunded and restocked automatically.
  • Tax and shipping are uploaded as a combined total.
  • We only go back 5 years of order data.
Payment Methods

Saved Payment Methods

Your customers' saved credit cards are securely transferred through your payment processor — we never see the actual card numbers. The processor exports encrypted tokens, our gateway imports them, and we match each token back to the right customer.

What gets moved in a basic migration

  • All saved credit card tokens (securely transferred)
  • Card mapped to the correct customer account

What doesn't move in any migration

  • Billing addresses on cards (these come from club data instead)
  • CVV numbers (card processors never store or share these)

Good to know

  • We need a unique customer ID from your current system to match each card to the right person. If there's no match, the card data is lost.
  • The transfer happens processor-to-processor. Your customers won't need to re-enter their cards.
  • This is one of the last steps because it depends on customer data being loaded first.
  • If your current CRM and payment processor do not provide data on primary card mapped to card, we will upload all cards, but assign the first one given to the club.
  • Most CRM's charge for this service. Therefore, you may opt-out of the payment migration if desired.

Ready to answer your migration questions?

We need a few answers from you before we can start your migration. It takes about 5 minutes and covers all 5 areas above.

Start the questionnaire

You can save your progress and come back anytime.