WineDirect Classic Ends December 31, 2026: A Winery Migration Checklist

WineDirect Classic has a real finish line now. Existing clients can use it through December 31, 2026, according to WineDirect's current website.

That date is useful, but it is not a migration plan.

A winery does not just need customer records copied into a new screen. It needs the next club run to charge correctly. The tasting room needs to find the right customer. The website needs to sell the right inventory. Reservations, email, fulfillment, compliance, payments, and accounting need to keep recognizing the same order. Staff need enough time to learn the new path before a busy weekend exposes every assumption at once.

Commerce7 says its WineDirect onboarding process typically takes six to eight weeks and recommends going live at least two weeks before the next club processing. Working backward from December 31 leaves less room than it appears, especially once holiday shipping, club schedules, website work, staff training, and integration testing are placed on the same calendar.

The goal is not to move at the last possible moment. It is to choose a quiet enough launch window to verify the business before the old system is no longer the daily fallback.

This migration guide follows our broader look at AI and automation in Wine Country. The common lesson is the same: useful technology starts with accountable handoffs between the systems and people already doing the work.

Treat this as four connected projects

A WineDirect Classic transition has four parts:

1. Data migration: customers, club memberships, cards, orders, gift cards, tasks, products, inventory, and historical records.
2. Commerce cutover: ecommerce, point of sale, payments, taxes, shipping, club processing, discounts, and transactional email.
3. Website cutover: storefront components, product pages, account access, forms, analytics, redirects, and the final domain switch.
4. Integration cutover: reservations, email marketing, fulfillment, compliance, production, accounting, reporting, and any custom API or spreadsheet process.

The standard migration can be moving along while a critical integration is still unresolved. That is why a green data-import report alone is not proof that the winery is ready to launch.

Start with a systems and ownership register

Before changing anything, list every system that reads from or writes to WineDirect Classic.

Give each row a person, not a department. If the answer is “the website company” or “the tasting room,” ownership is still unclear.

Also record which system is authoritative for customers, products, orders, inventory, membership status, and shipment status. A migration is much easier to test when the team agrees which record wins.

Back up the original before cleaning it

Commerce7 says its team handles the standard WineDirect data migration, but its own documentation still recommends exporting the original data for winery records. Commerce7 also says WineDirect data remains accessible for three months after launch.

Do not use that post-launch window as the primary backup plan. Export before cleanup, then export again before final migration.

At minimum, preserve:

• the full contact list;
• active and historical club memberships;
• product and SKU data;
• order detail and financial reports;
• orders by ship or pickup date;
• gift-card balances and identifiers;
• inventory by location;
• customer notes, tasks, tags, and contact types;
• current promotions, allocations, and club configuration;
• a list of integrations, API users, and scheduled exports;
• screenshots or PDFs of reports the team depends on.

Store the files in a dated, access-controlled folder and keep a short manifest explaining what each export contains. Customer and payment-related data deserves the same care during migration that it receives in production.

Clean the records that affect live relationships first

Not every old record deserves the same amount of attention. Start with active club members, high-value customers, recent buyers, open orders, current products, gift cards, and records used by integrations.

Commerce7's migration guidance calls out several practical limits:

• customers without a valid email address will not import as customer records;
• adding fake email addresses is discouraged because it can damage email deliverability;
• some orders can import without an attached customer when the related profile cannot be corrected;
• imported order numbers change, although the original WineDirect order ID remains available as an external reference;
• product descriptions lose HTML, and only the main product image is imported;
• unsupported characters in SKUs are changed;
• migrated bundle orders retain the bundle SKU, not the child SKUs;
• imported, unfulfilled orders do not automatically deduct inventory when fulfilled;
• some Tock order histories may need to be preserved through WineDirect reports;
• duplicate-looking pickup and inventory locations should not be deleted before the final migration is complete.

This is exactly why the first migration is a rehearsal. Use it to find the exceptions while Classic is still operating and while the people who understand the old records can explain them.

Put the calendar around club and holiday risk

Choose the go-live date before the team starts making isolated configuration decisions.

Avoid placing launch directly before:

• a major club processing date;
• a high-volume allocation release;
• a holiday shipping cutoff;
• a large event or tasting-room weekend;
• a key employee's absence;
• harvest work that already has the same staff at capacity.

Commerce7 recommends launching at least two weeks before the next club processing. Treat that as a minimum buffer for observation, not as extra project time.

A practical sequence looks like this:

Six to eight weeks before launch

• confirm the launch date and named project owner;
• complete the systems register;
• begin the first migration and data review;
• confirm website ownership, DNS access, payment setup, hardware, and integration responsibilities;
• define what must work on day one and what can wait.

Three to five weeks before launch

