# CRM Implementation Checklist for Small Businesses > Use a practical checklist for goals, data, stages, permissions, workflows, testing, training, ownership and review before CRM go-live. A CRM implementation is a controlled change to customer-facing work. This checklist helps a small business prepare the operating model, configuration, tests and handover without assuming that setup is included in the subscription. ## Eight questions before go-live 121 implementation methodology. Exact delivery, timing and support require a separate agreed scope. ## Capabilities explained ### Users, roles and permissions Controls whether a user acts at agency or sub-account level and which supported areas they can access. **How it works:** Controls agency or sub-account configuration that determines access, packaging, governance or billing. **Why a business would use it:** Limits day-to-day access to the work a person actually needs to perform. **Limitations:** Availability and control depth depend on agency plan, role and current account configuration. **Human responsibility:** An authorised administrator must review, approve and audit material changes. ### Import and export Moves supported records through structured files, with mapping and validation needed before relying on the result. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Supports controlled migration and operational extracts when the data is prepared and reconciled. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Testing and execution logs Supports test runs and operational evidence used to diagnose why a record did or did not follow a path. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Gives a human a way to verify automation and investigate exceptions. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ### Connected app management Shows and manages authorised app connections and their account-level installation state. **How it works:** Exchanges supported data or events through an authorised connection, scope or documented interface. **Why a business would use it:** Provides a review point for removing access that is no longer needed. **Limitations:** External availability, rate limits, schema changes, permissions and data-controller duties still apply. **Human responsibility:** An owner must approve access, monitor failures and remove connections that are no longer needed. ## Define the work the CRM is meant to improve. Start with a customer journey and an operating problem, not a list of screens to configure. ### Problem and boundary Describe what is difficult today, which journey is in scope and which specialist systems or decisions remain outside. ### Executive and operating owners Name who approves scope and risk, and who maintains users, fields, stages, workflows and messages day to day. ### Acceptance measures Write observable checks such as ownership, correct routing and representative journey completion; avoid unsupported revenue promises. ## Prepare only the information the configured journey needs. Data quality and permissions shape whether the CRM can be trusted in everyday use. ### Source inventory List spreadsheets, systems, inboxes and forms with owners, formats, quality and sensitivity. ### Field definitions Name purpose, format, required status, source and owner for each important field. ### Roles and permissions Test who can view, create, edit, export and administer relevant records and settings. ## Configure the ordinary path and the exceptions together. A happy-path demonstration is not enough for a production workflow. ### Stages and ownership Define entry, movement, exit, owner and next-action rules for the main journey. ### Messages and automation Approve sender, wording, consent, timing, stop conditions, failure and human escalation for every automated step. ### Integrations Record connection type, account owner, data direction, matching, limits, costs, monitoring and removal. ## Prove that people can operate the system after configuration ends. Go-live should be an accepted operating decision, not the date a builder stops making changes. ### Representative testing Include new, duplicate, incomplete, sensitive, opt-out, failed connection and changed appointment cases. ### Training by role Show each user the records, decisions and exceptions they own, using the agreed real-world journey. ### Acceptance and review The customer records known limitations, approves go-live, names support routes and schedules the first operating review. ## Frequently asked questions ### Who should own a CRM implementation? Use both an accountable sponsor and an operating owner. Technical configuration alone cannot decide customer process, access, wording or acceptance. ### Should we configure every feature before launch? No. Launch the smallest complete, tested journey that solves the priority problem, then add capability through controlled changes. ### What should user acceptance testing include? Test ordinary work plus duplicates, missing data, opt-outs, sensitive replies, failed integrations, rescheduling, permissions and recovery from mistakes. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/onboarding-support](https://121.direct/crm/onboarding-support) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.