The big arch discontinued status has left many designers and developers searching for clarity. This overview explains what changed and how it affects ongoing projects.
Below is a structured snapshot of key facts related to the big arch discontinued situation, including dates, product lines, and affected regions.
| Product Line | Discontinued Date | Primary Impact Region | Support Status |
|---|---|---|---|
| Big Arch Core | 2023-06-30 | Global | End of general availability |
| Big Arch Enterprise | 2024-01-15 | North America, EMEA | Extended support until 2024-12-31 |
| Big Arch Cloud | 2024-09-30 | Asia-Pacific, Americas | Migration path available |
| Big Arch On-Prem | 2025-03-01 | All regions | No further updates |
Product Line Details
Core and Enterprise Editions
The core and enterprise editions formed the foundation of the big arch platform. When the big arch discontinued timeline began, these editions were prioritized for phased retirement to streamline resources.
Cloud and On-Prem Variants
Cloud deployment followed later in the discontinuation sequence, while on-prem variants were scheduled as the final wave. This sequence allowed enterprise customers to plan migration paths with clearer lead times.
Migration Pathways
Data and Workflow Transfer
Official migration tools were released to move data and workflows to successor platforms. Teams are encouraged to validate mappings and run dry runs before the final cutover dates.
Licensing and Cost Adjustments
Licensing shifted to reflect new contractual terms, with transitional discounts for customers moving to alternative solutions. Finance teams should coordinate early to align budget cycles with migration schedules.
Impact on Current Projects
Timeline and Dependency Checks
Project managers should audit schedules for tasks that rely on big arch discontinued components. Identifying critical path dependencies early reduces the risk of unexpected delays.
Compatibility and Testing
Compatibility matrices help determine which integrations remain supported. Conducting regression testing on replacement platforms ensures stability before full deployment.
Recommended Actions
- Review the official discontinuation timeline for your specific product line.
- Run a dependency map of integrations and custom workflows.
- Engage finance early to evaluate transitional pricing and licensing options.
- Start migration testing at least two quarters before the cutover date.
FAQ
Reader questions
What happens to active subscriptions after the big arch discontinued date?
Active subscriptions are honored until their scheduled end date, after which access is revoked and migration guidance is provided.
Can I still download the software once it is discontinued?
Downloads are disabled after the end of support window, and access to repositories is revoked in line with security policies.
Are there penalties for changing plans due to the big arch discontinued status?
Flexible transition programs waive early termination fees for customers moving to approved alternative solutions within the eligibility period.
How do I contact support for legacy big arch discontinued instances?
Legacy support remains available through designated channels until the final extended support cutoff date, with limited feature coverage.