How to keep lumberyard sales moving during an ERP migration

To keep lumberyard sales moving during an ERP migration, agree on what happens to every live quote and order, rehearse the work reps will do after the switch, and set a controlled process for requests received while systems are unavailable. Before normal selling resumes, sales, operations and finance should verify that the new records reflect the contractor commitments the yard has already made.

A successful file import does not answer the questions at the counter. Can the inside salesperson find the current framing quote? Can the outside rep tell which part of an order still needs to ship? Does the CRM point to the correct contractor account? Those are useful acceptance checks for the people responsible for customer relationships.

This guide covers the sales side of an ERP change. It is not a technical conversion manual, and it does not replace your ERP partner's plan for accounting, inventory, security or recovery. Use it to identify the customer work that must survive the transition and the people who can confirm it did.

Define what the sales team needs on opening day

Start with the jobs that customers will expect you to handle when the new system opens. Finding an account, revising a live estimate, checking an order and answering a delivery question are better starting points than a list of screens to learn. Have inside sales, outside sales and the affected branch managers describe the records and permissions each job requires.

Then distinguish the information being moved. Microsoft's data migration guidance separates configuration data from master records and open transactions. Its examples include customers, products, sales orders and open balances. That guidance is for Dynamics 365, but the distinction is useful when asking an LBM implementation partner what the agreed conversion includes.

Do not assume that importing customers also imports all their quote versions, attachments, conversations or transaction history. Ask the project owner where each will be available after the switch. Some information may remain in an approved read-only archive rather than the new ERP. Confirm access and retention requirements with the people responsible instead of letting reps keep private copies indefinitely.

Write down the agreed scope in plain language. For example, the team needs the current version of a live quote, its contractor and job address, its responsible rep, and a way to find the previous correspondence. These are requirements to verify, not a claim that every ERP moves those records in the same way.

Reconcile live work before moving it

Review the quotes and orders that will still matter after the change. Identify superseded estimates, canceled work and quotes that already became orders. A migration should not turn an old revision back into a live opportunity or make a partly fulfilled order look completely unshipped.

For a practical sales review, check the contractor identity, job address, serving branch, current document version, status and next customer action. Ask operations to verify the remaining quantities and delivery commitments on open orders. Have finance or credit confirm the handling of deposits, balances and restrictions; a sales review is not permission to change them.

Keep a link between old and new identifiers wherever the implementation team supports it. A contractor may call with an old quote number after the switch. The rep needs an approved way to locate its successor, not a guess based on the account name. Also check that similar company names have not been combined incorrectly.

The existing lumberyard quote follow-up guide explains how to maintain current job context in ordinary selling. During a migration, the additional task is to show that the same context can still be found after records have moved or changed identifiers.

Agree on the cutoff and the temporary way of working

Cutover is the point when the business stops using the old system and starts using the new one. Your implementation team should define when entry stops, when the final data is extracted, and how any later changes are captured. Reps need those rules before they receive a customer request during the transition.

Decide who can accept a quote revision, order request or delivery change while systems are unavailable. Use the dealer's approved temporary process with a named owner, a time received and a clear indication of whether the request has been entered into the new system. Restrict access to customer information and retire temporary records according to the agreed policy after reconciliation.

Do not quietly operate two competing order books. A request captured during downtime must be checked before it becomes a new transaction, especially if someone may already have entered it elsewhere. The migration lead should decide how staff confirm completion and avoid duplicates.

Tell affected contractors about practical service changes when needed. State which contact to use and what may take longer to confirm. Do not promise stock, credit approval, a price hold or a delivery slot based on an old screenshot. If a reliable answer is unavailable, name who will verify it and when the customer should expect an update.

Rehearse customer work, not just the data transfer

Microsoft's cutover guidance recommends rehearsing in a test environment with the planned data, tools, people and sequence. It also calls for named owners, verification steps and a rollback plan. These are planning principles to discuss with your ERP partner, not product-specific instructions for BisTrack, Spruce or another LBM system.

Include sales scenarios in that rehearsal. For example, an inside salesperson could find a contractor by an old quote reference, confirm the current revision, and follow the approved process to turn it into an order. The test should use the salesperson's intended permissions, not an administrator account that hides an access problem.

A second scenario could involve a contractor served by more than one branch with a partly shipped order. Can the next branch identify the relationship owner, see what remains to be supplied and find the person authorized to confirm the next delivery? The multi-branch account guide covers the ongoing ownership rules. The migration test checks whether those rules still work in the replacement system.

These scenarios are illustrative. Choose examples from your own operation, including a difficult exception rather than only a clean new sale. Record the expected result and what actually happened. When a step fails, identify whether the problem is data, configuration, access or training, then repeat the test after it is corrected.

Check the CRM after the ERP changes

An ERP conversion can change the identifiers, statuses or data feeds another application relies on. Ask whoever owns the connection to explain what must change and how they will verify it. Do not assume that a successful ERP launch means the CRM's quote list is current.

Compare a small, representative set of accounts and live jobs across the source system and the CRM. Check the contractor match, branch and rep assignment, quote status and last successful update. Include a revised quote and an order that should no longer appear as an open sales opportunity. Agree on how delayed or failed updates will be made visible to users.

SalesJack's CRM page describes bringing ERP and manufacturer quotes into one place and consolidating quotes by project. Those capabilities make the continuity check relevant; they do not establish that an ERP change needs no integration work. Confirm the transition plan for your actual connection before relying on CRM reminders or customer outreach based on migrated records.

The ERP–CRM integration guide explains why quote relationships and status mapping matter. Keep the migration review focused on whether those relationships survived this particular switch, rather than reopening a general CRM feature evaluation.

Make the go-live decision a business check

Sales should provide evidence to the project lead, alongside the checks owned by operations, finance and IT. Record unresolved customer-facing issues clearly. A cosmetic label problem and a quote showing the wrong contractor have different consequences and should not be treated as equivalent exceptions.

A concise sales readiness review should establish whether:

• Staff can find current quotes and open orders using the approved lookup process.
• Account identity, branch ownership and permissions work for the people who need them.
• Remaining order quantities and customer commitments match the agreed source records.
• Requests received during the transition have an owner and a reconciliation status.
• Connected sales tools show verified data, or users know which functions remain unavailable.

Have the authorized project owners decide which failures block opening, which have an acceptable temporary process, and who can approve a delay or recovery action. A rollback decision belongs in the coordinated implementation plan. Reps should not restart the old system on their own after new transactions have begun.

Review exceptions after the doors open

Keep a named support contact available when staff begin working with real customers. Log missing quotes, duplicate requests, incorrect account matches and stale CRM updates with their customer impact and responsible owner. Give reps a clear escalation route so they can get an answer without trying to repair unfamiliar records themselves.

Check unresolved items at an agreed daily review during the initial support period. Separate training questions from defects and data problems. A rep who cannot find the new lookup screen needs a different response from one whose customer's live order was omitted.

The useful finish line is that staff can carry out the customer work and explain any remaining exceptions. A contractor should not need to reconstruct the yard's records to get a quote revised or an order checked. Keep that practical test beside the technical migration milestones, and the sales team will have a clear basis for saying what is ready and what still needs attention.

Sources

• Microsoft Learn, data migration for Dynamics 365 implementation projects. Definitions of master records, configuration and open transactions.
• Microsoft Learn, transition with the cutover process. Rehearsals, task ownership, verification, approval and support. Applied here as general planning guidance, not LBM product instructions.