What to prepare before moving your window business to new software

Moving to new software is easier when you first decide what the business needs to carry forward. That does not mean tidying every file the company has ever created. It means knowing which information is active, who owns it and what the team needs to do its next job.

A folder full of old spreadsheets is not a migration plan. Neither is a promise that everything will be imported exactly as it is. Start with a manageable scope and confirm what the receiving system can actually accept.

This guide is a preparation exercise. Available import formats, transfer support and fees must be confirmed with the provider; they should not be assumed from a general article.

Map how one job moves through the business Choose a representative job and follow it from enquiry to completion. Where are the customer details recorded? Who prepares the quotation? Where do survey photographs go? How does the workshop receive the final instruction?

Write down the handovers, not just the software names. Two people may use the same spreadsheet but depend on different columns or a conversation that happens alongside it.

Identify the problems you want the move to solve. “A clear current specification” is a useful goal. “Put everything into a new system” is too broad to guide a practical setup decision.

Separate live work from historical records List current enquiries, accepted jobs, work in production and upcoming installations. Decide what the team must be able to act on after the move. Historical records may need to remain accessible without being recreated as active jobs.

Keep the original records and agree how they will be retained. Do not delete the old system simply because a few sample imports look right. Access, retention and disposal should be reviewed against your business needs and applicable obligations.

If a job spans the changeover, define which system is the working record. Splitting updates across both systems without a clear rule can create more confusion than the move was supposed to remove.

Give each data set an owner Customer details, product information, price lists and active job records often need different people to check them. Name an owner for each rather than expecting one administrator to recognise every technical or commercial error.

Ask owners to identify duplicates, obsolete entries and fields that need explanation. A column called “type” may make perfect sense to the person who built it and mean nothing to anyone receiving the file.

Do not silently correct uncertain information. Mark it for review so the right person can decide. Moving a questionable figure into a new system does not make it reliable.

Agree the commercial foundations Check the product and supplier information the business intends to use, the current pricing basis and who is allowed to maintain it. Confirm whether additional setup or provider work is needed rather than assuming a file can be dropped straight in.

Decide how quotations should be presented and which business details belong on customer documents. Gather approved branding and contact information in a small, clearly named folder.

Review access by role. The person taking a site measurement does not necessarily need the same commercial information as the owner. Confirm the actual permissions the platform supports before promising a particular arrangement to the team.

Test a representative job, not just a login A successful login proves very little about the working setup. Try the tasks that matter: finding a customer, preparing a quotation, recording a survey and passing a clear instruction to the next person.

Use approved demo or anonymised information while testing. Compare the result with the source records and check exported or customer-facing documents, not just the screen.

Record questions as you go and send them to the right support route. Free help pages and platform walkthroughs can support learning, but the scope of any assisted migration or other service needs to be agreed separately.

Choose a controlled changeover Pick a sensible point to start using the new process for defined work. Explain what happens to existing jobs and who answers questions during the changeover. Avoid switching everything at once simply because the account is ready.

Prepare this small pack first - The job workflow and the main problems to solve. - An agreed list of live records and historical records. - A named reviewer for each important data set. - Current product, supplier, pricing and branding information. - A representative test job and a short acceptance checklist. - A clear rule for where new work and updates will be recorded.

A useful software move is not measured by how much old data you copy. It is measured by whether the team can carry out the next real job with confidence.