From Spreadsheet Chaos to a Clean Perfume System: A Migration Guide

You've got ingredients in one spreadsheet, formulas in another, maybe accords in a third. You want to be organized—one place, clean structure, no more hunting—but the idea of switching tools makes you groan. Re-typing everything? Learning a new app? Losing your data? No thanks.

I wanted to be organized—but I hated the idea of switching tools and re-entering everything.

— The pain every spreadsheet perfumer knows

Migration doesn't have to mean starting over. When your new system supports CSV import—and a clear structure—you can move your data in one go. This guide walks through CSV import/export, a clean structure, and how to use an ingredient sheet template so you go from spreadsheet chaos to a clean perfume system without the pain.

Why people want to be organized but hate switching

Switching tools usually means re-entering data by hand—ingredients, formulas, accords—or copy-pasting from messy spreadsheets into a new app. It's tedious, error-prone, and scary (what if something gets lost?). When migration is painful, people stay in chaos. When migration is a one-step import, switching becomes possible.

What you need: CSV import/export and a clean structure

CSV is the universal format for tabular data. If your current system can export to CSV (or Excel, which saves as CSV), and your new system can import CSV and map columns (name, category, dilution, price, note type, etc.), you move data in one go. No re-typing. The key is a clean structure: consistent column names, one row per ingredient, and a format your new tool understands.

Walking through CSV import

Migration in five steps:

1. Export your current data to CSV (or open your spreadsheet and Save As CSV).
2. Check the columns—Ingredient (name), Category, Type, Note (T/H/B), Dilutions, Price, and any notes or IFRA limit.
3. In Perfume Workbench, open Ingredients → Import and select your CSV (or Excel) file.
4. Map your columns to the app's fields if your headers differ (e.g. "Name" → Ingredient, "Dilution %" → Dilutions).
5. Review the preview and click Import. Your ingredients move in one shot.

Clean structure: what to include

Required and recommended columns for your CSV:

• Ingredient (required) — material name, e.g., "Hedione" or "Bergamot BF"
• Type — natural, synthetic, base, solvent, or modifier
• Category — e.g., Citrus, Floral, Woody (comma-separated if multiple)
• Note — Top, Heart, or Base (or T, H, B)
• Dilutions — e.g., 100% or "10% in DPG"
• Price — per gram (numeric only, no currency symbols)

Optional columns: IFRA limit, Aroma description, Substantivity, Date obtained, Inventory (g), Supplier link, CAS Number, Tags.

Ingredient sheet template

If you're starting from scratch or cleaning up a mess, use an ingredient sheet template: a CSV with the right column headers and one example row. Fill in your ingredients, save as CSV, and import into Perfume Workbench. No guesswork—one file, one structure.

How Perfume Workbench handles migration

Perfume Workbench is built for this. Import ingredients from CSV (or Excel): map your columns to the app's fields, review, and import. Your existing data—names, categories, dilutions, prices, note types—transfers in seconds. Export to CSV or JSON anytime for backup or to move data elsewhere. Clean structure, CSV in and out, no re-typing—that's how you go from spreadsheet chaos to a clean perfume system without the pain.