Use the Solution Modeller to import previously created and exported solution packages. See the article Exporting Clio Operate Configuration for more information on building and exporting solution packages.
It is best practice to perform imports after hours and to use the Maintenance mode global feature to minimise issues when importing a solution package.
How to import solution packages
The Import Configuration screen lists past jobs and their status. Clicking a job row for completed jobs opens the Job Progress blade, while jobs with another status open the Import Job blade. The more options menu (burger menu) allows you to view or delete the job.
Clicking the New Import Job icon lets you choose an exported solution package zip file to import. If the package passes validation, click Execute to perform the import.
If any Event Engine (EE) roles are running, the system will ask if you want to stop them before performing the import. Click Yes to continue. After the import, click the Start All EE Roles button in the action bar to restart the EE roles. This is a manual step and does not happen automatically. Confirm the roles are running afterwards on the Event Engine Health screen, and follow the After an import checklist below.
Job Progress
The Job Progress blade shows the status and allows you to view full details. Clicking Full Details in the action ribbon opens the Import Job blade.
If the import job encountered errors, the tasks causing the issue are listed, and you can retry 
the task or view the error log 
to troubleshoot the problem.
Import Job
The blade shows pending, complete, and errored tasks: 
Clicking one of the coloured icons allows you to view the log for each task.
Clicking jobs with the Created state shows the import job validation blade.
Select the error (red) or warning (orange) icon to see the validation details. You must fix the validation condition, redo the export package, and try the import again.
You can try revalidating; if everything passes, execute the import job.
After an import: verification checklist
Stopping the Event Engine (EE) roles is part of the import, but restarting them is a separate manual step. If it is missed, indexing, email, webforms, and workflow processing stop across the platform, often with no obvious error. Before you treat an import as complete, confirm all of the following.
- Restart the EE roles. Click Start All EE Roles in the action bar. This does not happen automatically on import completion.
- Confirm the roles are green. Open Admin > Diagnostics > Event Engine and check that all roles show as running (green). See Monitor Event Engine Health.
- Confirm a test event flows. Trigger a simple event (for example create or update a test record) and confirm it processes, so you know the pipeline is live, not just the roles.
- Confirm downstream processing has resumed. Check that search results update, inbound email is picked up, and webform submissions arrive. Review the Search Indexes screen and confirm the backlog is draining, not growing.
Tip: run imports after hours and use Maintenance mode, so any missed restart is caught before users are affected.