Connect Nextcloud
Authenticate once with Nextcloud Login Flow v2 so uploads and imports target the right account.
Electron desktop app
Pull your Google mess into Nextcloud without babysitting scripts.
01 / Overview
Nextcloud Migrator is an Electron desktop app for one-way imports into Nextcloud. Connect your server with Login Flow v2, connect Google once, choose channels, then run imports with local credential storage, scheduled repeats, destination overrides, and file-level run history.
Current implementation is Google-first. Apple, Dropbox, and OneDrive are scaffolded as next adapters instead of bolted-on one-offs.
02 / Workflow
Connect the destination, connect the source, then let runs stay repeatable.
Authenticate once with Nextcloud Login Flow v2 so uploads and imports target the right account.
Choose the import channel that matches the data you want to move instead of forcing everything through one generic uploader.
Keep one-off imports manual or attach schedules for repeat runs, with run logs and item-level history stored locally.
03 / Channels
The Google path is already split into real migration targets instead of a vague “sync everything” button.
Manual browser-assisted media selection for targeted photo and video imports.
Headless ingestion of media files from Drive for repeatable manual and scheduled runs.
Exports Docs, Sheets, and Slides into conventional files before uploading them to Nextcloud.
Builds iCalendar output for import into the Nextcloud calendar stack.
Exports contacts as vCard so the import path is clear and reversible.
Creates a board per task list so Google Tasks can land in Nextcloud Deck with structure intact.
Turns Google Keep notes into Markdown files for a cleaner Nextcloud notes workflow.
Encrypted local secrets, destination overrides, dedupe, and local reports keep reruns traceable.
04 / Safeguards
Credentials are stored locally with Electron safeStorage instead of some always-on backend.
SHA-256 records help skip duplicate uploads when imports need to be resumed or repeated.
Jobs, runs, and item-level results are kept locally so failures can be traced without guesswork.
Stable binaries are published through the public releases repo. Use the latest build for your machine or browse the full release history and notes.