As technology evolves, so do we — and with Ascend.io Gen2, you'll experience an array of refined features, optimized performance, and improved reliability. This guide gives you a step-by-step walkthrough, ensuring your move is seamless and efficient.
We've created a structured approach for migrating from Gen1 to Gen2. Following this approach means you'll have a hassle-free and efficient migration, leveraging the best of Ascend.io's capabilities.
- If you're a non-enterprise customer, Ascend leads the audit and shares the findings with you.
- If you're an enterprise client, choose between two options:
- allow Ascend limited access to conduct the audit for you, or
- follow Ascend’s detailed instructions to carry out the audit in-house.
- If you're using the Cloud, Ascend launches a new cell for you within a day.
- For dedicated users, you receive a custom provisioning of a dedicated environment.
- If you store credentials internally, you handle the migration.
- If you don't have access to your credentials, Ascend's team assists you in shifting from Gen1 to Gen2.
- You deploy a new Docker container, which generally takes about a week.
- Ascend oversees the transition of all Read, Transform, and Write Connectors and associated Data Feeds. Once your Docker container is deployed, we'll begin migrating those components into the Gen2 environment with a paused status. Components in Gen2 will remain paused until the Gen2 environment is activated.
- Gen1 components will remain running during migration.
- Ascend helps you migrate any persisted data within the platform to Gen2, ensuring all functionalities remain intact.
- Unpause Gen2 Read Connector and Transform components and point them to Gen1 Write Connectors.
- Validate your data by comparing and spot-checking data points across your external sources. If needed, Ascend assists in the validation process.
- Once data is validated, pause the Gen1 Write Connector, point Gen2 Read Connector and Transform components to the Gen2 Write Connector counterpart, and unpause.
- We'll place Gen1 in hibernation for several weeks before eventually shutting it down.
You can expect the migration to take between 4-6 weeks, depending on your enterprise status.
Every client has unique needs. During migration, extra tasks may come up that extends your migration timeframe. Ascend is prepared to handle these and ensure a smooth transition.
|1. Audit Gen1 components.||1 to 3 days|
|2. Launch a new environment.||Up to 1 week|
|3. Migrate Connections & Credentials||1 to 3 days|
|4. Launch Custom Docker.||About 1 week|
|5. Migrate Connectors.||1 to 2 weeks|
|6. Migrate persisted data.||Depends on data size and complexity.|
|7. Validate persisted data.||Depends on your bandwidth.|
|8. Activate the Gen2 environment.||About 1 day.|
|9. Deprecate the Gen1 environment.||Several weeks of hibernation + shutdown period.|
Ascend Cloud Enterprise Environments:
If you have an enterprise account with Ascend Cloud, both the Gen2 Infrastructure and Ascend processing costs are waived for you during the migration phase. This means you don't have to worry about these specific expenses while transitioning.
Dedicated Ascend on Customer Clouds:
If you have a dedicated Ascend environment with your own cloud account, you'll need to cover the infrastructure costs. The Gen2 Ascend processing costs, though, are still waived during migration. This means you should be prepared to budget for infrastructure expenses when you migrate to Gen2.
Ascend communicates with you primarily through Slack. If you aren’t on Slack, emails serve as the main communication method. After the kickoff, Ascend creates a temporary Slack channel named
ascend_customer_gen2_migration for all migration-related discussions.
During migration, keep in mind the following escalation points:
Field Engineering: Field engineering manages customer communications related to engineering tasks, resolves migration issues, answers queries, oversees the Gen1 audit, sets up Gen2 environments, and manages connector migrations.
Technical Project Manager: maintains communication with you, reports progress, and acts as the primary escalation point.
Customer Delivery: ensures the migration aligns with Ascend.io's strategy and serves as the secondary escalation point after the Technical Project Manager.
Updated 12 days ago