# Note Bridge: move notes between seven Chinese phone clouds, or take them offline > A Windows tool that migrates selected notes across Xiaomi, OPPO, vivo, Huawei, Honor, Meizu and WPS cloud accounts, or exports everything to TXT, Markdown, HTML and Word for local keeping. **lingxuanqjc-alt/note-bridge-desktop** — Windows 笔记导出与迁移工具：七平台适配、四格式导出、离线阅读，明确验证范围与失败状态。 - Repository: https://github.com/lingxuanqjc-alt/note-bridge-desktop - Website: https://github.com/lingxuanqjc-alt/note-bridge-desktop#readme - Stars: 771 · Forks: 41 - Language: Python - License: MIT - Published: 2026-09-18 · Updated: 2026-09-18 · Language: en - Canonical page: https://hysenlabs.com/projects/lingxuanqjc-alt-note-bridge-desktop ## Switching phone brands should not strand your notes Switch from a Xiaomi phone to a vivo one and your notes stay behind in the vendor's cloud, locked to the account you are leaving. Note Bridge, by lingxuanqjc, is a Windows desktop tool for exactly that situation: log into both cloud accounts, pick the notes worth keeping, and migrate them into the target platform's cloud, or export the whole set to local files you control. Seven platforms are supported for both reading and cloud migration: Xiaomi, OPPO, vivo, Huawei Notes, Honor, Meizu and WPS. Export covers TXT, Markdown, HTML and Word, with merged files or one file per note. Version 1.0.0 is the current release, MIT licensed, and the README is refreshingly upfront about limits: format differences are reported rather than hidden, and uncertain writes leave a receipt for inspection. ## Installing, and the export-first workflow Requirements are Windows 10 or 11 x64 plus Microsoft WebView2 Runtime, with the installer guiding you to Microsoft's page when WebView2 is missing. Three downloads exist: a setup executable, a portable zip whose extracted folder must stay intact around NoteBridge.exe, and a source zip for building from the development README. The README prescribes an order worth following: install, try export first, then migrate. Export needs only the source account login, saves locally, and is the least risky way to learn the flow: open the export page, sign in, fetch notes, choose the format and file mode, export locally. Only after that does the migration page make sense, where both accounts are signed in through their official login windows, notes are selected from a list with format hints, and a confirm button commits the batch with a count. ## The migration model: add, never replace Migration writes new notes into the target cloud and always keeps the source, and the README builds its safety advice on that foundation: export a backup first, practice with a single note, and check text, images and grouping on the target side after each run. The pipeline is cloud to cloud, source cloud to Note Bridge to target cloud to target phone, with the vendor's own sync service handling the last hop, so there is no per-note copy-pasting. Uncertainty is handled explicitly. When the tool cannot confirm whether a write landed, it marks the item as needing verification and preserves the receipt rather than claiming success, and the FAQ warns against re-migrating the same batch because a phone has not synced yet: the correct sequence is checking the target's web view first, since a successful cloud write does not guarantee the handset has caught up. Re-authenticating does not clear that protection, which is the right behavior for a tool that touches your notes. ## The support matrix, with per-platform honesty All seven platforms support local export and cloud migration in, and the README's matrix records each platform's quirks rather than averaging them away. Xiaomi migration requires a verified non-encrypted account and caps single images at four megabytes. OPPO stops processing with a prompt when its server demands chunked image upload. Huawei maps to its Notes cloud service specifically. vivo, Honor, Meizu and WPS carry no extra notes in the table. Cross-platform conversion has its own honesty section: body text, groups and images convert within what each target platform supports, cloud migration currently limits images to PNG and JPEG, and rich text such as tables, code blocks and some styling may flatten to plain text, with differences reported. Vendor-specific handwritten and encrypted content is explicitly called out as not fully compatible, and logins, cloud storage quotas and network conditions remain under each manufacturer's control. ## The offline export is its own product For users who want out of vendor clouds entirely, the HTML export is a small product of its own: a built-in table of contents, keyword search, month filtering and media preview, packaged with attachments into a portable archive. The FAQ carries one operationally important instruction: to read an exported HTML archive on another computer, carry the complete ZIP and keep its resource directory together, because copying the lone HTML file strands the attachments. Word export targets people moving into other note systems, Markdown suits static-site and second-brain workflows, and TXT is the lowest-common-denominator backup. The combination, one login, four formats, merged or per-note files, positions the export path as the primary product and migration as the convenience layer on top, which matches the README's recommended learning order. ## Verification culture, written down The repository backs its claims with documents most tools skip. VERIFICATION.md records the validated scope, COMPATIBILITY.md details per-platform differences, PROJECT-CASE.md carries a case study with an English summary, and the demo screenshots disclose that they run on synthetic data with a simulated bridge, no real accounts or cloud requests. Bug reports are asked to include the software version, migration direction, exact steps and actual results, using self-generated content as examples, and to never submit passwords, verification codes, cookies, tokens or private notes. Logins happen in the vendors' official windows rather than in-app credential capture, which is the trust architecture you want in a tool that asks for cloud note access. Project facts: version 1.0.0, MIT for the self-written code with third-party licences catalogued separately, one release published, and the last push on 2026-09-09. CI runs offline checks, and the development README documents building from source. ## Against vendor tools and manual copy-paste Each phone vendor offers its own transfer assistant for the switch to its hardware, and those tools work well for contacts and photos; notes moving between different vendors' clouds is the gap they leave, and manual copy-paste through a web browser is the tedious fallback. Note Bridge fills the gap with selection, batch processing, format reporting and receipts, on Windows, which is the platform most users will have available during a phone switch. The boundary cases belong to the vendors: handwritten notes, encrypted notebooks and vendor-locked attachments may never transfer cleanly, and no third-party tool can force them. For the common case, years of text notes with photos accumulated in a Xiaomi or Huawei cloud, the tool converts the migration from an evening of copy-paste into a logged, verifiable batch job, and the export path means the next switch will not need any tool at all. ## Conclusion Note Bridge fits users in the Chinese phone ecosystem facing a brand switch or a backup itch, on Windows 10 or 11, who will follow the export-first order and treat the per-platform caveat table as binding. Skip it if your notes live in OneNote, Evernote or Notion, which are outside the seven platforms, or on macOS and Linux. Verify gently: install it, export five notes from your source cloud to HTML, open the archive, then migrate a single note and check text, images and grouping on the target before committing to a full batch. ## FAQ ### Will Note Bridge delete my original notes? No. Migration adds notes to the target cloud and preserves the source, and the README recommends exporting a backup and practicing with a single note before running a full batch. ### Which platforms does Note Bridge support? Seven: Xiaomi, OPPO, vivo, Huawei Notes, Honor, Meizu and WPS, all with local export and cloud migration. Per-platform caveats apply, such as Xiaomi's 4 MiB image limit and OPPO's chunked-upload restriction. ### Why have my migrated notes not appeared on my new phone yet? The tool migrates cloud to cloud; the vendor's sync then pushes to the phone. Check the target platform's web view first, and do not re-migrate the same batch, since a successful cloud write does not mean the handset has synced yet. ## Sources - [License: MIT](https://github.com/lingxuanqjc-alt/note-bridge-desktop/blob/main/LICENSE) - [lingxuanqjc-alt/note-bridge-desktop on GitHub](https://github.com/lingxuanqjc-alt/note-bridge-desktop) - [Project website](https://github.com/lingxuanqjc-alt/note-bridge-desktop#readme) - [README](https://github.com/lingxuanqjc-alt/note-bridge-desktop/blob/main/README.md) - [Releases](https://github.com/lingxuanqjc-alt/note-bridge-desktop/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lingxuanqjc-alt-note-bridge-desktop