Merge remote-tracking branch 'origin/4.4'

domaincomponents · Nov 16, 2020 · 0fbd621 · 0fbd621
2 parents 761dfb1 + efe9f21
commit 0fbd621
Showing 1 changed file with 0 additions and 1 deletion.
diff --git a/axon-server/migration/standard-to-enterprise-edition.md b/axon-server/migration/standard-to-enterprise-edition.md
@@ -20,6 +20,5 @@ There are multiple benefits of moving from an Axon Server SE based deployment to
 ## Notes
 
 * The controldb file on Axon Server SE just contains information on the users allowed access to the server. Users in Axon Server SE are not assigned to any contexts or roles. It is recommended that this file is not copied over over and these users be recreated in Axon Server EE and assigned the proper roles/contexts.
-* The migration of the event data from the default context from Axon SE can only be done to a default context within Axon EE. Data cannot be moved to any other context.
 * Any token setup for client access to the Axon Server SE must be setup on the Axon Server EE cluster too.