If you are running Sage BusinessVision, you already know the clock is ticking. You have seen the sunset notices, and you are likely already weighing or planning your move to Spire.

What is harder to find is a straightforward, practical account of what actually happens once you hand over your data.

Because Spire provides direct, built-in conversion tools for BusinessVision, moving your data is far closer to a turnkey process than migrating off older, non-BV software. But turnkey does not mean instantaneous, and it does not mean flipping a switch on a Friday afternoon.

Here is what the conversion path actually looks like, how your data gets used along the way, and why the trial phase is your best safeguard before go-live.

The Real Sequence: From Tailored Demo to Working Sandbox

A proper conversion begins long before your actual cutover weekend. In fact, it starts before you even sign a contract.

The first step is handing over a backup copy of your BusinessVision data. We take that backup and run it directly through Spire's native conversion tools. At this stage, we do not adjust settings or clean up messy records. We let the data come over exactly as it sits in BusinessVision.

This raw conversion serves two critical purposes:

1. A tailored demo using your real operations. Instead of watching a sales rep click through generic sample data for a fictional bicycle company, you see your own customers, your active items, and your actual order history inside Spire. You can immediately see how your daily workflow looks in the new interface.
2. A working sandbox for setup and training. If you decide to move forward, that converted database becomes your non-production sandbox. This is where we design and print sample invoices, purchase orders, and packing slips to test your custom forms. It is where we build custom reports against your real numbers. Most importantly, it gives your team a zero-risk environment to train and practice daily tasks without touching live operations.

Treating this initial conversion as a sandbox is deliberate. It acts as a diagnostic window, revealing exactly what needs to be adjusted before you commit to a live cutover.

The Surprises That Surface in the Data

When a business runs the same system for ten, fifteen, or twenty years, data quirks accumulate. These are not signs of a broken software platform; they are simply the natural result of decades of real-world operations, changing staff, and evolving processes.

Because Spire's conversion routines are thorough, they hold up a clear mirror to your historical data. Running that initial conversion often brings several common situations to light:

1. Trial balances out of balance. In older datasets, historical general ledger balances sometimes do not balance cleanly. While this does not prevent you from using the sandbox for training, it is something that must be reconciled before the final cutover.
2. Missing date fields halting a conversion. Occasionally, specific historical transaction rows lose a date value over time. Spire requires valid dates to build its relational database, so an empty date field will pause the conversion routine until that specific record is corrected.
3. Negative inventory running millions in the red. If a company used BusinessVision primarily for order processing and invoicing rather than full inventory management - recording sales without entering purchase orders - items set as physical inventory will steadily accumulate negative balances. Seeing an inventory valuation millions of dollars in the red can be jarring, but it is simply a configuration mismatch.
4. Decades of inactive accounts and obsolete items. Companies with data stretching back before 2000 often carry thousands of former customers and discontinued parts. Spire will convert every record it finds, bringing legacy clutter right along with active accounts.
5. Dormant warehouses carrying forward. Spire converts every warehouse set up in BusinessVision, even locations unused for a decade. Because modern ERP systems maintain strict audit trails and resist deleting tables with historical activity, those old warehouses will remain visible unless addressed.

What Real Cleanup Looks Like Before Go-Live

The entire reason for running a sandbox conversion months before your target launch date is to give you time to address these findings without operational pressure.

Cleanup is a shared effort between your team and your implementation partner:

• What you can clean up before the final conversion. For obsolete items, inactive customers, or dormant warehouses, the best strategy is often to archive and purge very old history inside BusinessVision before running the final live export. For mass updates, providing spreadsheets of accounts or parts to mark inactive allows your consultant to batch-update records rather than having your staff edit them one by one.
• What your consultant fixes under the hood. For structural hurdles like missing date fields, out-of-balance ledgers, or resetting negative physical inventory to non-physical items with zeroed-out balances, an experienced partner works behind the scenes to adjust the data so the live conversion runs cleanly.

Treating data cleanup as a deliberate, methodical phase ensures that when go-live day arrives, you are moving into a clean, well-structured environment.

What This Means for Your Timeline

A data conversion done properly is not a single weekend event. It is a phased process that runs parallel to your planning and training.

When an implementation partner pauses to point out an out-of-balance subledger, missing transaction dates, or obsolete master records during the sandbox phase, that is not a setback. That is the system working exactly as intended. Finding and resolving data oddities in a sandbox takes time, but it protects your live business from disruption.

A partner who catches these quirks early is protecting your go-live. A process that rushes past the sandbox stage without scrutinizing the converted data simply defers those problems to day one of live operations, when fixing them is far more stressful and disruptive.

Taking the time to test forms, verify reports, and clean up historical clutter turns go-live day from an anxious gamble into an orderly non-event.

Taking an Honest Look at Your Data

If you are currently running BusinessVision and planning your next move, you do not need to have all your data sorted out before you start talking to a partner.

The sandbox conversion exists specifically to show you where things stand. Running a trial conversion against a backup copy of your data gives you a clear, factual starting point. You will see what converts cleanly, what needs a quick adjustment, and what your team might want to clean up before cutover.

Before you set an arbitrary launch date on the calendar, take an honest look at your data first. If you want to see what your BusinessVision data looks like inside Spire and walk through a realistic transition plan, the door is always open.

Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.