Splid-to-KitchenOwl Migration

[JanJK2011]

🧾 Migrating Shared Expenses from Splid to KitchenOwl

My girlfriend and I had been tracking shared expenses in Splid, and we wanted to migrate all of that data into our self-hosted KitchenOwl instance.

Splid (Pro version) offers the option to export your data as an Excel file — specifically an .xls file that includes all expenses, categories, currencies, and individual shares.

However, KitchenOwl doesn’t support direct imports from Splid.
That’s where this script comes in.

---

🤝 Contributions Welcome

This script was written as a quick-and-dirty migration tool to solve a very specific use case.
It works reliably for German-language Splid exports and a standard KitchenOwl setup — but:

• It’s not bulletproof
• It’s not polished for every edge case
• And it could absolutely benefit from cleanups, refactoring, and extensions

So if you have ideas, improvements, or just want to make it less dirty — contributions are more than welcome.

---

🔄 What This Script Does

This Python tool reads your Splid Excel export and generates KitchenOwl-compatible SQL INSERT statements, ready to import into your PostgreSQL database.

✅ Features

• Supports any number of users dynamically
• Converts currencies to EUR, using the exchange rates in the Währungen sheet
• Maps categories to KitchenOwl IDs via a configurable mapping
• Calculates fair user shares using fractions.Fraction for exact ratios
• Adds recurring/static entries (e.g., salaries, income, corrections)
• Excludes specified titles/categories from statistics (e.g., "Zahlung", "Umbuchung")
• Outputs clean SQL for the expense and expense_paid_for tables

---

📥 Input Format

The script expects:

• A German-language export from Splid
• File format: .xlsx
  (you can convert .xls to .xlsx using OnlyOffice, LibreOffice, or MS Office)
• Two required sheets:
  • Zusammenfassung – detailed overview of all expenses and shares
  • Währungen – conversion rates per currency

---

🧾 Output

The output is a SQL file named:
your_export_kitchenowl_output.sql

It contains:

• DELETE FROM statements (optional cleanup)
• INSERT INTO expense (...) statements
• INSERT INTO expense_paid_for (...) statements (with factor-based shares)
• setval(...) statements to restore auto-increment sequences

---

⚙️ Configuration

Configuration is done via Python functions inside the script:

Function	Purpose
get_user_map()	Maps Splid names to KitchenOwl user IDs
get_category_mapping()	Maps Splid categories to KitchenOwl category_ids
get_static_entries()	Adds hardcoded recurring entries like salaries
should_exclude_from_statistics()	Defines titles/categories to exclude from stats

Example:

def get_user_map():
    return {
        "mySplidUser1": 2,
        "mySplidUser2": 4,
        "mySplidUser3": 5
    }

def get_category_mapping():
    return {
        "Restaurants": 5,
        "Lebensmittel": 2,
        ...
    }
    
def get_static_entries():
    return [
        ("2025-05-27", -2421.46, "Gehalt", 14, 2, 2)  # (date, amount, title, category_id, paid_by, paid_for)
    ]
    

📥 splid2kitchenowl.zip