FolderView3 Migration

FolderView3 Migration

FolderView Plus can convert a complete FolderView3 configuration through a read-only preview followed by one reviewed transaction. This workflow is broader than importing a Docker or VM folder file because it can include both types, rules, defaults, start order, and appearance.

Before you begin

1. Copy the entire FolderView3 configuration directory off-server.
2. Copy /boot/config/plugins/folderview.plus too if FolderView Plus already contains data.
3. Keep the old export until every runtime surface is verified.
4. Open Settings -> FolderView Plus -> Advanced -> Recovery.

If FolderView3 is still installed, FolderView Plus may pause Docker/VM/Dashboard injection to avoid two folder runtimes owning the same host pages. Settings and migration review remain available. Do not remove FolderView Plus; remove the conflicting legacy plugin only after its data is safely copied and the migration plan is available.

Choose a source

• Detect installed FolderView3: reads the bounded FolderView3 configuration location and reports availability, version, and Docker/VM counts.
• Preview FolderView3 export: parses a supported full-export JSON file selected in the browser.

Detection and preview are read-only. Unsupported export schema versions are rejected rather than guessed.

What is converted

The preview can plan conversion of:

• Docker and VM folders, hierarchy, members, and stable member identities where available.
• Legacy folder regex into ordered auto-assignment rules.
• Docker and VM preferences and folder defaults.
• Dashboard layout preferences.
• FolderView3 custom start-order data into custom batches.
• Recognized appearance variables and bounded custom CSS into a named appearance profile.
• Informational counts for native Docker organizer/autostart data.

Imported appearance is inactive by default so it cannot immediately restyle the webGUI before review.

Review optional host changes

Replacing Unraid's native Docker autostart order is a separate, explicit option and defaults to off. The preview reports the native-autostart count but does not silently select replacement. FolderView3 organizer-registry data is also reported separately instead of automatically taking ownership of native host structures.

Custom CSS is bounded and scanned. Unsafe constructs such as remote @import rules are excluded and shown as warnings. Review all retained CSS before activating the imported appearance profile.

Preview digest and apply

The preview produces a digest of the exact source and plan. Apply requires confirmation and sends that expected digest back to the server. If the source changed or the preview is stale, reopen the preview rather than bypassing the check.

Apply performs one coordinated transaction:

1. Revalidates the source and expected digest.
2. Creates global and type-specific rollback protection.
3. Writes Docker, VM, rule, default, start-order, and appearance targets atomically.
4. Optionally applies the separately selected native-autostart change.
5. Reads the saved state back and verifies it.
6. Rolls back if commit or verification fails.

The downloadable migration report is summarized and does not expose the raw migrated target configuration.

Screenshot placeholder — FolderView3 migration preview

Capture detected source/version, Docker/VM counts, operations, warnings, native-autostart opt-in shown off, digest status, and Apply confirmation using an isolated test system.

Verify the result

1. Confirm the transaction says Applied and verified.
2. Review Docker and VM folders in Basic Settings.
3. Open Rules and confirm converted regex priority.
4. Open Start Order and preview the sequence before synchronizing native order.
5. Open Appearance and review the inactive imported profile before activation.
6. Remove only the conflicting FolderView3 plugin when its external backup is secure.
7. Refresh Docker, VMs, and Dashboard and confirm the conflict-resolved banner.
8. Run Diagnostics and create a fresh manual snapshot.

When to use normal import instead

Use normal Docker/VM import when you only have one type file or want Merge/Add/Replace control for a narrow folder-map migration. Use this page's workflow when the source is a complete FolderView3 installation/export and coordinated conversion matters.

See also: Backup, Recovery, and Migration · Installation and Upgrades · Appearance, Icons, and Themes