# CRM implementation plan: six phases and a checklist

https://krokul.com/en/blog/crm-implementation-checklist/ · Krokul Team · Updated 2026-11-19

Project managers and implementers who set up a CRM for a client need a plan that the client can sign phase by phase. This guide gives six phases with exit checks, an example timeline and one checklist to copy.

**Short answer.** A CRM implementation plan has six phases: discovery, design, data migration, integrations and documents, training with a pilot, and go-live with support. Each phase produces a named output and ends with an exit check that the client signs, so the project has a visible end and a date for the next phase.

## When do you need a CRM implementation plan

A CRM implementation plan is needed whenever a CRM goes live for a team that already works with clients, because every phase depends on decisions that the client has to make and sign. It is the project view of the method in the guide on [recurring revenue from CRM implementations](https://krokul.com/en/blog/topics/implementation-partners/).

- An integrator is about to quote a CRM project and needs phases that the client can approve one by one.
- An internal project owner has to move a sales team from spreadsheets to a CRM by a fixed date.
- A client keeps adding requests, and the project has no point where the scope is agreed.
- A company wants to know what to prepare before the first workshop.

- **CRM implementation plan** — A CRM implementation plan is the ordered list of project phases, each with an output, an owner and an exit check, that takes a CRM from the first workshop to daily use.
- **Exit check** — An exit check is the condition that the client signs to close a phase, for example the process map confirmed in writing or the record counts matching the source file.
- **Pilot** — A pilot is a period, usually one week, in which one team works in the new CRM with real data while the other teams wait.

## What are the six phases of a CRM implementation

The six phases of a CRM implementation run in a fixed order, because each phase uses the signed output of the one before it. The table gives the output, the exit check and the people for each phase.

Six implementation phases with an output and an exit check:

| Phase | Output | Exit check | Who works |
|---|---|---|---|
| 1. Discovery | Process map, list of pipelines, roles and documents | The client confirms the map in writing | Implementer with the client’s process owner |
| 2. Design | Stages, fields, access roles and automation rules on paper | Each rule has an owner | Implementer, approved by the client’s manager |
| 3. Data migration | Companies, contacts and deals loaded after a trial run | Record counts match the source file | Implementer, with source files from the client |
| 4. Integrations and documents | Email, payment services and print templates connected | One test invoice and one test email | Implementer |
| 5. Training and pilot | Team trained and one team working live | The pilot team enters data for one week | Implementer trains, the client team works |
| 6. Go-live and support | All users live and support agreed | The first monthly review is scheduled | Both sides |

## How to run a CRM implementation in six steps

A CRM implementation runs best as six steps that follow the phases above, each closed by its exit check before the next one starts.

### 1. Run discovery and write down the process

Interview the people who run the process every day and the person who ordered the project. List every pipeline, document type and report the team uses today, and ask the owner which three reports they open first.

The exit check is the process map, signed by the client.

### 2. Design stages, fields and roles on paper

Write each pipeline as a list of stages. Give every stage an exit condition, a time limit and the fields that must be filled before a deal moves on, and name an owner for each automation rule and each access role.

Keep the design to one page per pipeline, because a client signs what it can read in five minutes.

> **Tip.** Design one pipeline first and add the next one after go-live.

### 3. Migrate data after a trial run

Count the records in each source file, map every column to a field and run a trial import that writes nothing. Read the list of failing rows, fix the file, and only then run the live import, one kind of record at a time.

The full method is in the [CRM migration checklist](https://krokul.com/en/blog/crm-migration-checklist/).

### 4. Connect email, payments and documents

Connect the mailbox, the payment channel and the print templates, then test them with one real invoice and one real email. A wrong template shows up in your test, before any customer of the client sees it.

### 5. Train the team and run a pilot

Train each role in the client’s own pipeline with its own records, in sessions of about an hour. Then let one team work live for a week, collect every question in one list and close the list before the other teams join.

### 6. Go live and hand over to support

Move all users on a fixed day, keep the old tool readable for a week and schedule the first monthly review before the project team leaves. Agree who takes change requests and how many hours the first month includes.

The guide on pricing CRM implementation services shows how to price those hours.

## How long does a CRM implementation take

A CRM implementation for a mid-size client takes more calendar time than effort, because the client signs off between the phases and the pilot runs for a full week. The example below runs the phases one after another.

Example: effort and calendar time for a mid-size client (illustrative figures):

| Phase | Effort, hours | Weeks at 16 hours a week | Calendar weeks |
|---|---|---|---|
| 1. Discovery | 16 | 1.0 | 1 |
| 2. Design | 24 | 1.5 | 2 |
| 3. Data migration | 24 | 1.5 | 2 |
| 4. Integrations and documents | 20 | 1.25 | 2 |
| 5. Training and pilot | 12 | 0.75 | 2 |
| 6. Go-live and support | 8 | 0.5 | 1 |
| Total | 104 | 6.5 | 10 |

Formula: weeks of effort = hours ÷ hours per week the team gives to the project, and calendar weeks = weeks of effort + waiting for sign-offs and the pilot week. In the example 104 hours at 16 hours a week is 6.5 weeks of effort, and the plan takes 10 calendar weeks. Tell the client the calendar number, because the client’s sign-offs decide it.

## Which mistakes break a CRM implementation plan

- Starting design before discovery is signed. The first change request then reopens every rule, so get the process map signed first.
- Migrating data in the last week. Untidy source files push go-live back, so run the trial import in phase 3 while the design is still open.
- Training on sample screens. The team forgets them by Monday, so train on the client’s own pipeline and records.
- Skipping the pilot. Every team finds the same gap in its first week, so let one team find it and fix it for the others.
- Ending the project without a support agreement. The client’s questions arrive anyway, so agree hours and a price before go-live.

## The CRM implementation checklist to copy

Copy this list into the project plan and tick each line with a name and a date.

- The person who owns the process on the client side is named.
- The process map with pipelines, documents and reports is signed.
- Each pipeline has stages, exit conditions and time limits on one page.
- The required fields of each stage are agreed.
- Every automation rule and access role has an owner.
- The source files are counted and the totals are written down.
- The trial import is done and every failing row has a reason.
- The counts after the live import match the source files.
- Email, the payment channel and print templates pass one real test.
- Training sessions are held for each role in the client’s own pipeline.
- The pilot team works live for a full week and its questions are closed.
- The go-live day is fixed and the old tool stays readable for a week.
- Support hours, the price and the first monthly review are agreed in writing.
- Every phase has a signed exit check with a date.

## How the plan works in Krokul

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. The setup phases above map to actions that an administrator takes in the product.

For the design phase, the form that creates a company asks one question about the type of business (integrator, vendor or goods business) and lists the stages of the pipeline each type creates. The chosen template adds the pipeline with its stages, sources of inquiries, loss reasons and message templates. It only adds records and leaves existing ones unchanged, so applying it again creates no duplicates. In the pipeline settings the stages can then be reordered, and each stage has a probability, a time limit in days and its own required fields.

![Pipeline settings with stages, probability, time limit in days and required fields on the Proposal sent stage](https://krokul.com/img/en/blog/implementation-plan-pipeline-stages.webp)

An administrator also gets a launch checklist that Krokul computes from live counts. For a B2B company it has six steps: a pipeline created, 10 or more contacts loaded, the first deal created, a price list set up, a channel connected and a colleague invited. A step reopens when its data is deleted, so the list always matches the data.

For the migration phase, the Migration screen is available to administrators. It takes a file in CSV, TSV or XLSX format or a Google Sheet by link, and one file holds one kind of record. The dry run is a separate run with the same mapping. It writes nothing, reports how many records would be created, updated and skipped, and says how many rows would be skipped and why. The dry run does not run the full record validation, so the live import can still reject some rows. The Rollback button after a live run removes the records that run created. The page on [what Krokul migrates and what it leaves behind](https://krokul.com/en/solutions/migration/) lists the sources.

![Migration screen, Source step: file in CSV, TSV or XLSX, the kind of record in the file and a Google Sheet by link](https://krokul.com/img/en/blog/implementation-plan-migration-source.webp)

On the Margin plan an administrator can also create a test company, a separate company for trying the setup, an import and automations without risk to the working one. Data does not move between the two, so the final setup is repeated in the working company.

Two paths start a project. A new company with simple accounting creates a free workspace, answers the question about the type of business and sets up on its own. A company with years of data, several pipelines or an accounting exchange orders the setup, the team training and the data transfer from an implementation partner. After go-live, Krokul shows the [hours of a project against the client’s support package](https://krokul.com/en/for/integrators/) in the project.

## Frequently asked questions

### How long does a CRM implementation take?

For a mid-size client the example plan takes about ten calendar weeks for 104 hours of effort, because sign-offs and the pilot week sit between the phases. Your own number depends on how fast the client signs and how tidy the source data is.

### Who should own the project on the client side?

One person who runs the process every day and can approve changes. Two owners slow every sign-off, because each phase waits for both answers.

### Can the phases overlap?

Yes, in two places. Integrations can start while the trial import is being fixed, and training materials can be prepared during the pilot. Design and migration should stay in order, because the mapping depends on the signed design.

### What is the difference between a pilot and go-live?

A pilot is one team working live for a week with real data while the other teams wait. Go-live is the day all users move, after the questions from the pilot are closed.

### When should a company hire an implementation partner?

When it has years of data, several pipelines or an accounting exchange, because mapping fields and configuring stage rules takes judgement. A new company with simple accounting can start on its own.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
