Cribl.Cloud Migration

Running your own Cribl Leader means running its upgrades, backups, certificates and capacity. Cribl.Cloud takes that off your plate and adds Search and Lake, but moving there by hand means re-creating configuration and hoping nothing was missed.

The Cribl.Cloud Migration does the move methodically: inventory, export, test import, validation, then a cutover you have already rehearsed.

• Cribl manages the Leader, upgrades, security and scaling, so your team does not
• Your routes, pipelines, packs and knowledge objects move as they are, tested before cutover
• A single coordinated cutover window with a rollback path
• Access to the full Cribl.Cloud suite: Stream, Edge, Search and Lake

Service

Cribl.Cloud Migration

Part number

VC-PS-MIG-CRIBL

Platforms

Cribl, Cloud

Engagement

Fixed-scope project, 90 days service period

Pricing

Stated on the Order Form. Request a quote.

The Cribl.Cloud Migration is a fixed-scope consulting engagement that moves a self-hosted Cribl Stream and/or Cribl Edge deployment to Cribl.Cloud with minimal downtime and disruption. It covers the review of the current deployment, an updated architecture, configuration export and import, validation and cutover.

A dedicated VisiCore engineer, certified by Cribl, leads the work with your team. Support continues from initial planning through the post-migration period agreed at kickoff.

VisiCore delivers this service remotely through scheduled working sessions led by a named VisiCore engineer who holds current Cribl and/or Splunk certifications. On-site days can be added under a separate order.

Unless agreed otherwise in writing, the engagement starts within one week of VisiCore accepting the signed order. The working schedule is set at the kickoff meeting.

VisiCore provides an agenda before each session, including which of your team members should attend. Sessions run one to four hours.

Every task, decision and deliverable is tracked as a ticket in the X10 client portal, so your team always has a current record of what was done and why.

Scope summary. The base scope below, delivered in approximately 8 working sessions.

• Current-state review of the self-hosted deployment in a screen-share session
• Updated architecture document mapping each component to Cribl.Cloud and listing migration requirements
• Configuration export from the self-hosted Leader and test import into the Cribl.Cloud organization
• Items migrated: sources and destinations
• Items migrated: routes and direct connects
• Items migrated: packs
• Items migrated: knowledge objects, including lookups, parsers, schemas and global variables
• Items migrated: worker groups, including hybrid workers that stay on customer infrastructure
• Items migrated: Edge fleet configurations
• Items migrated: SAML / SSO configuration
• Items migrated: notifications and notification targets
• Validation of every migrated item against the self-hosted environment before cutover
• Cutover plan, a single coordinated cutover window and rollback steps
• Post-migration support through the period agreed at kickoff

Quantities

Deliverables

• Current-state inventory of the self-hosted deployment
• Updated architecture document for Cribl.Cloud
• Validated configuration in the Cribl.Cloud organization
• Cutover plan with rollback steps, and a post-cutover report
• Session recordings and migration notes in the X10 portal

Planning schedule for a typical engagement. The actual schedule is agreed at kickoff; hours are estimates of effort per session, not a guaranteed number of service hours.

VisiCore Technology Group provides the services described in this brief under the applicable Order Form and the VisiCore Master Services Agreement, or another written agreement in place between VisiCore and the customer.

Session and hour counts in this brief are planning estimates for the work described, not a guarantee of a fixed number of service hours.

Pricing is stated on the Order Form. Contact VisiCore for a quote.

The following are not included unless added to the Order Form:

• Installation, modification or maintenance of customer hardware, operating systems, containers, firewalls or load balancers
• Changes to the configuration of source or destination systems outside the platform in scope
• Backup and recovery, or day-to-day maintenance, of the customer's environment
• Performance testing and benchmarking
• Formal product training beyond the guidance given in working sessions
• Any service or activity not explicitly listed in the Scope section of this brief
• Migrating persistent queue data from the self-hosted workers
• More than five on-premises worker groups (available as a custom SOW)
• Changes to source or destination system configuration beyond repointing to the new workers
• Re-architecture or optimization of pipelines during the move (see Cribl Deployment Health Check or Growth Activation)
• Decommissioning the self-hosted Leader and worker infrastructure

90 days.

• The customer has 90 days from the start date (the "Service Period") to schedule and use the services in this brief.
• The service ends automatically at the close of the Service Period unless VisiCore agrees in writing to extend it.
• Unused portions of the service are non-refundable and non-creditable.
• VisiCore may deliver services after the Service Period if the customer gives written notice at least 30 days before it ends and VisiCore agrees.

To deliver this service on schedule, the customer agrees to:

• Name an engagement lead with the authority to make decisions and accept deliverables
• Provide the accounts, access and network connectivity VisiCore engineers need before the first working session
• Attend scheduled sessions (one to four hours each) and complete prerequisite work before them
• Bring the subject-matter experts who own the systems being integrated
• Review each deliverable within five business days of hand-off. Without written feedback in that window the deliverable is accepted; non-blocking issues are handled after acceptance
• Have the Cribl.Cloud organization provisioned and licensed before the first working session
• Provide administrative access to both the self-hosted Leader and the Cribl.Cloud organization
• Approve a change window for the cutover and have the owners of affected sources available during it

Meetings are scheduled at mutually agreed times during VisiCore business hours.

The customer must give at least 48 hours' written notice to cancel, reschedule or shorten a scheduled meeting. Without that notice, VisiCore may count the meeting as delivered.