Skip to content

Commit 21b6284

Browse files
authored
Merge pull request #67 from ClickHouse/krithika-ch-patch-4
Update plan_migrations.md
2 parents 451b3a9 + 505ea3f commit 21b6284

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/en/cloud/manage/jan2025_faq/plan_migrations.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ description: Migrating to new plans, tiers, pricing, how to decide and estimate
99

1010
### Can new organizations launch services on the old (legacy) plan?
1111

12-
No, newly-created organizations will not have access to the old plan after the announcement.
12+
No, newly created organizations will not have access to the old plan after the announcement.
1313

1414
### Can users migrate to the new pricing plan self-serve?
1515

@@ -22,7 +22,7 @@ Yes, see below for guidance on self-serve migrations:
2222
| Development | Enterprise (2 replicas+) | :white_check_mark: |
2323
| Production | Scale (3 replicas+) | :white_check_mark: |
2424
| Production | Enterprise (3 replicas+) | :white_check_mark: |
25-
| Dedicated | Contact Support at support@clickhouse.com |
25+
| Dedicated | Contact [support](https://clickhouse.com/support/program) |
2626

2727
### What will the experience be for users in trial running Development and Production services?
2828

@@ -70,15 +70,15 @@ Your service has to be on version 24.8 or later and already migrated to SharedMe
7070

7171
### What is the migration experience for users of the current Development and Production services? Do users need to plan for a maintenance window where the service is unavailable?
7272

73-
Migrations of Development and Production services to the new pricing tiers may trigger a server restart. To migrate to Dedicated services, please contact support.
73+
Migrations of Development and Production services to the new pricing tiers may trigger a server restart. To migrate to Dedicated services, please contact [support](https://clickhouse.com/support/program).
7474

7575
### What other actions should a user take after the migration?
7676

7777
API access patterns will be different.
7878

7979
Users that use our OpenAPI to create new services will be required to remove the `tier` field in the service creation `POST` request.
8080

81-
The `tier` field has been removed from the service object as there is no more distinction between Development and Production services.
81+
The `tier` field has been removed from the service object as we no longer have service tiers.
8282
This will affect the objects returned by the `POST`, `GET`, and `PATCH` service requests. Therefore, any code that consumes these APIs may need to be adjusted to handle these changes.
8383

8484
The number of replicas each service will be created with defaults to 3 for the Scale and Enterprise tiers, while it defaults to 1 for the Basic tier.

0 commit comments

Comments
 (0)