- Home
- Blog
- EDGEBIC How-To
- How to Move EDGEBIC to a New Computer
To move EDGEBIC to a new computer for a single-user install, export the database on the old PC from Settings and then DataSource, install EDGEBIC on the new PC, copy the exported file across, then point the connection at it with Browse and Apply and restart. In EDGEBIC by User Solutions the local database is a single file, so copying it moves the whole system, and users travel inside the database: you sign in on the new machine with the same accounts. The only thing that does not travel is a saved SQL Server password, which is account-bound and re-entered.
This post covers moving a single-user install. To make the snapshot the move relies on, see how to back up the EDGEBIC database; the full task library is at the EDGEBIC how-to hub.
Before You Start
- You know whether the install is single-user (a local file) or shared (a SQL Server database). The two paths differ.
- You have the installer for the new PC and administrator rights to run it.
- If you use SQL Server authentication, you have the SQL password to hand, because it will not carry across.
The Steps
Single-user install (local file):
- Export the database on the old PC. Open Settings, then DataSource, and click Export on the connection card. This makes a clean, consistent snapshot even while the application is open.
- Note the file path. The connection card shows the exact path of the live database if you prefer to copy that instead of the export (close EDGEBIC first if you copy the live file).
- Install EDGEBIC on the new PC and copy the exported file onto it.
- Point the connection at the copied file. On the new PC open Settings, then DataSource, keep the provider on SQLite, use Browse to select the copied file, and click Apply and restart.
- Sign in. Use the same accounts as before; users live inside the database.
Shared install (SQL Server database):
- Install EDGEBIC on the new PC. There is no data to copy.
- Point at the same database. Open Settings, then DataSource, choose SQL Server, and enter the same server and database.
- Re-enter the SQL password if needed. For SQL authentication, re-enter the password under the new Windows account. Windows authentication needs no re-entry. Click Apply and restart.
What Changes When You Save
| Surface | Effect |
|---|---|
| The database | For single-user, the copied file becomes the active database on the new PC. |
| User accounts | Travel inside the database; the same sign-ins work. |
| SQL Server password | Does not travel; re-entered on the new machine under the new account. |
| Display configuration and labels | Travel if you exported them to a file and import on the new PC. |
| The old PC | Untouched; its database remains as a fallback until the move is confirmed. |
How to Check It Worked
On the new PC after the restart, open Settings and then DataSource and confirm the connection card shows the copied file (single-user) or the same server and database (shared), with a green Connected chip. Then open Job View and confirm your orders and schedules are exactly as they were on the old machine. Sign in with an existing account to confirm users came across. When the data and accounts match, the move is complete and you can retire the old PC.
Common Mistakes
Copying the live file while EDGEBIC is open. A hot copy of the live file can catch an in-progress write. Use Export for a consistent snapshot, or close the application before copying the file directly.
Expecting the SQL password to travel. It is encrypted against the original Windows account and cannot be decrypted elsewhere. Re-enter it on the new machine, or use Windows authentication to avoid the issue.
Copying files for a shared install. With a shared SQL Server database there is nothing to copy. Install EDGEBIC and point it at the same server and database.
Deleting the old install too soon. Keep the old PC's database until the new machine has run real scheduling for a while. It is your fallback if anything looks wrong.
What to Do Next
The move depends on a good snapshot, so how to back up the EDGEBIC database is the companion habit. If the move is really a step toward multiple users, how to switch from SQLite to SQL Server in EDGEBIC and EDGEBIC deployment options explained cover the shared-server path. To repoint an existing install at a different file, see how to change the database connection in EDGEBIC, and the EDGEBIC product page shows where the database sits in the platform.
Expert Q&A: Deep Dive
Q: We are replacing a planner's laptop and a year of scheduling data lives on it. What is the exact sequence to move it cleanly?
A: For a single-user install on the local file, it is four moves. First, on the old PC open Settings and then DataSource and click Export to make a clean snapshot of the database. Second, install EDGEBIC on the new PC. Third, copy the exported file to the new machine; the DataSource connection card on the old PC shows its exact path if you want the live file instead of the export. Fourth, on the new PC open Settings and then DataSource, keep the provider on SQLite, use Browse to select the copied file, and Apply and restart. Sign in with the same accounts, because users travel inside the database. The only thing that does not travel is a saved SQL Server password, which is account-bound and must be re-entered.
Q: The planner uses SQL Server authentication for a shared database. Does moving to a new PC break the login?
A: The saved SQL password does not travel, but nothing is lost. A SQL authentication password is stored encrypted and tied to the Windows account that entered it, so on a new machine or a new account it cannot be decrypted. On the new PC, install EDGEBIC, open Settings and then DataSource, select SQL Server, enter the same server and database, re-enter the SQL password under the new Windows account, and Apply and restart. If the database is on a shared SQL Server you are not really moving data at all, just repointing a new install at the same database, which is the easy case. Windows authentication avoids the password re-entry entirely.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
