Import & Export Your TrueCommander Setup

Q: Can I move my whole setup at once?

Export is per module, one .json file each. Together they cover your custom commands, macros, scheduled and startup commands, shortcuts, templates, variables, and APIs, so exporting each gives you the full set to import on another site.

The work you put into TrueCommander, your custom commands, macros, templates, and more, does not have to stay on one site. Each of those modules can export its contents to a file and import them back on another site, so you can clone a setup, hand it to a teammate, or keep a backup.

What you can move

The configurations you create live in their own modules, and each one exports and imports independently:

Each export is a standard .json file, one per module, so you pick exactly what travels.

Exporting

Open the module you want in wp-admin and click its Export button. TrueCommander downloads a .json file of that module's items. Repeat for each module you want to carry over, and keep the files together.

Importing

On the destination site, use the matching module's Import control. Review its validation preview and dependencies. Imported Custom Commands remain disabled until an administrator reviews and enables their executable code.

When this helps

Agencies standardizing a baseline, build your command and macro set once, then import it onto every client site.
Staging to production, move a configuration you have tested into the live site.
Backups before experiments, export a working set, try changes, re-import if you want to roll back.
Sharing, send a teammate your macros or templates as a file.

Good to know

Exports move module items, not licenses or all global settings. Export non-secret Variables separately when referenced. Do not store passwords, API keys, or access tokens in Variables. Review exports for code and sensitive integration fields before sharing.

When you are importing into a site that already has items, it is worth running it on a staging copy first so you can confirm the result before touching production.

Frequently asked questions

Can I move my whole setup at once?

Export is per module, one .json file each. Together they cover your custom commands, macros, scheduled and startup commands, shortcuts, templates, variables, and APIs, so exporting each gives you the full set to import on another site.

What format are the export files?

Plain JSON, one file per module. They are validated for the right format when you import them.

Is this good for setting up new client sites?

Yes. Build your baseline once, export it, and import it onto each new site so every install starts from the same commands, macros, and templates.

Does it move my license or global settings?

No. It moves the items you create in each module, not your license or plugin-wide settings. Each site activates its own license, see Licensing.

Is importing safe to run on a live site?

Import files are validated before they are applied. If the destination already has items, try it on a staging copy first so you can review the result before doing it in production.

Import and export your setup