How to Migrate Your Handmade Inventory Spreadsheet to Software
Migrating a handmade inventory spreadsheet to software means transferring your materials, product recipes, and current stock counts into a dedicated inventory system — structured and cleaned so the software reflects reality from day one, not after weeks of correction.
Inventory management software is only useful if it reflects reality. And for most handmade makers, reality lives in a spreadsheet — sometimes a very old, very color-coded one that has been patched and extended for years. Moving that data into software is not complicated, but it does require doing things in the right order. Skip steps, and you end up with stock counts you cannot trust. Do it carefully, and you walk away with a system that actually runs your business instead of one more tool you have to babysit.
This guide covers the full migration process: what to fix before you import, how to run both systems safely during the transition, and the specific issues that trip up handmade makers that generic migration guides never mention.
Why Handmade Inventory Spreadsheet Migrations Usually Go Wrong
Most migration guides skip straight to the fun part: logging into the new software and clicking import. That is where things break.
The data in a working spreadsheet is almost never clean enough to import directly. Names drift over time. A material you buy regularly might appear as "lavender EO," "Lavender Essential Oil," and "lav EO" across different tabs. A product might have three variants tracked as three separate rows with no shared identifier. A cost column might have some cells in dollars-per-ounce and others in dollars-per-pound from the time you switched suppliers.
None of this matters when you are the only one reading the spreadsheet, because you carry the context in your head. Software does not have that context. It reads what is there and nothing else.
The other reason migrations fail is anxiety. Makers have real business records in those spreadsheets. Supplier costs, production history, stock counts built up over months or years. Handing that to an unfamiliar system feels risky. And so people delay, or they do a partial import and try to maintain both systems indefinitely, which is worse than either option alone.
The answer to both problems is the same: clean the data first, then import, then run in parallel for a defined period before cutting over completely. That sequence makes the migration predictable and reversible.
Step 1: Back Up Everything Before You Touch Anything
Before you change a single cell, make an archival copy of your spreadsheet and store it somewhere you will not accidentally overwrite it. A separate folder, a cloud backup, a dated export file — whatever works. This is your rollback option if anything goes wrong.
Label it clearly. Something like inventory-backup-[date]-do-not-edit works fine. The goal is to have a snapshot of your data exactly as it existed before migration began, so you can compare against it or restore from it if needed.
This step takes two minutes and removes the single biggest source of migration anxiety. You are not committing to anything yet. You are just making it safe to proceed.
What happens to your backup if your spreadsheet is the only thing standing between you and lost inventory data?
A backup file protects your past, but it does not fix the underlying problem. Batchforja keeps your materials, recipes, and batch history in one place so a corrupted spreadsheet is never your only safety net.
Get early access →Step 2: Clean Your Data Before You Import It
This is the step most guides skip, and it is the most important one. For most makers with 20–50 materials and 10–30 products, expect two to four hours depending on how consistent your data is — larger catalogs or years of accumulated drift may take longer. A few hours of cleanup before importing will save you days of correcting bad data after the fact.
Standardize material names
Go through every material in your spreadsheet and make sure each one has exactly one name, spelled and formatted the same way everywhere it appears. Create a reference list if it helps. "Lavender Essential Oil (Bulgarian)" should be that, and only that, across every tab and column.
Pay special attention to materials that appear across multiple product recipes. If your shea butter shows up three different ways, the software will import it as three different materials, and your stock count will be split across all three.
Resolve unit inconsistencies
Decide on one unit of measure per material and convert everything to it. If you track cocoa butter in ounces in some places and grams in others, pick one before you import. The same goes for cost per unit. Every material should have a single, current cost figure in a consistent unit.
If you are not sure what you paid most recently for a material, check your last supplier invoice. Use that number. It does not have to be perfect — it has to be consistent.
Handle variants correctly
Products with variants (different scents, sizes, colors) are a common source of import confusion. If your spreadsheet tracks each variant as a separate row with a slightly different name, you will need to decide how your software handles variants before you structure the import file.
Most inventory software designed for handmade makers treats variants as options under a single parent product. That means your "Lavender Soap 4oz" and "Eucalyptus Soap 4oz" might be two variants of "Bar Soap 4oz" rather than two completely separate products. Restructure your data to match how the software expects it before importing.
Flag made-to-order and seasonal items
Made-to-order products do not have a standing stock quantity. Seasonal items may be inactive for months at a time. Both of these need to be handled differently from your standard in-stock products. Go through your product list and mark which items fall into these categories so you can set them up correctly in the software rather than importing them as regular inventory items with a stock count of zero.
Fill in missing recipe data
If any of your products are missing ingredient quantities in your spreadsheet, fill them in now. A software system that tracks production through recipes cannot function if the recipe is incomplete. It is fine to estimate if you do not have exact records, but make a note so you can refine it later.
Step 3: Structure Your Import Files
Most inventory software accepts imports as CSV files and provides templates that show the expected column structure. Download those templates before you start reformatting anything.
You will typically need separate import files for:
Import File | Key Columns |
|---|---|
Materials | Name, unit of measure, stock quantity, cost per unit, reorder threshold |
Products | Name, SKU, stock quantity, sales price |
Recipes / Bill of Materials | Product name, material name, quantity per batch |
Work through your cleaned spreadsheet data and map each piece of information to the correct column in the import template. This is methodical work, not complicated work. Take it section by section.
One practical note: you do not need to import your full order history. Most makers are better off starting with a current snapshot of materials and products, then letting the software build order history going forward. Historical orders add complexity without much operational benefit unless you need them for tax reporting.
If your software of choice offers a dedicated import tool or migration support, use it. Batchforja's inventory software for handmade makers, for example, is built specifically for handmade makers and is designed to handle the kinds of messy, real-world data most makers are working with — materials, products, recipes, and production history all in one place.
Step 4: Run a Test Import First
Before you import your full dataset, import a small slice of it — maybe 10 materials and 5 products with their recipes attached — and verify that everything came through correctly.
What a clean test import looks like
Material names match what you entered with no duplicates created
Units and costs are correct
Recipe quantities are accurate for each product
Stock quantities reflect current reality
Variants are linked to the correct parent product
If anything looks off, go back to your import file and fix it before proceeding. It is much easier to correct a formatting issue in a CSV file than to manually edit 200 records inside the software after the fact.
If only some records import correctly, do not try to manually fix the failed ones inside the software. Go back to the CSV, correct the rows that failed, and re-import only those rows. Most software will skip duplicates or let you overwrite by SKU — check the documentation before re-importing to avoid creating duplicate records.
Once the test batch looks right, import the rest of your data.
Step 5: Run Both Systems in Parallel for 30 Days
This is the step most people skip in their eagerness to be done with the spreadsheet. Do not skip it.
For the first 30 days after importing, update both your spreadsheet and your software when anything changes. A new order comes in: record it in both places. You receive a material delivery: log it in both places. You complete a production run: record it in both places.
This sounds like extra work, and it is. But it serves a specific purpose: it lets you catch discrepancies while you still have a reliable reference point.
For makers selling across Etsy and other platforms simultaneously, Etsy's seller handbook covers multi-channel inventory basics worth reviewing before you configure channel-specific stock settings.
The spreadsheet you trust today is only trustworthy because you built the context in your head. Software reads what is there — and nothing else.
How to handle discrepancies during the parallel period
If your software shows 48 bars of soap in stock and your spreadsheet shows 52, something was miscounted or misconfigured during import. Common causes include a stock quantity that imported from the wrong column, a duplicate material entry splitting the count, or a production run that was logged in the spreadsheet but not reflected in the imported opening stock. Check your import CSV first — most discrepancies trace back there rather than to the software itself.
After 30 days, compare your stock counts between the two systems. If they match, or if you can account for any differences, you are ready to cut over. If there are unexplained gaps, investigate before closing the spreadsheet.
Inventory accuracy problems are a well-documented source of operational loss for small product businesses — stock discrepancies compound quickly once they go undetected. For broader context, Shopify's inventory management guide covers how accuracy issues compound over time.
Step 6: Cut Over Completely and Close the Spreadsheet
At the end of your parallel-run period, pick a specific date to make the software your single source of truth. On that date, stop updating the spreadsheet. Archive it the same way you archived the original backup — dated, labeled, set aside.
Do not delete it. Do not keep updating it. Archive it.
Keeping the spreadsheet active after you have cut over is how you end up with two systems that gradually diverge from each other until neither one is accurate. The archived copy is there if you ever need to reference historical data. It is not there to be maintained.
For the first few weeks after cutting over, pay extra attention to your stock counts after each order and production run. You are building confidence in the new system. Most makers find that within a month, the software starts to feel more reliable than the spreadsheet ever did, because the numbers update automatically instead of requiring manual intervention every time something changes.
The IRS recommends keeping business records for at least three years, which is another reason to archive rather than delete your old spreadsheets. They may be useful for tax purposes even after they are no longer your active inventory system.
What to Do If You Get Stuck
The most common sticking point is messy recipe data. If you have products with many ingredients and you are not sure your quantities are right, do not let that block the entire migration. Import your materials and products first, then build the recipes inside the software directly. It is slower than importing, but it lets you verify each recipe as you go rather than finding errors after a batch import.
The second most common sticking point is variants. If your software's import template does not handle variants the way your data is structured, reach out to their support team before you spend hours reformatting files. Most tools built for handmade makers have encountered this before and can tell you the fastest path through it.
If you are considering which software to migrate to, the key things to look for in handmade inventory software include recipe-based production tracking, multi-channel stock sync, and an import process that accounts for the realities of small-batch maker data. Not all tools are built with those needs in mind.
It is also worth understanding what a bill of materials for handmade products should include before you import your recipes, so you are not missing any cost or quantity data that the software needs to do its job.
And if you are unsure whether your current pricing even covers your costs once everything is properly tracked, the free product pricing calculator is a useful starting point for verifying your numbers before you formalize them in a new system.
Still rebuilding your recipes one ingredient at a time because the import would not cooperate?
Batchforja is built around the way handmade sellers actually work, so you can enter recipes directly inside the software and check quantities as you go, without wrestling a CSV template into the right shape first.
Get early access →
Key Takeaways
Clean the data before you import it — a few hours of cleanup prevents days of correcting bad data after the fact.
Back up your spreadsheet before you change anything. This is your rollback option and it takes two minutes.
Clean your data before importing, not after. Standardize material names, resolve unit inconsistencies, and fix variant structure first.
Flag handmade-specific items early. Made-to-order products, seasonal items, and multi-level components need to be handled differently from standard inventory.
Run a test import with a small subset of data before committing your full dataset.
Run both systems in parallel for 30 days. This catches discrepancies while you still have a reference point to compare against.
Pick a cutover date and archive the spreadsheet. Do not maintain both indefinitely. The parallel period is a bridge, not a permanent state.
You can reverse course. Your archived backup is always there. Knowing that makes it easier to move forward.