You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/advanced/migration-from-ld.mdx
+73-71Lines changed: 73 additions & 71 deletions
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ process while providing information on the technical differences between the two
14
14
Migration can be done on a LaunchDarkly project basis, and migration of a project usually consists of the following
15
15
three steps:
16
16
1. Migrating LaunchDarkly feature flags and segments to ConfigCat
17
-
1. Migrating LaunchDarkly teams and permissions to ConfigCat
18
17
1. Adjusting the code of your applications to use ConfigCat instead of LaunchDarkly
18
+
1. Migrating LaunchDarkly teams and permissions to ConfigCat
19
19
20
20
ConfigCat provides a wizard-like tool that is able to do the heavy lifting for step 1. However, there is currently
21
21
no automation for step 2 and 3. So please expect these steps to require some manual work.
@@ -37,8 +37,8 @@ organization that you want to host the products corresponding to the projects yo
37
37
You will also need to have the Organization Admin permission in that ConfigCat organization to be able to create
38
38
products.
39
39
40
-
* If the target ConfigCat organization does not exist yet, you can create one by <atarget="_blank"href="https://app.configcat.com/auth/signup">
41
-
signing up</a>. During the signup process, you will have the opportunity to create your own organization, in which
40
+
* If the target ConfigCat organization does not exist yet, you can create one by
41
+
<atarget="_blank"href="https://app.configcat.com/auth/signup">signing up</a>. During the signup process, you will have the opportunity to create your own organization, in which
42
42
you will have the Organization Admin permission by default.
43
43
* Otherwise, you will need to get an invitation to the target ConfigCat organization, and after joining, you will
44
44
need to request the Organization Admin permission.
@@ -57,8 +57,8 @@ behavior as closely as possible.
navigatetotheOrganizationOverviewpage, thenclickthecardlabeled"Import from LaunchDarkly".
62
62
63
63
<imgalt="Launching the import tool"src="/docs/assets/migration-from-ld/launch-import-tool_192dpi.png"width="1366"height="768"decoding="async"loading="lazy" />
64
64
@@ -172,71 +172,9 @@ In either case, it's highly recommended to download and go through the report. I
172
172
issues, and also includes links to the original and imported entities, which can make it easier for you to look into and
173
173
resolve the issues.
174
174
175
-
## Migrate LaunchDarkly teams and permissions to ConfigCat
176
-
177
-
At the moment, ConfigCat doesn't offer a tool or other automated solution for migrating your teams and permissions from
178
-
LaunchDarkly since there are fundamental differences between the user management and permission systems of the two
179
-
services.
180
-
181
-
LaunchDarkly allows more fine-grained access control over resources, while ConfigCat's permission system was designed to
182
-
be simpler and easier to understand, at the expense of fewer possibilities for fine-tuning access control.
183
-
184
-
Therefore, we can only give you some pointers, but this task will inevitably require some effort on your part.
185
-
186
-
As the first step, we recommend getting familiar with ConfigCat's user management and permission system. You
187
-
can find the basic concepts in the following guides:
As you can see from this, ConfigCat doesn't use the concept of teams and roles of LaunchDarkly. You can't define such
192
-
entities at the organization level, but *permission groups* per product instead.
193
-
194
-
### Map LaunchDarkly roles to ConfigCat permission groups
195
-
196
-
Permission groups roughly correspond to LaunchDarkly roles, with a few key differences:
197
-
* They are scoped to the product where they are defined.
198
-
* There are no [built-in roles](https://launchdarkly.com/docs/home/account/built-in-roles) like Reader or Writer. To
199
-
recreate these in ConfigCat, you will need to define the corresponding permission groups in each relevant product.
200
-
However, LaunchDarkly's Admin and Owner roles can't really be represented using permission groups. ConfigCat supports
201
-
the concept of [Organization Admin role](../../organization/#organization-admin-role) but it's an organization-level
202
-
permission. You can assign this to users on invite or on your organization's "Members & Roles" page as shown in the
203
-
next section.
204
-
* To migrate [custom roles](https://launchdarkly.com/docs/home/account/custom-roles) to ConfigCat, you will need to
205
-
translate the [policies](https://launchdarkly.com/docs/home/account/role-concepts#policies) they define to the fixed
206
-
set of permissions offered by ConfigCat permission groups. Obviously, this won't be entirely possible in every case.
207
-
208
-
With this in mind, create the necessary permission groups in your products, based on the roles defined in your
209
-
LaunchDarkly organization.
210
-
211
-
To set up permission groups for a product, open the ConfigCat Dashboard, select the product on the sidebar, and choose
212
-
"Permission Groups" in the top menu.
213
-
214
-
<imgalt="Launching the import tool"src="/docs/assets/migration-from-ld/permission-groups_192dpi.png"width="1366"height="768"decoding="async"loading="lazy" />
215
-
216
-
### Invite users to ConfigCat and assign them to permission groups
217
-
218
-
Permission groups also act as per-product teams. Once created, you can assign users to them, who will then have the
219
-
permissions specified by the permission group. (A user can only be a member of a single permission group at a time
220
-
though.) This is how you map your LaunchDarkly teams to ConfigCat.
221
-
222
-
However, users don't yet exist in ConfigCat at this point. You need to invite them to ConfigCat first. To do this,
When inviting users, you will need to choose a product, more specifically, a permission group to invite them to.
226
-
This means that they will be automatically assigned to the specified permission groups after signing up. So,
227
-
as you have already created the permission groups, ideally you can immediately invite your users to the right
228
-
permission groups. (Of course, you may need to do this in batches.)
229
-
230
-
It can easily happen that you want to add a user to more than one product. In such cases, invite the user to
231
-
one of the products (it doesn't matter which one), then, after they've signed up, navigate to the "Members & Roles" page of your
232
-
organization, and assign them to the other products too, using the "Change roles" feature of the "Members & Roles"
233
-
table.
234
-
235
-
<imgalt="Launching the import tool"src="/docs/assets/migration-from-ld/member-and-roles_192dpi.png"width="1366"height="768"decoding="async"loading="lazy" />
236
-
237
175
## Adjust the code of your applications
238
176
239
-
The final step in the migration process is to adjust the code of your applications to use ConfigCat instead of
177
+
The next step in the migration process is to adjust the code of your applications to use ConfigCat instead of
240
178
LaunchDarkly to evaluate your feature flags.
241
179
242
180
This will also require more or less manual work, depending on what API your applications currently use for feature flag
@@ -304,8 +242,9 @@ Let's see now step by step how to convert this code to ConfigCat:
304
242
```
305
243
1. Replace the LaunchDarkly SDK key with the ConfigCat one.
306
244
307
-
You can obtain it from the ConfigCat Dashboard, by selecting the config containing the imported feature flag on the
308
-
sidebar, and clicking the "VIEW SDK KEY" button in the top right corner of the page.
245
+
You can obtain it from the [ConfigCat Dashboard](https://app.configcat.com/organization), by selecting the config
246
+
containing the imported feature flag on the sidebar, and clicking the "VIEW SDK KEY" button in the top right corner
247
+
of the page.
309
248
1. Instead of a LaunchDarkly client instance, obtain a ConfigCat one:
310
249
311
250
```js
@@ -505,4 +444,67 @@ you can integrate such tools with ConfigCat to replicate LaunchDarkly's analytic
0 commit comments