
01
The short answer
In a small business, start with one specific process, such as tracking an inbound enquiry through to a sale. Define who will use Salesforce, what data is needed, and how you will know whether the project is working. Configure a minimal scope, import a small sample, have the team test it, and make corrections before adding automations or new services.
02
What problem should Salesforce solve first?
Before discussing screens or modules, describe what happens today. Do enquiries arrive in several email inboxes? Are follow-ups missed when someone is away? Does the manager have to ask everyone where their sales stand? A useful implementation starts with an observable pain point, not the general idea that you should “manage customer relationships better.”
Salesforce generally organizes sales tracking around accounts, contacts, leads, and opportunities. An account represents an organization, a contact is a person associated with that organization, and an opportunity is a transaction in progress. A lead is a person or organization to qualify; converting it can create an account, a contact, and an opportunity. These concepts help clarify the process, but they do not mean you have to import every historical detail on day one.
03
How should you scope an initial deployment?
Map the journey the team actually follows, from the first contact to a decision. Note the stages, the people responsible, the information used, and the exceptions that come up regularly. Do not automatically reproduce every current habit: some steps exist because the old tool required them, not because they help you sell.
The scope also needs to fit your Salesforce edition, licences, and existing tools. Check which features are actually included in your environment before designing the process around a particular capability. If an integration, access permission, or automation is essential, confirm that it is available and check its conditions instead of assuming. This check helps avoid building a solution around a feature the team cannot access.
04
Which features should you configure first?
- Useful configuration
- Configure only what makes the process clear and usable.
- Objects and sales stages
- For the initial scope, it may be enough to have the accounts, contacts, leads, and opportunities you need, with sales stages the team can understand.
- Fields, views, and a report
- Then add the essential fields, the team's work views, and a report to track the planned activity.
- Optional fields
- A screen filled with optional fields does not make a CRM more useful; it can slow data entry and reduce data quality.
Do not automate a process that is still disputed or poorly understood. Automation can apply a rule consistently, but it cannot decide for you whether the rule makes sense. First, run the process manually in Salesforce. Once the team knows what to do and the exceptional cases are understood, automate one repetitive task at a time.
05
How should you prepare and test the data?
Importing data is often where inconsistencies in old records become visible. Before transferring files, identify the sources, look for duplicates, and decide what information needs to be kept. A small business does not necessarily need to move its entire history to get started: active records and information useful for follow-up may be enough, depending on the business's needs and retention obligations.
Salesforce's import wizard supports certain standard objects, including accounts, contacts, and leads. You also need to review field mappings: a field that is not mapped will not be imported. So do not treat an import as a simple file copy. Keep a copy of the source, record your mapping choices, and check the results with people who know the records.
06
How should you manage access and privacy in Canada?
A CRM often centralizes personal information: names, contact details, correspondence, or details related to a sale. To determine what information is necessary, who should have access, how long it should be kept, and how to respond to requests or incidents in your situation, consult the official sources and have a lawyer review your obligations. Set permissions according to actual job responsibilities rather than giving everyone administrative access.
The Office of the Privacy Commissioner of Canada outlines the principles of PIPEDA and notes, among other things, that the federal law applies to covered commercial activities, including certain interprovincial or international transactions. Quebec also has its Act respecting the protection of personal information in the private sector. Official sources describe general obligations, but they do not replace a legal analysis of your specific situation. For the project, document decisions about collection, access, retention, and incident management.
07
When should you launch the pilot, and what comes next?
- Group and way of working
- A pilot is more than opening user accounts. It should give a small group a practical way to work in Salesforce, with sufficiently representative data, brief instructions, and someone to report problems to.
- Training on real tasks
- Train the team on its actual tasks: creating a lead, qualifying an enquiry, opening an opportunity, recording an interaction, and planning the next action.
- Learning resources
- Salesforce guides can support learning, but they do not replace the rules specific to your process.
After the pilot, improve in small steps: one integration, automation, or additional team at a time. Compare the cost of customization, licences, integrations, and maintenance with the expected benefit. If your process requires many workarounds, it may be worth comparing two paths: keep Salesforce and add automation or AI, or have a custom application assessed. Language models can lower the cost of some development, but they do not automatically make every custom application cheaper. The comparison should account for your needs, security, long-term support, and recurring costs.
Sources
The pages the facts in this guide come from. Each link was checked when the guide was written.
- Salesforce TrailheadSalesforce CRM Basics
- Salesforce HelpImport Data with the Data Import Wizard
- Salesforce HelpStart an Automation When a Record Is Created or Changed
- Salesforce HelpPermissions and Access Settings
- Commissariat à la protection de la vie privée du CanadaQuestions and Answers regarding the application of PIPEDA, Alberta and British Columbia’s Personal Information Protection Acts
- Éditeur officiel du QuébecLoi sur la protection des renseignements personnels dans le secteur privé
