DjMirror Pulse does not provide one universal export that captures every preference, credential, license and external device setting. Use the app's export functions where available, then back up the remaining data files. For activation on another computer, follow License & Activation.

Chapter 1: Know What You Need To Preserve

Other settings are stored separately in operating-system settings, and paired-phone data is stored in app data (on Windows, mobile_devices.json next to the effective config.json in %AppData%\DjMirror\DjMirrorPulse\). Those items are not included by copying config.json alone. Re-pair phones on the new installation.

Chapter 2: Prepare A Backup

1. Finish or stop any active recording, then close DjMirror Pulse so it cannot change files while they are being copied.
2. Locate the effective config.json using Config & CLI. If you use a custom documentsPath, note the path before copying.
3. Export the schedule and timecode cues from their editors, and save the exported files with the backup.
4. Copy the user data listed in the table into a dated backup folder or archive. Keep original filenames and subfolder structure, especially under Visuals/.
5. If you use DMX or controller data stored outside Documents, locate the active files from the app's existing settings/project layout before copying them. Avoid backing up the whole installation directory as a substitute for identifying user data.
6. Protect the backup. Service API keys (Pixabay/Pexels/Gemini, Settings → API Keys) live in OS-level settings, not in config.json — they do not transfer with a file copy, so re-enter them on the new machine. Do not upload an unprotected archive or share it in a support conversation.
7. Keep at least one separate copy on another drive or trusted storage location, then verify that the archive opens and contains the expected files.

Example: back up on Windows

With DjMirror Pulse closed, this PowerShell example copies the media folder and the effective config.json into a dated folder. Adjust the source paths to your own documentsPath and user-data folder (see Config & CLI).

$dest = "D:\Backups\DjMirrorPulse_$(Get-Date -Format yyyy-MM-dd)"
New-Item -ItemType Directory -Force $dest | Out-Null
robocopy "$env:USERPROFILE\Documents\Visuals" "$dest\Visuals" /E /R:1 /W:1
Copy-Item "$env:APPDATA\DjMirror\DjMirrorPulse\config.json" "$dest\config.json"

robocopy reports exit codes below 8 as success. On macOS, copy the same folders with Finder or rsync -a, and take config.json from ~/Library/Application Support/DjMirror/DjMirrorPulse/.

Backup checklist

• App closed, no recording active.
• Visuals/ copied (media, playlists, Styles/).
• Effective config.json copied.
• Schedule and timecode cues exported.
• DMX and controller files copied if used.
• Service API keys noted in a safe place (they do not travel with files).
• Archive opens and a second copy exists elsewhere.

Chapter 3: Restore Or Move To Another Computer

1. Install DjMirror Pulse on the target computer and launch it once so its user folders are created.
2. Close the app before restoring files.
3. Restore media and styles under the destination computer's configured Visuals/ folder. If the documentsPath differs, either restore to that configured folder or deliberately configure the intended path before launching.
4. Restore only the config.json values you need. A configuration copied from another machine may contain machine-specific paths, network settings, or secrets; review it before replacing the target computer's file.
5. Import schedules and timecode cues using their editor controls. Re-select runtime audio, MIDI, DMX and network devices on the new machine.
6. Restore DMX profiles, scenes and controller mappings only where the destination app expects them. Verify fixture addresses, universe/output-port assignments and hardware before enabling live output.
7. Start the app and check the active style, playlists, artist profiles, schedule, cues and connected devices. Rehearse with the simulator or a safe test setup before a live show.

Chapter 4: Important Items That Do Not Transfer By Copying Visuals/

• License: activation is machine-bound. Ask the distributor for a key for the new machine ID; do not copy license settings as a substitute. See License & Activation.
• Audio and device selection: audio, MIDI and hardware devices may have different names or identifiers on the destination. Select and test them again.
• Operating-system preferences: some live settings are stored in Windows registry or macOS preferences, not in config.json. This guide does not prescribe copying those settings between systems.
• Paired phones: pair the Android remote again with the destination desktop. Do not assume the old pairing record is portable.
• Secrets: service API keys live in OS-level settings, not in config.json — re-enter them under Settings → API Keys after a move. If a backup was exposed, rotate the affected keys.

Chapter 5: Before An Application Upgrade Or Reinstall

There is no in-app update procedure documented here. Before installing a newer release or reinstalling:

1. Export schedule and timecode data, and back up the active user data you need.
2. Close DjMirror Pulse and make sure no recording is still active.
3. Follow the installation instructions supplied with the release for your operating system; do not assume that uninstalling preserves every user-data folder.
4. After installation, confirm the version in the app's About section, open the intended Visuals/ folder, and test audio and output before the event.

If the release instructions do not say whether user data is preserved, keep the backup until the new installation has been fully checked.

Chapter 6: Troubleshooting

More: Troubleshooting.