Switch from Plausible

Plausible's CSV export uses the same file names and columns that misomoon's CSV import reads, so your daily history moves as it is. Your tracking calls keep their shape: plausible('Signup', { props }) becomes misomoon('Signup', { props }). Revenue history and goals stay behind.

#Add misomoon next to Plausible

1. Add your site in misomoon and paste its script tag into the <head> of every page, next to Plausible's (Track your site).
2. Leave both scripts on for a week or two, until misomoon's numbers look right to you.

#Replace Plausible's calls

The call has the same arguments: an event name, then props, revenue, callback, and interactive. On most sites, replacing plausible( with misomoon( is enough.

The data-misomoon-* attributes need Tagged events, which a new site has on (Choose what to track). If you send revenue from a payment provider's webhook instead, connect it and drop revenue from the call, or each sale counts twice.

Goals don't move. Add each one again in Settings > Goals (Turn goals into conversions). A goal counts the events misomoon already collected, so you can add it at any time.

#Bring your history

Use the export in Plausible's site settings. The Export stats download on the dashboard holds totals for one period, not days, and the upload refuses it with no imported_*.csv files found (expected a CSV export).

1. In Plausible, open Site Settings > Imports & Exports and click Export to CSV.

2. Download the ZIP file from the email Plausible sends. On Plausible Cloud, the link works for 24 hours.

3. Unzip it. Plausible exports every day up to its last visit, and misomoon skips the days it already counted (Days that count once). The command drops Plausible's own engagement events from the custom events file, a name misomoon keeps for itself, and zips the files:

   shCopy

   for f in imported_custom_events*.csv; do
    awk -F, 'NR == 1 || $2 != "engagement"' "$f" > "$f.new" && mv "$f.new" "$f"
   done
   zip plausible-history.zip imported_*.csv

   The second column of the custom events file is the event name.

4. In misomoon, open Settings > Integrations, click Upload CSV or zip, and pick plausible-history.zip.

The import fills the top-line numbers, the chart, sources, UTM tags, pages, entry and exit pages, countries, devices, browsers, operating systems, and custom events, with bounces, visit duration, time on page, and scroll depth. Imported days appear only in reports without filters (What imported data fills).

If you uploaded the wrong file, delete the import and upload again.

#Remove Plausible

Once the import shows in misomoon, remove Plausible's script tag and its window.plausible snippet. Plausible keeps your data until you delete the site there.

#What stays behind

• Revenue history. Plausible's export doesn't include revenue, and misomoon imports none.
• Goals and funnels. Add them again in misomoon.
• Custom properties. misomoon skips imported_custom_props, so imported events have no property breakdown.
• Cities and hostnames. misomoon ignores the city column and the hostname column of imported_pages. A site with several hostnames gets their paths added together.
• Region names. Plausible exports region codes, such as US-CA, and misomoon's own data names the region, such as California. The two sit on separate rows in Regions.
• Visitor counts of File Download and Outbound Link: Click events. Plausible writes a row per link, and misomoon adds the rows up, so a person who clicked two links counts twice. The event counts are exact. misomoon renames these events Download and Outbound link, and Form: Submission becomes Form sent.

#Sources

Checked on 2026-10-25.

• Plausible: CSV import and export, Export stats, export columns in the code, custom events, revenue, script options, the current snippet