• resolve high-priority migration errors;
• finish website and storefront implementation;
• configure products, clubs, shipping, taxes, emails, roles, and locations;
• reconnect or rebuild integrations;
• train staff with real operating scenarios;
• run a complete club rehearsal with test records.

One to two weeks before launch

• freeze nonessential changes;
• confirm final migration timing;
• run the go-live checklist with every workflow owner;
• prepare customer and staff communications;
• verify analytics, redirects, transactional email authentication, and support escalation paths;
• take a second set of exports.

Launch and the following business day

Commerce7 documents a final push one business day before launch and a delta, or top-up, push one day after launch. During that window, record every change made in either platform. After the delta migration, reconcile counts and inspect the actual records that matter most.

Test outcomes, not buttons

“The integration connected” is not a useful launch test. Run the transaction from beginning to end and confirm the evidence in every system that should receive it.

Test at least these scenarios:

• a new ecommerce customer places a shippable order;
• an existing club member signs in and updates a card;
• a club member changes an address or pickup preference;
• a tasting-room order updates the correct customer and inventory;
• a failed payment enters the right recovery workflow;
• a compliant shipment reaches fulfillment and returns tracking;
• a blocked shipment stops in the correct review queue;
• a reservation or visit updates the intended guest profile;
• an order appears correctly in email segmentation and accounting;
• a gift card, discount, refund, and exchange behave as staff expect;
• a customer service representative can find an order by its old WineDirect ID;
• reporting totals can be explained even when the two platforms use different dates or order identifiers.

For every test, save the order number, customer, time, expected result, actual result, and screenshots. If the test fails, assign an owner and a retest date. A launch checklist without evidence becomes a list of assumptions.

Pay special attention to custom and older integrations

WineDirect's developer documentation distinguishes the newer integration paths from Classic's older SOAP APIs and discourages new Classic integrations. Its Classic API documentation also notes an HTTPS change that took effect in February 2026 and can expose clients that do not handle redirects correctly.

That history matters because an integration may have been quietly running for years with credentials, endpoints, field mappings, or scheduled jobs that no one has revisited.

For each integration, answer:

• Is there a supported Commerce7 app or native connection?
• If not, is there a current API, webhook, or documented export path?
• Which identifiers are used to match customers, orders, products, clubs, and locations?
• Will historical WineDirect IDs remain searchable where staff need them?
• What is the retry and exception process when a sync fails?
• Who can disable the old connection after the final delta migration?

Do not rebuild an old integration field for field just because it exists. Preserve the business outcome, then simplify the handoff where the new platform makes that possible.

Reconcile after launch before calling it complete

The first successful order is a good sign. It is not the finish line.

For the first week, review a short daily reconciliation:

• ecommerce and POS order counts;
• payments, refunds, and failed transactions;
• club joins, cancellations, holds, and address changes;
• inventory movement by location;
• shipments held, released, and fulfilled;
• transactional email delivery;
• reservation and marketing sync exceptions;
• accounting totals and unmapped records;
• customer issues related to login or account history.

Keep the issue log open until every critical exception has an owner, a resolution, and a verified retest. Then document which WineDirect exports must remain in the winery's records after access closes.

The checklist

Ownership and scope

• [ ] A launch owner and decision maker are named.
• [ ] The launch date avoids club, holiday, event, and staffing conflicts.
• [ ] Day-one requirements are separated from later improvements.
• [ ] Every WineDirect-connected system has an owner and migration path.
• [ ] Systems of record are named for customers, products, orders, clubs, and inventory.

Data

• [ ] Original WineDirect exports are complete, dated, secured, and inventoried.
• [ ] Active club members, recent buyers, open orders, products, gift cards, and locations are reviewed first.
• [ ] Migration errors are assigned and tracked.
• [ ] Old and new identifiers can be reconciled.
• [ ] A second backup is scheduled before final migration.

Commerce and website

• [ ] Payments, hardware, shipping, taxes, clubs, promotions, and transactional emails are configured.
• [ ] Website storefront, account access, analytics, redirects, and DNS cutover are ready.
• [ ] Email sending domains and customer-facing templates are verified.
• [ ] Staff have practiced the real workflows they own.

Integrations and launch

• [ ] Reservation, marketing, fulfillment, compliance, accounting, production, and custom integrations are tested end to end.
• [ ] Final and delta migration windows are on the shared calendar.
• [ ] The change log, issue log, escalation path, and fallback procedures are ready.
• [ ] Post-launch reconciliation has an owner and a daily review time.
• [ ] Old connections will be disabled only after the new path is verified.

The December deadline creates urgency, but urgency should produce a cleaner plan, not a rushed cutover.

If your winery has WineDirect at the center of a larger stack, start with a winery systems map. Bring the current integrations, spreadsheets, club calendar, reports, and known exceptions. We can turn them into a migration scope with owners, tests, and a launch sequence before the calendar makes those decisions for you.