Preparing Your EDGEBIC Install Before Migrating

Before migrating, prepare your EDGEBIC install by choosing the right deployment: SQLite for a single planner, SQL Server for a team, with the first-time setup wizard handling the connection either way. In EDGEBIC by User Solutions, this choice is about how many people share the schedule, not about setup difficulty, because the wizard connects the data source for you. Getting the deployment right before you import means your migrated data lands in the environment you will actually run on, and you confirm which one that is on the Settings tab.

Decide the deployment before you import

A migration imports data into a running EDGEBIC install, so the install has to exist first, and how it is deployed shapes everything after. The good news is that the decision is simple, because it comes down to a single question: how many people will share the schedule?

That question has two answers, and EDGEBIC has a deployment for each. Deciding before you import means you build your masks against the environment you will keep, rather than importing twice. This preparation step sits at the very front of the RMDB to EDGEBIC guide.

SQLite for a single planner

If one planner runs the schedule, EDGEBIC runs on SQLite, and there is effectively no database administration. The planner installs the application, the first-time setup wizard connects the data source, and they are importing within the hour. Nothing to provision, no server to stand up.

This is the ideal footing for a pilot. When you plan an EDGEBIC pilot on one cell, the goal is to test the engine cheaply, not to build infrastructure, and a single-user SQLite install is the lightest possible way to do that. One person, one machine, data imported through saved masks, comparing EDGEBIC's dates against RMDB for one cell.

SQL Server for a team

When several planners need to work against the same schedule, EDGEBIC runs on SQL Server. IT provides a database, and the planners connect to it, so everyone sees the same data. The first-time setup wizard handles that connection too, pointing EDGEBIC at the server rather than asking anyone to build a schema by hand.

This is the deployment you grow into. A pilot that succeeds and widens to a team moves from single-user SQLite to a shared SQL Server deployment, and the same import masks you built load your data into it. The choice is about people, not difficulty: the wizard does the connection work in both cases.

The setup wizard does the connecting

Whichever deployment you choose, the first-time setup wizard handles the database connection. For SQLite that means there is nothing to configure beyond the wizard. For SQL Server it means you point EDGEBIC at the server through the wizard instead of running a manual database build.

After setup, the data source is confirmed on the Settings tab, so you can always see and change which database EDGEBIC is running against. Preparing the install is therefore a matter of choosing the deployment and letting the wizard connect it, not a database engineering project.

What to tell IT

If your IT team asks what EDGEBIC needs before you commit to a migration, the footprint is light. EDGEBIC is a Windows desktop application built on .NET 8, with two deployment shapes:

• Single planner: SQLite, no database server, no database administration. Essentially a desktop install.
• Team: SQL Server, so IT provides a database the planners connect to, with the setup wizard handling the connection.

There is also no ERP connector to provision. Data moves through Excel, CSV, and database import-export masks, so IT does not need to build a live integration. The ask is a Windows machine and, for a team, a SQL Server instance, with the wizard doing the connection work.

Start small, grow into a team

Because the deployment choice is about how many people share the schedule, it is not a one-way commitment. You can start a pilot on single-user SQLite and move to a team SQL Server deployment when you widen, carrying your data across with the same masks.

That matches the phased shape of the whole migration: single-user for the pilot, team server when several planners work the same plan. You are not choosing your final architecture up front; you are matching the deployment to the current stage. The staged approach is laid out in a phased migration plan to EDGEBIC.

Common pitfalls

• Building masks against the wrong environment. Decide the deployment before you import so you do not have to redo the work in a different data source.
• Over-provisioning for a pilot. A single-planner pilot does not need SQL Server. SQLite keeps the pilot light.
• Assuming an integration project. There is no native ERP connector to build. Data moves through masks.
• Losing track of the data source. Confirm which database EDGEBIC runs against on the Settings tab, especially when you move from a pilot to a team.

The takeaway

Preparing your EDGEBIC install before migrating is a single decision: SQLite for a single planner, SQL Server for a team, with the first-time setup wizard handling the connection either way. Start a pilot light on single-user SQLite, grow into a shared SQL Server deployment when several planners work the same schedule, and carry your data across with the same import masks. Confirm the data source on the Settings tab, and tell IT the footprint is a Windows machine and, for a team, a SQL Server instance. See the platform in full on the EDGEBIC overview, read the whole path on the RMDB to EDGEBIC guide, and once the install is ready, work through an EDGEBIC migration checklist.