https://github.com/zouloux/umami-import-csv
Import CSV from Umami Cloud into any custom Umami instance.
https://github.com/zouloux/umami-import-csv
Last synced: over 1 year ago
JSON representation
Import CSV from Umami Cloud into any custom Umami instance.
- Host: GitHub
- URL: https://github.com/zouloux/umami-import-csv
- Owner: zouloux
- License: mit
- Created: 2023-12-22T20:18:25.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-12-22T21:22:10.000Z (over 2 years ago)
- Last Synced: 2025-01-05T16:45:47.263Z (over 1 year ago)
- Language: JavaScript
- Size: 6.84 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
- License: LICENSE
Awesome Lists containing this project
README
# Umami import CSV
Import CSV from Umami Cloud into any custom Umami instance.
## Why
This is script can be used to import CSV from **Umami Cloud** into your **custom Umami instance**.
There is an export button on Umami Cloud but this feature does not exists in the open-source version.
So, if you need to migrate from **Umami Cloud** to an **On-Premise** version, here is a script helping you to do it.
## Usage
#### Install
- `git pull git@github.com:zouloux/umami-import-csv.git`
- `cd umami-import-csv`
- `npm i`
#### Export your CSV
Go to **Umami Cloud**, login and export the website you want to import as CSV.
Add this file into the script's directory.
#### Create website
Go to your **On-Premise Umami instance**, and create a new Website which will be imported.
Keep the created website id.
#### Setup
- Copy default config file `cp config.default.js config.js`
- Set file name or rename your CSV to match config
- Set `website.from`, it should be the exact website id in Umami Cloud ( the one you exported )
- Set `website.to`, it should be the exact website id you just created from your Umami instance
- Set postgres parameters. The script will check connection before continuing.
#### Run
- `node index.js` and follow instructions
## Known issues
Node process keeps running. I maybe forgot to remove some handler or the postgres connection is still running.