Create a Teamleader Backup with Backup TL¶
Use this guide to prepare a destination folder, run a backup from the main window and verify the result. To automate the process, see console usage.
flowchart LR
A["Prepare credentials"] --> B["Configure backup"]
B --> C["Run backup"]
C --> D["Monitor progress"]
D --> E["Verify result"]
E --> F[".encrypted files verified"]
Quick path¶
- Install Backup Teamleader and open the application.
- Enter Client ID and Client Secret if the credentials window appears.
- Choose an empty or dedicated destination folder.
- Keep Rollback days at
0and Full re-run backup disabled for a normal incremental run. - Click Run backup.
- Wait for Process completed successfully and review the
.encryptedfiles in the folder.
First run
Do not enable attachments or file conversion in the first test. Add each option separately after confirming that the basic backup completes correctly.
Prepare credentials¶
When starting, Backup Teamleader may show a window with Client ID and Client Secret fields. Click Verify after completing both fields. The application saves the values and continues with authorization; if it cannot verify at that moment, it shows the available detail.
| Review | Criterion |
|---|---|
| Visible data | Do not document or share real keys, tokens, passwords or sensitive identifiers. |
| Confirmation | Wait for the tool to accept credentials before starting the backup. |
| Evidence | If you need a screenshot, hide the values and show only labels, fields and buttons. |
Protect credentials
Do not share screenshots, configuration files or logs containing Client ID, Client Secret or authorization tokens.
Configure the backup¶
Before clicking the run button, review these fields.
| Field or option | Operational use | Recommendation |
|---|---|---|
| Destination folder | Defines where .encrypted files are saved. |
Use a path with write permissions and sufficient space. A new installation proposes C:\backup_teamleader. |
| Rollback days | Allows recovering earlier changes. | Keep 0 if you don't need to extend the range. |
| Full re-run backup | Forces a complete backup from scratch. | Use when you want to rebuild the backup or discard an incremental run. |
| Download attachments | Enables attachment download when you enter the corresponding key. | Verify beforehand that you have the key and disk space. |
| Export to Excel - destination folder | Converts encrypted files to a readable format. | The current implementation generates .json, although the interface uses the name "Excel". The confirmation requests the Client Secret. |
See Configure backup options to decide when to use each field.
Run and monitor¶
- Click Run backup when the configuration is ready.
- Observe the console or status area to check progress.
- Wait for the completion message before opening or moving generated files.
- Use Stop only if you need to cancel. The button requests cancellation; wait until the state shows Cancelled.
Do not interrupt files
Do not close the application or move the destination folder while the backup is in progress. An interruption may leave a partial run.
Verify the result¶
When finished, verify the result before considering the backup valid.
| Evidence | What to check | Where to look |
|---|---|---|
| Final state | That the run completed successfully or indicates a controlled cancellation. | Status label or built-in console. |
| Generated files | That .encrypted files exist and the date matches the run. |
Folder selected in Destination folder. |
| Attachments | That the expected files were created or updated if you enabled the option. | Destination folder or subfolders generated by the tool. |
| Readable conversion | That .json files exist in the chosen folder. |
Folder indicated in the export block. |
| Log and state | That there are no error messages and the final state is consistent. | Built-in console and available log in the installation. |
A folder with files does not prove a correct backup
Also check the final state and dates. If the run ended with errors or was cancelled, treat the result as partial.
Checklist before using Backup TL¶
- Backup TL is installed or extracted from a specific GitHub Releases version.
- The necessary credentials are available and are entered only in the tool.
- The destination folder exists, has write permissions and sufficient space.
- You decided whether the backup will be incremental or complete.
- You decided whether to download attachments.
- You decided whether to convert files to JSON.
- You will check the final state before closing the tool.
- You will keep the log if the run needs to be audited.
Next step¶
If the basic backup completed correctly, review the full backup, rollback days and attachment options. If an error appeared, go to Troubleshooting before retrying.
Enviar incidencia