Overview of your Data Migration

Corksy will work diligently with the client to export, clean, and map all data fields from the clients current CRM software, into the Corksy platform.
We will map all fields that we are able to import based on the structure of our platform.
We do not guarantee 100% data transfer as our platform is structured and operated in a way different than your current software provider. For this fact, we cannot upload all data with a 1:1 match.
Corksy will work with the client to ensure all fields are mapped in the correct data structure and make as many revisions in a testing account as needed, to comply with the clients requests.
Corksy will dedicate resources to each client to ensure this is completed to the best of our ability and will be open and transparent about any data we are unable to migrate.
Corksy will outline to the client all changes to their data that are needed in order to upload successfully.
Corksy and the client will discuss all of these changes via a 1:1 migration call with our migration team.

Processes of Data Migration

The first data export will be managed via an Excel file. The client can request additional revisions or make the changes themselves in the file.
Next, the client will approve of the changes in the Excel file.
Once approved via email, Corksy will uploaded all the data into a testing (staging) account for further review.
Once the client signs off on the staging (testing) account, Corksy will not make further or future changes.
Corksy will download client data from their current CRM software during the migration onboarding process and again right before the client goes live.
To ensure we meet these requirements, the client is required to go-live on the agreed upon go-live date,

Corksy Auto-Data Clean up

Automatic data changes (clean up) will be make by Corksy. The client will have the ability make changes if desired. If the client provides not response on these items, Corksy will assume all changes by our team are approved and will be uploaded.

Missing email address will be changed to guest1@wineryname.com, guest2@wineryname.com, etc.
Bad email address - Corksy will fix or change bad email addresses to guest1@wineryname.com, guest2@wineryname.com, etc.
Missing birthday - Corksy will enter 01-01-2000
Invalid birthday - Corksy will enter 01-01-2000
Missing first name and last name - Corksy will enter Guest Customer
Invalid address, missing zip codes - Address will be omitted from the upload
Orders missing customer ID - Corksy will assign ID 1 to all orders. ID 1 = Guest Customer
Customers missing customer ID - Corksy will assign an unused ID
Re-mapping order type fields to identify with Corksy - Client must provide order ID mapping. Corksy will not upload data until this is identified.
Re-mapping product type fields to identify with Corksy - Client must provide order ID mapping. Corksy will not upload data until this is identified.
Duplicated emails - Corksy will delete records with duplicated email addresses. If the email address has a wine club attached, we treat this record as the primary.
1. We are not responsible for order history lost in this process.
Duplicated customer IDs - Corksy will change customer ID number if they are duplicated.
1. We are not responsible for order history lost in this process.
Duplicated order numbers - Corksy will delete orders with duplicated order ID numbers.
1. We are not responsible for order history lost in this process.
Duplicated products SKUs - If the client does not provide direction on product clean-up needs within 2 weeks, Corksy will change the duplicated SKU name to the product name.
1. We are not responsible for making future changes to SKU name.

Testing (Staging) Account

Corksy will upload all data with changes agreed upon by Corksy and the client into a testing (staging) account to visually see and interpret the data.
While the data is in the testing account, the client will not use this account as their live Corksy account.
1. This account is only for testing purposes and should never be directly edited, changes, or order placed through the system.
2. If the client makes edits to this testing account, Corksy is not responsible for email notification, charges, or complaints made by customers of the account.
3. This testing account is linked to the customers real email addresses and therefore, any edits or changes will trigger an email notification.
4. Any changes in the data that need to be made in the testing account, will be communicated to Corksy via email or phone call. Corksy will be the only one responsible for making further changes to the data on the backend.
Corksy will create as many testing accounts as needed to ensure the data is uploaded correctly during the migration.
Once the client signs off on the staging (testing) account, Corksy will not make further or future changes. The client is responsible for making an manual changes to the data after this point. This includes:
1. Manually deleting product that were initially indicated to be uploaded
2. If product type is incorrect, client must manually delete the products and re-create them with the correct product type
  1. Corksy does not allow the changes of product types in the platform
3. If brand is incorrect, client must manually delete the products and re-create them with the correct product type
  1. Corksy does not allow the changes of brand in the platform
4. If any other product fields were incorrectly migrated and approved in the testing account, client must manually make these changes
5. Order status must be manually changed by client if it is incorrect
  1. Client must manually change from Unfulfilled, Fulfilled, Restock, or vice versa
6. If customer accounts with invalid email are uploaded, Corksy is not responsible for deleting or changing these records
  1. Client must manually change the email addresses in the customer accounts to the correct email address

Live (Production) Account

Once the client signs off and approve all data in testing account is correct and accurate before Corksy moves it into the live Corksy (production) account.

When all orders, customer, and club member data is uploaded into the live Corksy (production) account, the client is able to use and operate Corksy. They are entitled to all data ownership and communication to their customers.
Corksy will agree to upload product data into the live Corksy (production) account before the go-live data and before customers, orders, and club member is uploaded data, to ensure the client can build discounts and club requirements.
Once the data is uploaded into the live production account,
1. Corksy will map the shipping and billing addresses to the club member accounts
2. Corksy will map customers to orders
3. Corksy will map club members and members to card cards, if a credit card migration is taking place.

Go-Live Date

Corksy will download client data from their current CRM software during the migration onboarding process and again right before the client goes live. We will ensure that there is no data gap between the first data clean-up and the go-live date.

To ensure we meet these requirements, the client is required to go-live on the agreed upon go-live date, unless unforeseen circumstances occur where Corksy is liable for the delay.
On the go-live date, Corksy will upload all data into the clients production (live Corksy account)
If the client delays the go-live date, the data gap will not be uploaded to the clients account
1. Data integrity is upheld by Corksy to the highest standards. If you request changes to the data after it was already uploaded to your live Corksy account, we cannot honor these requests as they threaten the data integrity and quality.
If the client continues to use their old system after the agreed upon go-live date, Corksy is not responsible for the data gap between the old CRM software and Corksy.
1. This includes club member, orders, customer, and product new or changed data.

Credit Card Migration

If a credit card migration is taking place, Corksy is not responsible for 100% data transfer of card numbers, expiration dates, CVC codes, or billing address details
The client’s current credit card processor and current CRM software are responsible for transferring the tokenized card data to Corksy.
Corksy will then map the tokenized card data to the customer IDs from the clients current system.
1. Corksy is matching customer ID from the clients current system to the customer ID provided in the tokenzied credit card file.
2. If a customer ID match is not available, Corksy cannot make the credit card match, and is not responsible for this loss in data.
Corksy is not responsible for wine club processing that results in failed cards. Since Corksy is migrating tokenized card data provided by the clients current payment processor and current CRM software, we are not liabile for incorrect or expired data provided by these partners.
Corksy is not responsible for wine club failed credit card processing due to security restrictions from the payment processor.
1. Corksy respects the highest practices in data privacy and may have different security measures in credit card processing, compared to the client current CRM software.
If a customer has multiple credit cards listed in the tokenized card file, Corksy will map the primary credit card to the membership, only if this data is available from the clients current CRM software.
1. If this data is not exportable from the clients current CRM software, Corksy will migrate all credit cards in the tokenized card file, but we will not map the cards to the membership
  1. The customer or the client will be responsible for mapping AKA assigning the primary card to the club membership.
Corksy maps billing address from the clients current CRM software to the the tokenized credit cards. Corksy does not receive billing address from the clients current payment processor. Therefore, Corksy is not responsible for failed cards during wine club processing due to outdated billing data.