System configuration is a structure that includes:
- Installed and user-created workspaces and their content.
- Solutions of all types: custom and installed business solutions.
- Licensed tools.
- Custom modules.
- Business processes, groups, widgets, document templates, and other entities created at the company level.
- Org chart.
- Document categorization.
To prevent errors and service disruptions, you can build complex, interconnected custom solutions and global objects in a test environment first. Then, upload all created entities to your production company using an .e365 file.
Exporting a configuration from one company and updating it in another enables this development workflow.
This article explains how to export a configuration and import it into another company. It also covers resolving conflicts when component versions, org structure, access permissions, or registration settings differ.
Only system administrators can export and update configurations.
Export a configuration
Once you finish configuring modules, workspaces, apps, and solutions, export the configuration to an .e365 file.
To do this, follow these steps:
- Go to Administration > Main and click Export Configuration in the System Settings block.

- In the window that opens, click Start. Then click Export to File. The alternative Export to BRIX365 Store option is currently unavailable.

- Wait for the configuration check to complete, click Download File, and save the file to your computer.

Users can then update their company configuration using the provided .e365 file.
Note that an exported configuration file containing paid tools, or business solutions is encrypted. Unpacking this file will not allow viewing or editing its contents in full.
Update a configuration
Before updating a configuration on BRIX On-Premises, check the system version in the target company. It must be equal to or higher than the version used to create the imported configuration. If the changes are incompatible with your system version, the update will fail or components will malfunction.
To upload a new configuration version to a company, follow these steps:
- Go to Administration > Home and click Update Configuration in the System Settings block.

- Select an .e365 file from your local computer or system files and click Next.
If the system version is lower than the one used to create the workspace, a warning appears at this step. Choose whether to cancel or continue the update.
- The system validates all components included in the configuration. Any detected errors appear in the validation window.
In case of critical errors, such as differing field descriptions between two versions of the same app, you cannot proceed with the update.
If an error is non-critical, such as a missing custom solution in the current company, you can continue updating. Once completed, new solutions and their components are added to the company. Click Next to proceed.

- The system starts comparing the current and uploaded configuration versions. Resolve any detected conflicts.
- Once the update finishes successfully, click Main Page.

Note that licenses for paid tools or business solutions do not transfer with the configuration. If an updated configuration activates a license package that was not previously used in the company, enter a new activation key for it. Active licenses do not require re-activation.
Compare current and uploaded configuration versions
During comparison, current configuration settings and components are automatically matched with the uploaded file. Depending on detected changes and conflicts, step-by-step windows prompt you to choose further actions.
The following section covers handling conflicts, replacing the org chart, updating access permissions, and synchronizing registration settings for Document type apps.
Check configuration changes
Components already existing in the target company are checked for changes in the new version. If you added new components (such as business processes or apps) to the configuration before updating, the update will not affect them.
You can view a list of updates and conflicts to accept all incoming changes or cancel the update. Conflicts cannot be resolved individually.
To continue updating:
- Review the list of modified components grouped across three tabs:
- Change Conflicts. Components modified simultaneously in the target company and the uploaded configuration version. For example, fields added to the same app or edited settings in a business process.
The table displays the name and code of the conflicting component, along with modification timestamps for both current and uploaded versions.
When updating, version settings from the .e365 file apply to conflicting settings.

- Namespace Conflicts. Different components with matching codes created simultaneously in the target company and the uploaded version, such as pages with the report code.
The table shows the component name from the uploaded version. Opposite it, the component code in the target company appears alongside the uploaded component code appended with a digit, for example, _1.
Continuing the update adds the uploaded component with the modified code, keeping the existing component unchanged.

- New Versions. Modified components without conflicts.
- To accept all changes, click Confirm Configuration Update.
Check organizational chart consistency
If organizational chart differences are found, you can replace it entirely or keep the version configured in the target company.
Check access permissions consistency
If access permissions were edited in the current company, a window showing discrepancies opens. Choose which settings to update to the new version. Unchecked permissions remain unchanged. You can also update all access settings or cancel the update.

Check registration settings in Document type apps
If registration settings differ between the target company and the uploaded configuration version, a list of differing registers appears. They are highlighted as follows:
- Green: Registers specified in the new configuration registration settings but missing in the current version. Select the checkbox next to a folder to add it to Document Categorization and app registration settings in the target company.
- Red: Registers used in app registration settings in the target company but missing in the uploaded configuration version. Select the checkboxes for folders you want to keep. Unselected folders are removed from app registration settings, but remain in Document Categorization. You can add them back to registration settings later.

Choose whether to import only selected settings or all changes.