Switching to Vintiga

A new platform.
Not a new beginning.

You’ve spent years getting to know your guests. Switching should build on that—not start it over. Bring your winery’s next chapter together with Vintiga.

A winery guest browsing wines on a laptop in the tasting room
A more connected experience, from your tasting room to their next order.
01 The relationships you keep 02 The experience you gain 03 The plan to get there
Vintiga guest profile with membership status, interests, activity and an AI summary on two phones

01 / Keep the context

Your guest history has a future.

The bottles they love. The club they belong to. The visits that became a relationship. Start by understanding what’s in your current system, then map what can move.

Your products Wines, variants and the details your team sells with.
Your members Club records, tiers and membership information.
Your guests Profiles, contact details and available purchase history.

Exact fields and history depend on source data. Confirm the migration scope during discovery.

Explore Guest Intelligence

02 / See what’s on the other side

One guest relationship.
More ways to connect.

A visit, a membership, a booking, an order. Explore how Vintiga brings the moments together.

03 / A plan, not a leap

Move forward.
Know what comes next.

Your winery has its own rhythms. Build the switch around your data, your team and the way you serve—not a one-size-fits-all deadline.

A winery team member using a handheld device in a sunlit tasting room
The technology changes. The care behind the welcome stays yours.
  1. Start with your winery.

    Walk through your current platform, daily workflows and what you want to change. Together, define the migration scope, responsibilities and a timeline that fits your operation.

    Discovery → an agreed plan

  2. Map what comes with you.

    Review products, clubs, members, guest records and purchase history. Confirm available exports, field mapping and any gaps before importing the agreed data.

    Data review → an agreed migration scope

  3. Set it up. Put it to the test.

    Work through club tiers, member pricing, tax rules and payment setup. Review imported records and test the key journeys—from a tasting-room order to a member purchase.

    Configuration → review and testing

  4. Bring your team along.

    Prepare the people who will use Vintiga every day. Plan training around your actual service, club and guest-management workflows, with time for questions and practice.

    Staff training → readiness for launch

  5. Launch with a plan.

    Agree the cutover approach, final checks and support arrangements before launch. Coordinate the transition from your current system and work through questions as your team settles in.

    Launch → a clear support handoff

Start where you are

Different starting points.
A considered next step.

Tell us what you’re using today. We’ll review data access and export options before agreeing how to bring it across.

Commerce7

Review your catalog, clubs, member and guest records, and order history. Confirm available data access and the fields to map into Vintiga.

WineDirect

Walk through products, membership data and customer history. Identify available exports and the details your team needs to carry forward.

Shopify

Assess product, variant, customer and order exports as a migration source. Agree what moves and how your storefront transitions.

Ongoing Shopify integration is coming soon. Migration is not live sync.

Spreadsheets & CSV

Start with the files you have. Review structure, required fields and duplicates together, then define an import plan.

A few things worth asking.

The practical questions behind a considered move. Get clear on the details before you commit.

How long does switching to Vintiga take?

The timeline depends on your current platform, the data available and the workflows you need to configure. Discovery is where we confirm scope, responsibilities and a realistic launch plan.

What happens to payment details and recurring billing?

Payment credentials and recurring billing need a separate review with your current provider and the planned payment setup. Do not assume saved payment details can be exported like guest records. Confirm the approach and any member communication before launch.

Can we keep our current platform during the transition?

Discuss the overlap and cutover plan during discovery. Data access, final exports, testing and operational requirements determine how the transition is coordinated. Agree what remains in use and when before making changes to your current system.

Your next chapter

Let’s talk about your winery.
Not just your software.

See Vintiga in action and talk through what switching could look like for your data, your team and your guests.

See It In Action

Book a 30-minute conversation about your winery, your goals and the systems you use today. Together, we’ll identify:

A personalized plan for your winery. No commitment.

Start with a 30-minute conversation.