Free Consultation

Moving Data from Odoo Local to Production Using the Database Manager

If you’ve been building and testing in Odoo on your local and now it’s time to push that work to your production server, you don’t need anything fancy, Odoo has a built-in way to do this through the Database Manager. No command line, no scripts, just export and import.

In this post, I’ll walk through exactly how I move data from my local Odoo environment to production using backup and restore.

Step 1: Finish Your Work Locally

Before exporting anything, make sure your local environment is in the state you actually want to push live also with all your configuration, records, and test data should be exactly how you want production to look.

Tips: If your local database still has test/demo data you don’t want in production, clean it up first. Once it’s in the backup, it’s going live too.

Step 2: Open the Database Manager

On your local Odoo instance, go to:

http://localhost:8069/web/database/manager

This page lists all databases running on your local Odoo instance, along with options to Backup, Restore, Duplicate, or Delete each one.

Step 3: Back Up Your Local Database

  1. Find your database in the list.
  2. Click Backup.
  3. Enter your master password (set in odoo.conf as admin_passwd or it will be generated in the first open).
  4. Choose the backup format usually zip (includes filestore) rather than just the SQL dump.
  5. Click Backup and save the downloaded .zip file somewhere you can find it.

Step 4: Open the Database Manager on Production

Now switch over to your production server’s database manager:

https://yourdomain.com/web/database/manager

Step 5: Restore the Backup on Production

  1. Click Restore Database.
  2. Upload the .zip file you downloaded from local.
  3. Enter a new database name for production (or reuse an existing name if you’re intentionally overwriting).
  4. Enter the master password for the production instance.
  5. Click Restore.

Odoo will unpack the zip, recreate the database, and restore the filestore. Depending on your data size, this can take anywhere from a few seconds to several minutes.

Step 6: Verify Production

Once the restore finishes:

  • Log into the new/updated production database.
  • Spot-check a few records, especially anything with attachments (images, PDFs) to confirm the filestore came through correctly.
  • Check installed modules and settings match what you expect.

A Few Things Worth Knowing

  • The database manager must be enabled. If you don’t see /web/database/manager, check that list_db = True in your odoo.conf, some production setups disable this page for security, since anyone who reaches it can see your database list.
  • Master password ≠ login password. This is the admin_passwd set in odoo.conf, not any user’s Odoo login.
  • Restoring can overwrite an existing database. If you restore into a name that already exists, double-check you actually want to replace it, there’s no undo.
  • Large filestores mean large zips. If your local database has a lot of attachments, the backup/restore process will take longer and the zip file can get big. Keep an eye on upload size limits, especially if your production server sits behind a reverse proxy (nginx client_max_body_size, for example) that might reject a large upload.
  • This method fully overwrites, not merges. This is best for pushing a full snapshot from local to production (like an initial go-live or a full refresh), not for syncing partial changes. If you only need to move a few records, that’s a different workflow (manual export/import of specific data).

Book a Free Consultation

Haven’t found the right solution yet?
Tell us about your needs, and let’s discuss the best solution together.

Free Consultation

Project description.

Built a private marketplace research and purchase planning platform for Shopee. The system tracks product performance over time, estimates sales velocity and gross revenue, analyzes demand across product variants, and turns the research into actionable purchasing plans. It also calculates supplier costs, shipping, platform fees, margins, planned investment, and estimated earnings to support data-driven sourcing decisions.

Skills and deliverables

Full-Stack Development, Web Application Development, Data Analysis, Business Process Automation, Business Intelligence

Shopee Marketplace Research & Purchase Planning Dashboard

We built this application to solve a common problem in marketplace sourcing: finding products is easy, but deciding what is actually worth buying, which variant to prioritize, and how much inventory to purchase requires much more analysis. Instead of relying on a single product snapshot, the system organizes products into research collections and tracks their marketplace performance over time.

Product research & tracking

Products can be added individually or collected from marketplace stores and organized into dedicated research collections. The system keeps historical observations so users can compare changes between captures instead of relying only on the latest marketplace data. This makes it possible to estimate metrics such as: – Sales velocity – Estimated daily gross revenue – Price changes – Product movement over time – Variant-level demand

Variant demand analysis

One of the most important parts of the system is identifying which variants are actually driving sales. Instead of treating a product as a single item, the application analyzes sales movement at variant level and shows each variant’s contribution to recent demand. This helps identify which sizes, models, or variations should be prioritized when purchasing inventory.

Purchase planning

Research data can then be converted directly into a purchasing plan. For every product and variant, the user can enter supplier pricing, shipping costs, purchase quantities, exchange rates, and other operational costs. The system automatically calculates: – Planned inventory investment – Shipping cost – Marketplace/platform fees – Net margin per unit – Net margin percentage – Estimated earnings – Total batch investment This allows purchasing decisions to be evaluated before committing capital.

Why We built it

The goal was to replace a workflow that would normally require multiple spreadsheets, manual marketplace checks, and repeated calculations. The resulting workflow became: Discover products → Track performance → Analyze demand → Select variants → Plan purchasing → Estimate margins Everything is kept in one application, making the research and sourcing process easier to review, repeat, and scale.

Result

The platform turns raw marketplace observations into actionable purchasing information. Instead of choosing products based only on intuition or current sales numbers, users can evaluate sales movement, variant demand, sourcing cost, expected margin, and required investment before making a purchasing decision. Built as an end-to-end internal tool, from data collection and analysis to the final purchasing workflow.

Project description.

Built a browser-based tool that converts Shopee/SPX order exports into clean, print-ready shipping labels. It supports multiple Excel/CSV files, combines orders into one preview, and automatically generates QR codes, barcodes, tracking numbers, and product information for 68 mm thermal printers. All order data is processed locally in the browser for better privacy, eliminating repetitive manual label formatting.

Skills and deliverables

Laravel, Business Automation, CSV, Microsoft Excel

Shopee SPX Order Label Maker for Thermal Printing

This tool was built to simplify the shipping label preparation process for Shopee SPX orders. The existing workflow required order data to be exported from Shopee and manually formatted before it could be printed on a thermal printer. This became repetitive and time-consuming, especially when processing multiple orders at once.

We built a browser-based label generator that reads Shopee Excel/CSV exports and automatically converts the order data into clean, print-ready SPX labels. The tool automatically handles: – Tracking numbers – QR codes – Barcodes – Product names and variants – Order quantities – Multiple order files at once – 68 mm thermal printer formatting Users can review all generated labels before printing, without having to manually copy or reorganize the order information.

The order files are processed directly inside the browser instead of being uploaded to a server. This keeps customer and shipment data private while also making the tool fast and simple to use.