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

1. Install Backup Teamleader and open the application.
2. Enter Client ID and Client Secret if the credentials window appears.
3. Choose an empty or dedicated destination folder.
4. Keep Rollback days at 0 and Full re-run backup disabled for a normal incremental run.
5. Click Run backup.
6. Wait for Process completed successfully and review the .encrypted files in the folder.

First run

Do not enable attachments or file conversion in the first test. Add each option separately after confirming the basic backup completes correctly.

Prepare credentials

On startup, 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.

Check	Criteria
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 leave only labels, fields and buttons visible.

Protect credentials

Do not share screenshots, configuration files or logs containing the 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 do not 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. It may take longer.
Download attachments - key	Enables attachment download when the corresponding key is entered.	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, even though the interface reads "Excel". The confirmation requests the Client Secret.

See Configure backup options to decide when to use each field.

Run and monitor

1. Click Run backup when the configuration is ready.
2. Watch the console or status area to check progress.
3. Wait for the completion message before opening or moving generated files.
4. Use Stop only if you need to cancel. The button requests cancellation; wait until the status 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 status	That the run completed correctly or shows a controlled cancellation.	Status label or integrated console.
Generated files	That .encrypted files exist and the date corresponds to the run.	Folder selected in Destination folder.
Attachments	That 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 status	That there are no error messages and the final status is consistent.	Integrated console and log available in the installation.

A folder with files does not prove a correct backup

Also check the final status and dates. If the run ended with errors or was cancelled, treat the result as partial.

Pre-use checklist

• Backup TL is installed or extracted from a specific GitHub Releases version.
• Required credentials are available and entered only in the tool.
• Destination folder exists, has write permissions and sufficient space.
• Decided whether the backup will be incremental or complete.
• Decided whether to download attachments.
• Decided whether to convert files to JSON.
• Will verify final status before closing the tool.
• Will preserve the log if the run needs to be audited.

Next step

If the basic backup completed correctly, review complete backup, earlier days and attachment options. If an error appeared, go to Troubleshoot before repeating the run.

Enviar incidencia