Back Up Invoices Before a Browser Change

The short answer

In “Settings & customers”, use “Save backup” and keep the JSON file somewhere you control. Save issued invoice exports separately. Before “Restore backup” on a used browser, back up that browser too: restored copies of the same saved records take precedence.

Open the free tool

Identify the collection you need to keep

E-Invoice Studio stores invoices, customers, products and settings in this browser. Another computer does not automatically see that collection. Even two browser profiles on the same device can be separate working places. Before a move, open the profile where you actually created the records and examine “My invoices”. Do not assume that the browser showing the site most recently is the one containing all your drafts.

For an illustrative small business, the working set might include several drafts, saved customers and issued invoice copies. These are example records, not a claim about a tested user account. Write a short inventory of the kinds of material you need. Keep the distinction between local editable records and the files already delivered to customers. A full working backup serves recovery; an issued PDF or XML serves a separate document purpose.

Create a backup before changing anything

Open “Settings & customers”, find “Backup” and select “Save backup”. The application downloads a JSON file containing its saved invoices, customers, products and settings. Verify that the browser actually saved the file in the expected folder. A completion message alone does not tell you whether you can locate the download later. Give the copy a useful date-based name without losing its extension.

Keep the browser collection intact during this preparation. You do not need to delete all records merely to make a backup. If you are changing computers, copy the downloaded backup through a method appropriate for your own business data. The tool does not provide an automatic cloud transfer. Avoid placing the file in a broadly shared folder when its recipients do not need the customer and invoice details it contains.

Distinguish JSON, invoice files and CSV

The backup is a working collection in the application’s own format. An ordinary invoice PDF is not interchangeable with it. The file-opening workflow can read an invoice without recreating every customer, product and setting from the old browser. Likewise, a CSV export is useful for the rows it contains, but should not be treated as a full application backup. Identify each file by its purpose rather than judging all downloads as equivalent copies.

Keep issued PDF and XML files in your established document records. This guide does not specify legal retention periods or certify an archive. Consult current official requirements and your adviser for the actual business case. A local browser backup alone should not be described as legal compliance, nor does deleting a draft collection decide what issued documents you must retain. These are separate workflow and recordkeeping questions.

Check the destination before restoring

Open E-Invoice Studio in the destination browser and inspect whether it already contains data. If it does, save its own backup first. Restoration adds records, and where the backup represents the same saved record, the backup’s version takes precedence. Unrelated records are not automatically removed by this restore workflow. That behavior matters if two browsers have been used independently: it is not a conflict review screen that asks you to choose a version for every collision.

Do not restore an old backup over current work without considering that consequence. If you merely need to read one historical invoice, use a suitable saved invoice file rather than importing an entire old working collection by habit. Establish which browser will be the main workspace after the move. Continuing to edit both copies can create uncertainty about which draft or customer address is current, even when both computers appear to work normally.

Restore and reconcile the result

Choose “Restore backup” and select the genuine E-Invoice Studio backup JSON. Wait for the restore message and reload behavior, then inspect “My invoices” and the saved customer information. Compare the expected records with your short inventory. A displayed count is helpful, but also examine a representative older entry and the newest relevant draft. They should contain the information you intended to move, rather than merely having familiar filenames.

Check the company settings and numbering configuration before creating the next real invoice. Restoration can bring back those settings as well as document records. Do not issue a practice invoice to a customer as a migration test. If you use an example to inspect the interface, keep it separate from real records and follow the tool’s sample behavior. Preserve both source and destination backups until you are satisfied with the reconciliation.

Recover from an unreadable or incomplete backup

If the file is rejected as not being a backup, check that you selected the JSON backup rather than a PDF, XML or CSV. Renaming another file with a .json extension does not convert it. Keep the original rejected copy for investigation and return to the source browser while its data still exists. Save a fresh backup there instead of editing unknown fields in the file until the application accepts it.

A private window or a browser that refuses persistent storage can keep work only for the open session. Read the storage warning when present and save needed exports before closing. If browser data was already cleared and no backup exists, this guide cannot promise recovery. The practical protection is preparation before the change. Once the destination is checked, document the chosen working profile and store the appropriate backups in your controlled records, distinct from the files intended for customers.

Questions you might still have

Is a PDF download a full backup?

No. It is an invoice file. The application backup includes its saved working collection and settings.

Does restore erase all unrelated records?

The implemented restore adds records. For the same saved record, the backup’s version wins; unrelated records remain.

Should I back up the destination first?

Yes if it already holds work. That preserves a recovery point before restored versions take precedence.

Can CSV restore all customers and drafts?

Do not treat it as a complete backup. Use the application’s own JSON backup workflow.

Does the backup provide a legally certified archive?

This guide makes no such claim. Verify applicable recordkeeping requirements separately with official guidance and qualified support.

Can I recover data after clearing the browser without a backup?

Recovery is not promised. Preserve sources and make the backup before clearing or moving the working profile.

Sources & useful details

These guides are written from the current LoschaZ tools and the sources listed above. Examples are illustrations, not tests on every device or promises of an identical result.