PathReady Documentation

Prepare the archive, then hand it over

PathReady prepares a separate local copy for a described Microsoft 365 destination. It does not connect to a tenant, upload files or guarantee cloud acceptance. Version 1.0.0 requires Windows 11 x64 and fixed local NTFS folders. Use an archive that is not actively changing.

1. Choose folders

Choose an ordinary local source archive and describe the intended SharePoint library or OneDrive folder. Use a supported direct HTTPS folder address or an advanced decoded server-relative path. Confirm where the document library ends. Sharing links are unsupported; supported library-view URLs need an explicit folder-path parameter. Try an example creates synthetic files for a walkthrough.

2. Review repairs

Inspect original and proposed paths, warnings and blocking issues. Compare a shorter destination before renaming. Review parent-folder suggestions, edit individual names and explicitly exclude files or subtrees. Component changes are actual name edits; affected descendant paths are a different count. Applying a destination comparison retains overrides and exclusions but clears the previous approval.

3. Prepare the copy

Choose an existing staging folder separate from the source. Check changes, exclusions and warnings, then select Create verified copy to approve that exact plan revision. A new operation folder holds the output; PathReady does not merge into an older result. Free evaluation permits up to 100 included files AND 100 MiB of primary content per operation. Larger preparations require the paid license and remain subject to app limits.

4. Read the handoff

The files folder contains prepared content. The reports folder contains START-HERE.txt, handoff.html, path-map.csv, component-changes.csv and manifest.json. Reports identify inventoried scope, exclusions and unfinished work. Plan reports exported before copying are review documents, not evidence of completed verification. Reports and local projects contain potentially sensitive paths; review them before sharing.

Recheck and recover

Recheck prepared file hashes uses the saved receipt as its local baseline and detects changed, extra or missing output without rereading the originals. Keep that receipt trustworthy. If interrupted, resolve the cause, rescan and create a fresh operation. Partial output is not automatically complete, resumed or merged.

Supported scope

The inventory supports up to 100,000 entries including folders, 256 directory levels and 1,024 named streams per file. The Microsoft 365 rule profile models a 400 UTF-16-unit decoded service path, excluding the hostname and leading slash; its component model is 255 UTF-16 units. These are not guarantees of cloud acceptance. An optional client-root path budget is a text-only scenario, not an inspection of a sync client. Network shares, mapped drives, cloud placeholders, links, junctions, EFS-encrypted and offline files are unsupported. Export to supported local storage first. PathReady is not a backup or snapshot and does not repair document links or migrate ACLs.

Activate the full license

Use the purchase key from your EnlightPixel dashboard to activate online once. For an offline computer, display its installation ID and current challenge, obtain a certificate from the dashboard on a connected computer, then import it into PathReady. Subsequent checks are local. Activation is protected for the current Windows account; losing it may require reactivation. Refunded software must no longer be used.

Support

Use Contact or email support@enlightpixel.com with the app version, Windows version, steps and error message. Remove sensitive paths from screenshots. Never send passwords, private license keys or activation certificates. See the privacy policy, terms and refund policy.