Migration overview
Our Cribl.Cloud Migration Consulting Service offers a streamlined and effective solution to transition from your existing self-hosted Cribl deployment to our stateof-the-art Cribl.Cloud platform. Capitalizing on our extensive expertise and in-depth knowledge of the Cribl ecosystem, we strive to make this shift as seamless as possible, minimizing downtime and mitigating any disruptions to your ongoing operations.
How it works
Our consultants collaborate closely with you to apply our proven migration plan tailored to your unique requirements and constraints. During this phase, an updated architecture document will be created mapping out all requirements for the migration. They also collaborate with all internal Cribl teams to guarantee a seamless and efficient migration process.
The remote Cribl.Cloud migration begins with a thorough evaluation of your current deployment via a screen-sharing session. This involves examining your sources, destinations, routes, and pipeline configurations. Once reviewed, they will be exported and subsequently test-imported into your Cribl.Cloud organization for validation. After verification, the consultant will coordinate a cutover schedule with you.
Throughout the entire migration process, our consultants provide continuous support and guidance to ensure that your team is well-prepared to manage and maintain your Cribl.Cloud configuration. From initial planning to post-migration assistance, our experts are devoted to facilitating a smooth and successful transition to Cribl.Cloud.
Items migrated
The following items will be migrated during the process of moving to Cribl.Cloud:
Sources and Destinations
Routes / Direct Connects
Packs
Knowledge Objects
Worker Groups
Edge Fleet Configurations
SAML/SSO Configurations
Notifications
Terms and Conditions
Cribl, or an authorized partner, will provide Consulting Services as described in this Service Brief and subject to the applicable Order Form and signed Subscription services Agreement or other written agreement between Cribl and the Customer.
Out of scope
Modification of customer hardware including systems and network equipment
Modification of customer source and destination system configurations
Persistent Queue data will not be migrated.
Migration of no more than 5 On-Premises Worker Groups
Any services or activities other than those explicitly specified in this Service Brief
Scheduled meetings
Cribl may perform the Cloud Migration Consulting Services described in this Service Brief during mutually agreed upon scheduled meetings with Customer. Customer agrees to provide at least forty eight (48) hours’ prior written notice to cancel, reschedule, or otherwise change the length of a scheduled meeting. If Customer fails to provide such notice, Cribl may charge customer for the full price of the originally scheduled meeting.