diff --git a/MIGRATION.md b/MIGRATION.md
index ba849cbcf..c998d7312 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -1,3 +1,108 @@
+# Migrating to JSON Forms 2.5 for React users
+
+In version 2.5 we made the `redux` dependency within the `react` package optional.
+Users of the JSON Forms React standalone version (i.e. without Redux) don't need to change anything.
+In contrary you no longer need to install 'redux' and 'react-redux' to use JSON Forms.
+
+Users of the JSON Forms Redux variant need to perform some changes.
+
+Basically there are two different approaches:
+1. Migrate your app to the standalone variant
+2. Keep using the Redux variant of JSON Forms
+
+Below you can find some guidance about each approach.
+
+## Case 1: Migrate to the standalone variant (recommended)
+
+The standalone JSON Forms variant is the new default and the main focus for new features and bug fixes.
+We definitely recommend migrating to this version as soon as possible.
+All current Redux functionally can also be achieved with the standalone version.
+
+### Example 1: Init action
+Previously the store was initialized like this:
+```ts
+const store = createStore(
+  combineReducers({ jsonforms: jsonformsReducer() }),
+  {
+    jsonforms: {
+      cells: materialCells,
+      renderers: materialRenderers
+    }
+  }
+);
+store.dispatch(Actions.init(data, schema, uischema));
+return (
+  <Provider store={store}>
+    <JsonFormsReduxContext>
+      <JsonFormsDispatch />
+    </JsonFormsReduxContext>
+  </Provider>
+);
+```
+
+Instead of creating a store and passing the required information to that store, we rather pass it directly to the `<JsonForms .../>` component:
+```ts
+return (
+  <JsonForms
+    schema={schema}
+    uischema={uischema}
+    data={data}
+    renderers={materialRenderers}
+    cells={materialCells}
+  />
+);
+```
+
+### Example 2: Register a custom renderer
+Another commonly used action is the 'register renderer' action.
+
+With Redux this could look like this:
+```ts
+store.dispatch(Actions.registerRenderer(customControlTester, CustomControl));
+```
+
+Within the standalone version, the renderer can just be provided to the `<JsonForms .../>` element like this:
+```ts
+const renderers = [
+  ...materialRenderers,
+  // register custom renderer
+  { tester: customControlTester, renderer: CustomControl }
+];
+
+const MyApp = () => (
+  <JsonForms
+    // other necessary declarations go here...
+    renderers={renderers}
+  />
+);
+
+```
+### Example 3: Listen to data and validation changes
+The `JsonForms` component offers to register a listener which is notified whenever `data` and `errors` changes:
+
+```ts
+const MyApp = () => {
+  const [data, setData] = useState();
+  return (
+    <JsonForms
+      data={data}
+      // other necessary declarations go here...
+      onChange={({ data, errors }) => setData(data)}
+    />
+  );
+};
+```
+
+## Case 2: Use the Redux fallback
+
+If you want to keep using the Redux variant of JSON Forms for now (which is not recommended), you have to change a few import paths.
+
+The new imports are available at `@jsonforms/react/lib/redux`, i.e.
+
+```ts
+import { jsonformsReducers, JsonFormsReduxProvider } from '@jsonforms/react/lib/redux';
+```
+
 # Migrating from JSON Forms 1.x (AngularJS 1.x)
 The complexity of the migration of an existing JSON Forms 1.x application, which is based on AngularJS, to JSON Forms 2.x depends on the feature set you use.
 
@@ -37,5 +142,5 @@ As JSON Forms 2 does not rely on any specific UI framework or library you can ch
 #### Use with React
 Please refer to the React [Tutorial](http://jsonforms.io/docs/tutorial).
 
-## Step 3: Migrate Custom Renderers
+### Step 3: Migrate Custom Renderers
 Any custom renderer needs to be re-factored to conform to the new custom renderer style in JSON Forms 2.x. You can find instructions how to implement Custom controls based on React [here](http://jsonforms.io/docs/custom-renderers). While you need to change a lot except for the template, the good news it that writing custom renderers became much simpler in JSON Forms 2 since the framework will trigger rendering and re-rendering in case of changes to the data or other state. In many cases this means you will be able to streamline your code for custom renderers significantly.
diff --git a/packages/core/package.json b/packages/core/package.json
index a89b5b7b0..c2f89e11d 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -68,9 +68,6 @@
     "uri-js": "^4.2.2",
     "uuid": "^3.3.3"
   },
-  "peerDependencies": {
-    "redux": "^4.0.4"
-  },
   "devDependencies": {
     "@istanbuljs/nyc-config-typescript": "0.1.3",
     "@types/redux-mock-store": "^1.0.1",
diff --git a/packages/react/src/redux/JsonFormsReduxContext.tsx b/packages/react/src/redux/JsonFormsReduxContext.tsx
index eadcab7f7..e05e488b5 100644
--- a/packages/react/src/redux/JsonFormsReduxContext.tsx
+++ b/packages/react/src/redux/JsonFormsReduxContext.tsx
@@ -23,8 +23,18 @@
   THE SOFTWARE.
 */
 
-import { JsonFormsState } from '@jsonforms/core';
+import {
+  cellReducer,
+  configReducer,
+  coreReducer,
+  i18nReducer,
+  JsonFormsState,
+  JsonFormsSubStates,
+  rendererReducer,
+  uischemaRegistryReducer,
+} from '@jsonforms/core';
 import { connect } from 'react-redux';
+import { combineReducers, Reducer } from 'redux';
 import React from 'react';
 import { JsonFormsContext, JsonFormsReduxContextProps } from '../JsonFormsContext';
 
@@ -46,3 +56,16 @@ export const JsonFormsReduxContext = connect(
     ...state.jsonforms
   })
 )(JsonFormsReduxProvider);
+
+export const jsonformsReducer = (
+  additionalReducers = {}
+): Reducer<JsonFormsSubStates> =>
+  combineReducers<JsonFormsSubStates>({
+    core: coreReducer,
+    renderers: rendererReducer,
+    cells: cellReducer,
+    config: configReducer,
+    uischemas: uischemaRegistryReducer,
+    i18n: i18nReducer,
+    ...additionalReducers
+});