The transition from a sandbox environment to a production environment is both an exciting and critical moment for any integration project! To ensure a smooth cutover and post go-live management, we’ve compiled the essential strategies and resources every Celigo builder should have on hand.
Robust User Acceptance Testing (UAT) Plan
Before cutting over, you must validate that your integrations effectively support real-world business operations.
-
Include Super-Users: Involve departmental experts who know the day-to-day processes best to help build and execute the plan.
-
Review Before Testing: Review flow settings, field mappings, process diagrams, requirements documents, API rate limits, and product documentation to gather the processes and steps that should be included in your test plans.
-
Test Beyond "A → B": Purposefully test complex, multi-step scenarios using production-like data to ensure the integration handles unique edge cases.
-
Iterate and Retest: Start with simple flows and move toward complexity. Always retest to ensure consistency over multiple runs.
-
Identify Scheduled Flows: Confirm that all scheduled flows are set to the correct frequency and time to prevent operational disruptions.
Production Cutover & Operational Readiness
Transitioning from a sandbox environment to a live production state is a critical milestone that requires precise execution to ensure stability.
-
Integration Lifecycle Management (ILM): Utilize ILM to promote integrations from your sandbox to production seamlessly.
-
Snapshots: A key advantage during go-live is ILM’s snapshot feature. Should any post-launch issues arise, these snapshots allow you to restore your production integration to a stable version, minimizing potential downtime.
-
When promoting your integration from Sandbox to Production for the first time, always use the Clone feature at the integration level. This creates a relationship that is required for ILM features like ‘Pull’ and ‘Merge’ to work seamlessly in the future. Without this initial link, you won't be able to easily pull stable changes to production as your ecosystem grows.
-
-
Manage Concurrency & Throughput: Optimize performance by setting concurrency levels (the number of requests made to an API simultaneously) at the connection level.
- Dedicated Connections: Assign high-priority flows (like Orders) to dedicated connections with higher concurrency, while using separate, lower-concurrency connections for non-time-sensitive data.
-
Error Management: Review your error management responsibility matrix and set up error notifications for the identified individuals. This prevents operational gaps and ensures that data discrepancies are addressed by the individuals closest to the business process. Additionally, consider leveraging Auto-Resolve to reduce repetitive errors and allow your team to focus on priority errors.
Revisit and Refine Users’ Permissions
As you move into production, audit who has ‘keys’ to the Celigo platform to maintain security and operational stability.
-
Limit Permissions: Often, the people who build the flows aren't the ones monitoring them post-launch. Review your user list and assign specific roles based on actual need.
-
Audit Log: Familiarize yourself with the account-level audit logs to track user activity, sign-ins, and configuration changes once the system is live. This is essential for troubleshooting and compliance.
-
Enabled Builders: Ensure the post go-live management team is enabled on key Celigo fundamentals and best practices. For those not yet enabled, consider the self-paced enablement resources in Celigo University or the instructor-led Liftoff program.
-
Secure the Account with MFA & SSO: Audit your user security/access. Enforce Multi-Factor Authentication (MFA) for every user to add a mandatory second layer of protection. If your subscription supports it, configure Single Sign-On (SSO) to centralize access through your identity provider (like Okta or Azure AD). This not only streamlines the login experience but ensures that when an employee leaves the company, it’s even easier to revoke or remove access.
Leverage Celigo AI for Documentation
Documentation is vital for long-term maintenance and troubleshooting.
-
AI-Generated Descriptions: Use Celigo Copilot to generate plain-language descriptions for your flows. This helps both technical and non-technical stakeholders understand the integration logic at a glance.
- For complex JavaScript or Handlebar expressions, use Copilot’s "Explain Selection" feature to document exactly what those scripts are doing for future administrators.
Where to Go for Help!
Even with the best preparation, unexpected challenges can arise. If you encounter an issue during your production cutover, leverage these resources for support:
-
Celigo Copilot: Leverage Celigo Copilot to surface helpful documentation, receive troubleshooting best practices,
-
Celigo Help Center: Your first stop for technical documentation, troubleshooting guides, support tickets, and more.
-
Submit a Support Ticket: For critical errors, submit a ticket for further support from the Celigo support team.
-
The Celigo Connective: Visit our community forum to get advice from Celigo experts and peers who may have solved similar challenges.
-
Celigo Office Hours: If you are working on custom or platform flows, join a live Office Hours session to get guidance from a Celigo expert in a classroom-based environment.
-
Ask the Expert: Schedule a 30 or 60 minute call with a Celigo resource in this complimentary product consultation program.
-
Your Implementation Team: If you are currently in an active implementation, remember to notify your assigned Celigo Project Manager or your implementation partner for support.