Salesforce implementation guide: how to implement Salesforce CRM, step by step

What a Salesforce implementation includes

Salesforce gives you objects, fields, automation and reports. An implementation turns those parts into your system: how a lead comes in, who owns it, what happens next, and what a manager sees.

A full implementation covers nine phases. Some projects need all of them. A smaller project may skip some. The order stays the same.

1. Discovery and process mapping

Discovery answers one question: what should Salesforce do for this business? Skip it, and you end up with a CRM that copies the old spreadsheet.

• Walk one lead from first contact to closed deal. Note every person, tool and handoff.
• List every way leads come in: web forms, calls, chats, texts, referrals and imports.
• Write down the reports leadership needs, and the numbers behind them.
• List the systems Salesforce has to talk to, and which way the data moves.
• Confirm admin access to Salesforce and to each tool you plan to connect.

A diagram of your tools helps here. Our free tech stack diagram builder lets you sketch how data moves between your website, phones, CRM and other systems.

2. Design the system

Design turns the process map into a plan for the build. Each decision here is cheaper to change on paper than in Salesforce.

• Objects: which standard objects you use (Leads, Accounts, Contacts, Opportunities, Cases) and which custom objects you need.
• Fields: the fields on each object, their types, and which ones are required.
• Stages and statuses: lead statuses and opportunity stages that match your real process.
• Record types and page layouts, so each team sees the fields it needs.
• Automation: what Flow does on its own, and what stays a manual step.
• Access: profiles, roles and permission sets, so users see and edit the right records.
• Reports and dashboards for reps, managers and leadership.

Keep the design small. A field nobody fills in still shows on the layout and still has to be maintained. Add it later if the team asks for it.

3. Build in a sandbox

A sandbox is a copy of your Salesforce org. We build and test there, so your team can keep working in production while the new setup takes shape.

• Create the objects, fields, picklists, record types and page layouts from the design.
• Build the automation in Flow, plus validation rules and duplicate rules.
• Set up profiles, roles and permission sets.
• Build the reports and dashboards.
• Build a proof of concept for anything new or complex, and review it with your team before building the rest.
• Track every change, so the deployment to production includes all of it.

See what a Salesforce setup includes on our Salesforce CRM setup page, and what custom work looks like on Salesforce customizations.

4. Data migration

Your history is worth keeping, but only if it arrives clean and in the right place. Bad data in a new CRM costs trust on the first day.

Moving from another CRM? Our CRM migration services page covers how we move records, history and attachments into Salesforce.

5. Integrations

Salesforce does its best work when every lead and every touch lands on the record without anyone typing it in. That means connecting the tools your team already uses.

• Web forms and chat, with the landing page and source on every lead.
• Call tracking and phones, so calls log to the lead and missed calls create tasks.
• SMS, with opt-in and opt-out kept on the record.
• Google Ads, Microsoft Ads and Meta, so qualified leads and sales go back as offline conversions.
• Payments, billing and industry systems your team works in every day.

Use a native integration or an AppExchange app when one does the job. Build a custom integration through the API when it does not. Each one gets its own mapping document and its own test plan.

We have completed 900+ integrations. See the full list on our Salesforce integrations page.

6. Testing

Testing proves the system works the way your team works. Test with scenarios, not with single fields.

• Write a test plan: each scenario, the steps, the expected result and who checks it.
• Test each lead source end to end, from the form or call to the record in Salesforce.
• Test lead conversion, and check that every field maps from lead to contact, account and opportunity.
• Log in as each profile and check what that user can see and edit.
• Track each result in a QA sheet: pass, fail and the fix.
• Run user acceptance testing (UAT) with the people who will use the system, and get sign-off before go-live.

7. Training

A CRM the team does not use is an expensive address book. Training is where adoption starts.

• Train by role. A rep needs the daily workflow. A manager needs reports and dashboards. An admin needs to know what is safe to change.
• Train on the sandbox or on real records, with the team's own scenarios.
• Give each role a written guide and an SOP to keep.
• Record short walkthroughs for the tasks people do every day.
• Set up a process for new hires: user setup, permissions and training.

8. Go-live

Go-live is a plan, not a button. Write a checklist and walk through it in order.

• Deploy the tested changes from the sandbox to production.
• Assign users, profiles and permission sets.
• Run the final data import, and spot-check records against the old system.
• Switch each integration to production and send a test lead through every source.
• Turn on automation, alerts and scheduled reports.
• Set a freeze date for the old system, so new work happens only in Salesforce.

9. Support and improvement

After go-live, real use shows what the tests missed. Plan for it.

• Watch for Flow error emails and integration failures, and fix them as they come in.
• Collect requests from the team in one place, and sort them by impact.
• Set up a backup and recovery tool for your Salesforce data.
• Review the dashboards with managers, and adjust fields and reports to the questions they ask.
• Update the documentation and SOPs with every change.

Salesforce implementation deliverables to ask for

At the end of an implementation, you should own more than a working org. These deliverables let your team run it, and let anyone pick it up later.

• Process map: how leads and deals move through your business, and where Salesforce fits.
• Field mapping document: every field from forms, integrations and the old system, matched to its Salesforce field, with picklist values. We build these as a diagram plus a Google Sheet.
• Integration documentation: what each integration sends, when, and what to check when it fails.
• Automation list: each Flow, validation rule and duplicate rule, what it does and what triggers it.
• Test plan and QA results, with the UAT sign-off.
• SOPs for each role: how to work a lead, convert it, log a call and close a deal.
• Training guides and recorded walkthroughs.
• Admin notes: which fields are safe to edit and which feed formulas, automation or integrations.

Salesforce implementation best practices

• Name one owner on your side who makes decisions and signs off.
• Fix the process first. Salesforce makes a clear process faster. It makes an unclear one confusing.
• Start with what the business needs on day one, and phase the rest.
• Use standard objects and native features before custom objects and code.
• Build in a sandbox, test with real scenarios, and deploy in planned releases.
• Make the source of every lead a required, automated field from the start.
• Use duplicate rules and validation rules to keep data clean as it comes in.
• Write it down: mapping documents, SOPs and admin notes.

Common mistakes in a Salesforce implementation

• Copying the old spreadsheet or CRM field for field, instead of designing for the new process.
• Building straight in production, where a mistake hits live records.
• Migrating dirty data and planning to clean it later.
• Leaving lead source out, so reports cannot tie revenue to marketing.
• Adding custom code where a Flow or a native integration would do the job.
• Skipping user testing, then finding the gaps after go-live.
• One training session for everyone, and no written guide to come back to.
• No owner after go-live, so requests and errors pile up.

How to start your Salesforce implementation

Start with the process map and a list of every tool that touches a lead. That is enough to scope the project.

We are a Salesforce partner, and we price by project, not by the hour. Book a free call, walk us through how your team works, and you get a project quote to approve before any work starts.