Plan Coaching During a Salesforce Migration

Salesforce migration work changes more than screens and field labels. Sellers learn where account history appears, which stages call for evidence, and where meeting notes belong. Managers face another issue. Their forecast review still calls for a clear deal story, even when familiar habits no longer fit the new record. An enablement account executive should start with live decisions inside those reviews. A broad adoption promise adds work yet leaves a manager unsure what to ask on Friday.

Request two calendars before planning practice. One calendar shows access dates, manager training, pilot work, old system retirement, and reporting changes. The other shows forecast reviews, pipeline meetings, deal clinics, and one on ones. Put both calendars beside each other. Mark every point where a manager asks a seller to explain a deal from an unfamiliar record. Each marked moment offers a useful practice slot. This approach keeps preparation close to work sellers already face.

In a fictional situation, Priya meets Marcos, a revenue enablement director, on Tuesday. New record access starts Monday. Manager training occurs Wednesday. The first forecast review occurs Friday. Priya asks, “Which decision feels least secure during Friday’s review?” Marcos replies, “Managers need stage evidence, yet sellers will spend time finding history and fields.” Priya asks which evidence a seller needs to say aloud. Marcos names a next meeting date, a named buyer, and a reason for movement. Priya writes those exact terms in her notes.

Her next questions separate record design from meeting ownership. Priya asks who confirms the location of each new field. Marcos names the CRM administrator. Priya asks who leads Friday’s review. Marcos names a sales director. Priya schedules a short conversation with both people. The administrator identifies the correct record areas. The director describes questions managers already use when a deal stalls. Priya now has accurate system language and a familiar coaching exchange. No large program needs approval before one focused session.

Do not treat every pause as seller resistance. A seller might lack access, a new habit, a clear stage definition, or time to prepare. Each source needs a separate response. Missing history belongs with the migration group. Changed stage terms need approved language in a short prompt. Different manager views of acceptable evidence need a sales leader’s working definition. A practice session should expose a system problem rather than hide one beneath a performance label.

Build one exercise around an existing meeting rhythm. Use a fictional opportunity in the new view. Give a seller thirty seconds to state current stage, buyer contact, next meeting, and reason for confidence. Then ask one follow up question. Ask the seller to point to the record area holding support for each answer. Keep names, notes, and deal details fictional. The exercise tests a conversation and a record path. A full tour of every field would bury both purposes.

Question wording matters. “Tell me more” invites a broad response. A manager needs a prompt tied to a decision. Priya offers a fictional question: “What happened since our last review, who attended, and which scheduled customer conversation moves this opportunity forward?” The sales director replaces “event” with “scheduled customer conversation” because managers already use those words. The administrator confirms where date and attendee notes belong. Priya places the agreed wording in a shared draft for both reviewers.

Fit practice inside a current meeting. Ten minutes often suits a migration week better than a separate hour. Reserve two minutes for reading the fictional record. Use three minutes for the seller explanation, three for manager questions, and two for comparing spoken evidence with visible fields. Timing reveals friction. When everyone spends four minutes searching for a field, write down the record area and send the observation to the migration owner. Do not stretch the exercise to fill an agenda.

Prepare managers before the review. Send a note with the fictional record, the exact question, and the reason for practice. Priya’s fictional note says, “During forecast review, ask sellers for evidence behind stage movement. Use the new record for meeting date and buyer contact. Send workflow issues to the migration contact after review.” Managers still decide how to coach. Migration owners still answer system questions. The note lets each group enter the meeting with a clear task.

Listen closely when sellers get stuck. “I need more time in Salesforce” often covers several issues. Ask which detail the seller expected and where the search started. A seller might report buyer role under contacts rather than opportunity details. Another seller might report absent historical notes. Group observations by navigation, missing information, changed terms, or unclear manager expectation. Give each entry a meeting date, record area, owner, and next check point. Do not ask a manager to solve a data transfer issue before the full team.

In Friday’s fictional review, Marcos names one purpose: stronger evidence during stage discussion. A manager asks Jordan, a fictional seller, Priya’s agreed question. Jordan describes a customer meeting yet has no next date in the record. The manager asks Jordan to locate the date field. Jordan finds a separate activity area after forty seconds. Priya writes down the delay and the route Jordan used. She does not offer a personal workaround. After the meeting, the administrator reviews whether forecast users should open another view.

Hold a short review after each early session. Ask which question produced useful evidence, which field delayed discussion, and which answer affected a forecast decision. Ask sellers which record area felt unclear. Keep answers tied to observed moments. When someone says, “The new process feels confusing,” request a recent meeting, record area, and expected detail. This turns a broad complaint into an item ready for owner review.

A temporary workaround needs an end owner. Suppose a fictional leader asks managers to collect a missing detail outside Salesforce for two weeks. Record who decides when the step ends and when they will check readiness. Otherwise, a spreadsheet request might survive after a field becomes available. Priya asks, “Who closes this routine, and what observation shows the new path works?” A leader or migration owner answers. The practice facilitator records the answer and date.

Plan another exercise only when the first session shows a separate need. The next practice might cover a missing buyer role, an explanation of a changed stage, or a handoff between seller and manager. Keep one behavior at the center. Reusing the same meeting slot gives leaders a clear sequence of observations instead of one crowded activity. Managers also hear consistent language across reviews.

For a practice session, draw two columns on a page. Label one migration calendar and one manager calendar. In a fictional account, enter Monday access, Wednesday manager training, and Friday forecast review. Beside Friday, write one manager question and one record detail supporting an answer. Read both lines with a colleague. Then bring the page to the CRM administrator and sales director, ask each person to confirm the field and question, and place the approved prompt in Friday’s meeting agenda.