Bigcapital-migration

BigCapital-migration is a specialised tool designed to move your financial data into the BigCapital accounting platform.

  • Business & Finance
  • Databases
  • Tools & Utilities
BigCapital-migration is a specialised tool designed to move your financial data into the BigCapital accounting platform. It simplifies the transition from other software, ensuring your records are transferred accurately and securely so you can manage your business finances in one centralised place.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

68/100 Good

Maintained
100last commit 17 days ago
Popular
724,070 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM
GitHub stars
4,070
Open issues
331
Last commit
2026-11-04
Latest release
v0.25.45
License
AGPL-3.0
Activity
steady

Checked 16 days ago - source: GitHub (bigcapitalhq/bigcapital)

Resources & Compatibility

Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Make a .env file first Copy .env.example to .env and fill in the settings before starting the app. Without it, the app may not know how to connect to its database or other services. source
  • Start the Docker containers Run docker compose up -d, then check with docker-compose ps that MySQL on port 3306, Redis, and Mongo on port 27017 are up. If these Docker containers (isolated app pieces) are stopped, the app cannot save data or run. source
  • Run the database migrations After the containers are up, run pnpm run system:migrate:latest so the database gets the starting tables. If you skip this first setup, the app may not have the database structure it expects. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to create an environment file before starting Bigcapital?

Yes. Copy .env.example to .env and fill in the settings before starting the app. Without it, the app may not know how to connect to its database or other services.

Which Docker containers should I verify are running?

Check that MySQL on port 3306, Redis, and Mongo on port 27017 are up. If those containers are stopped, the app cannot save data or run.

What command should I run to initialize the database?

Run pnpm run system:migrate:latest after the Docker containers are up. This creates the starting database tables the app expects.

What email settings are configured for Bigcapital in Docker?

The Docker setup discussion centers on email environment settings for mail host, username, password, port, secure, sender name, and sender address.

Can I move existing accounting books into Bigcapital?

Bigcapital already has import machinery for getting books in. The discussion frames the remaining work as packaging a migration path, using an example of moving books from QuickBooks.

Answers sourced from github.com, github.com, www.reddit.com

Community

Collected 47 days ago - public community threads