CUSTOMER RELATIONSHIP MANAGEMENT · A PRACTICAL START CRM stands for Customer Relationship Management. It is the practice of managing relationships with current and potential customers; CRM software helps organize the records and work behind those relationships. A useful sales record tells you who the company is, what actually happened, which buying discussion is open and what you should do next. Buying software alone does not create that discipline. 10 October 2026 · Manual transition check Replay the events without overwriting the history. **Entirely fictional example:** Ayşe sells quotation-form implementation services. Duru Packaging and Elif are invented. On 2 October 2026, Elif asks for a quotation for a defined form project. The seller’s spreadsheet later contains one compressed note: “Elif — quote sent — call 12 Oct — review moved.” Budget and final purchase authority are unconfirmed. No sale or Anivo result is represented. Keep the dated events and their consequences Event | History to retain | Current work after the event 5 October: Ayşe sends the requested quotation. | Record the quotation version and date. Elif agrees to a check-in on 12 October. | Opportunity: quotation under review. Task: Ayşe checks on 12 October. A sent quotation is not an accepted order. 10 October: Elif says the internal review moved to 26 October and agrees to a check-in on 27 October. | Append the new statement and date. Retain the 5 October event and earlier agreement. | Opportunity: review postponed. Mark the 12 October task superseded, with the reason; create the 27 October task. Do not leave both as current follow-ups. The later statement changes current work, not the facts known on 5 October. An agreed check-in is not a promised decision or confirmed budget. Completed manual record as of 10 October 2026 Field | Recorded value Company and contact | C-014 / Duru Packaging / Elif, commercial contact. All fictional. Opportunity | Quotation-form implementation; buyer requested a quotation on 2 October. Current state: review postponed. History | 5 October: requested quotation sent; 12 October check-in agreed. 10 October: review moved to 26 October; 27 October check-in agreed. Previous task | 12 October check-in superseded on 10 October because the buyer moved the review. Keep the change trace. Current task and owner | Ayşe: check the review outcome with Elif on 27 October, using the existing conversation. Still unknown | Approved budget, final purchase authority, acceptance of the quotation and eventual outcome. If the only evidence had been a relevant website and an unanswered first email, record a researched prospect and an outreach activity. Do not turn that into a confirmed project. The [lead qualification guide](https://anivoapp.com/guides/lead-qualification) helps distinguish fit from a buying decision. Choose by the work that breaks, not a magic contact count. Excel or another spreadsheet can be sufficient when one person keeps a clear history, a reliable next-action list and recoverable records. Separate sheets or rows can hold companies, interactions and tasks. A calendar can support reminders. The issue is whether the routine works, rather than whether the file is called CRM. A practical decision before you buy software Observed situation | Reasonable next step | What to verify One person can recover the last agreement and current task without conflicting copies. | Keep the spreadsheet routine while it meets the job. | Try the worked example. Preserve dated history and a clear next action. One person repeatedly loses context between research, notes and follow-ups. | Test an individual CRM workflow on a small, representative set. | Can you find the history, update the current state and replace a task without losing the earlier event? Several people need simultaneous updates, permissions, assignments or approvals. | Evaluate a system that explicitly supports those shared requirements. | Test the actual roles, concurrent edits and access conditions. A one-user workspace does not meet this requirement. The main problem is invoices, stock, orders or accounting. | Evaluate the relevant operational or accounting workflow. | CRM relationship records alone do not establish these capabilities. Check the specific scope and connections. Nobody records the conversation or owns the next step. | Define the recording routine and responsibility first. | Software will still need accurate input and someone who acts on it. This is an editorial decision aid, not a measured productivity threshold or a ranking of software vendors. Two counterexamples A fictional seller with 300 names and infrequent, simple interactions may manage a consistent spreadsheet. Another with eight accounts, several contacts and changing proposals may need better relationship records immediately. Those numbers illustrate different work; they are not recommended cutoffs. BLANK DECISION RECORD Reviewer and review date: [ ] Relationship and work to track; specific failure in the current routine: [ ] Single-user / shared-user requirement and the capability inspected: [ ] Retained source copy, version and date: [ ] Test scope: companies, contacts, historical events, opportunities and tasks: [ ] Decision: keep spreadsheet / test individual CRM / evaluate shared system / evaluate another operational tool / repair recording routine first: [ ] Reason for this decision; unresolved question and next check: [ ] BLANK TRANSITION CHECK · REPEAT FOR EACH TEST RECORD Source record ID, original field and value: [ ] Target record/field and its meaning; company-contact relationship: [ ] Event date, source and historical information retained unchanged: [ ] Current opportunity state and the information supporting it: [ ] Previous task; why and when it changed; retained change trace: [ ] Current task, responsible person and agreed date: [ ] Unsupported data in the target system and required manual work: [ ] Values, relationships and dates visible after reopening the record: [ ] History, relationships and tasks actually present in export/backup: [ ] Retrieval or recovery test result and missing data: [ ] Accept / repair / stop decision and reason: [ ] This file contains a fictional teaching example, decision table and blank manual checks. It is not a CRM import format, automatic migration, readiness score or certification. State unknown or omitted data explicitly. Matching row counts do not prove that history and tasks were fully retained. Logical record distinctions do not mean every CRM has separate objects or that Anivo automatically migrates the sample. Shared-user requirements must be tested in a system that explicitly supports them. Sources and reading scope Checked on 10 October 2026. Relevant public guide sections were read; the academic paper was accessible only as an abstract. Vendor capabilities remain specific to those products. Microsoft: What is CRM? https://www.microsoft.com/en-us/dynamics-365/resources/what-is-crm Public definition and capability sections inspected. No visible publication date. Broad enterprise capabilities are not attributed to every CRM or to Anivo. HubSpot: Manage your CRM database https://knowledge.hubspot.com/get-started/manage-your-crm-database Updated 18 September 2026. Public sections on objects, records, associations and activities inspected; describes HubSpot’s own model. Salesforce Trailhead: explore CRM work https://trailhead.salesforce.com/content/learn/modules/lex_implementation_basics/lex_implementation_basics_explore Public worked account/contact/opportunity exercise inspected. No visible publication date; a vendor training example, not comparative research. Payne and Frow (2005): A Strategic Framework for Customer Relationship Management https://doi.org/10.1509/jmkg.2005.69.4.167 Journal of Marketing 69(4), 167–176, October 2005. Publisher abstract only; conceptual framework, not a measured transition threshold or Anivo outcome. Paraşüt: CRM and operational software scope https://www.parasut.com/blog/crm-nedir-ne-ise-yarar Turkish guide dated 25 August 2026. Relevant CRM, accounting and commercial-operation distinctions inspected; product-specific integration claims are not transferred to Anivo.