@@ -116,48 +116,6 @@ If a user has multiple ``RegisteredUser`` rows across organizations, the
116116command keeps that user when **any ** related row uses one of the excluded
117117methods.
118118
119- ``upgrade_from_django_freeradius ``
120- ----------------------------------
121-
122- If you are upgrading from `django-freeradius
123- <https://github.com/openwisp/django-freeradius> `_ to openwisp-radius,
124- there is an easy migration script that will import your freeradius
125- database, sites, social website account users, users & groups to
126- openwisp-radius instance:
127-
128- .. code-block :: shell
129-
130- ./manage.py upgrade_from_django_freeradius
131-
132- The management command accepts an argument ``--backup ``, that you can pass
133- to give the location of the backup files, by default it looks in the
134- ``tests/ `` directory, e.g.:
135-
136- .. code-block :: shell
137-
138- ./manage.py upgrade_from_django_freeradius --backup /home/user/django_freeradius/
139-
140- The management command accepts another argument ``--organization ``, if you
141- want to import data to a specific organization, you can give its UUID for
142- the same, by default the data is added to the first found organization,
143- e.g.:
144-
145- ::
146-
147- ./manage.py upgrade_from_django_freeradius --organization 900856da-c89a-412d-8fee-45a9c763ca0b
148-
149- .. note ::
150-
151- You can follow the `tutorial to migrate database from
152- django-freeradius
153- <https://github.com/openwisp/django-freeradius/blob/master/README.rst> `_.
154-
155- .. warning ::
156-
157- It is not possible to export user credential data for ``RadiusBatch ``
158- created using prefix, please manually preserve the PDF files if you
159- want to access the data in the future.
160-
161119.. _radius_convert_called_station_id :
162120
163121``convert_called_station_id ``
0 commit comments