These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- CRM
- Data model
The tables behind CRM
CRM ships with 69 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 69
- Features
- 8
- Change it
- Add fields and tables in Proto
How the model is organised
Customers and access
Accounts, Contacts, Users and Territories establish customer identity and team responsibility. Activities and Cases retain follow-up and scoped sales escalations. Entities, Currencies, exchange rates and CRM policies supply the operating boundaries.
Lead intake
Leads and lead scores retain captured interest and its source signals. Routing rules and routing assignments explain how eligible owners receive work. Communication preferences preserve the recipient’s current restrictions across capture, conversion and merges.
Campaigns
Campaigns, campaign members, Segments and Emails describe the audience and proposed outreach. Message deliveries records actual dispatch outcomes; campaign attributions record the disclosed source and weighting used for commercial measurement.
Pipeline
Opportunities, opportunity products and opportunity contacts retain the deal and buying committee. Opportunity history preserves changes. Forecast periods, forecast entries, forecast items and pipeline summaries retain identified reporting populations, while Quotas holds effective earner and period allocations.
Offers
Products, price books and price book entries supply the commercial basis. CPQ rules and Configurations preserve the technical evaluation. Quotes and quote items retain offered quantities, net prices and discounts. Document versions and approval decisions bind each required decision to the actual version and signer.
Agreements
Contracts and contract items preserve accepted terms and line scope. Signature requests record the required customer acceptance. Contract cycles identify each eligible charge period, Renewals links term decisions, and commercial allocations control cumulative order and billing scope.
Delivery and receivables
Orders and order items retain accepted fulfilment work. Fulfilment events and usage records supply delivery and measured-usage evidence. Invoices, invoice items and tax assessments establish issued charges. Payments received, payment applications, credit adjustments, credit applications and Refunds retain cash, settlement and correction history. Dunning actions track eligible collection follow-up.
Sales compensation
Commission plans, commission credits and Commissions retain the earning basis, allocated share and calculation. Commission statements freezes membership; commission adjustments preserve attributable corrections; commission payouts record independently authorized requests and confirmed settlement.
Governance and connections
Master changes retains proposed sensitive edits and approval evidence. Integration events and outbound deliveries distinguish authenticated incoming events from destination-specific requests and outcomes. Migration batches and migration items retain source identities, cutoff, mappings and reconciled historical positions.
Every table, by feature
- Lead management4
- Accounts & relationships10
- Pipeline & forecasts7
- Products & quotes13
- Contracts & renewals5
- Orders & receivables15
- Campaigns & outreach6
- Commissions & sales operations11
- Leads
Unqualified inbound prospects.
Linked to Campaigns, Users, Accounts, Opportunities - Lead scores
Scoring signals contributing to a lead’s composite score.
Linked to Leads, CRM policies - Routing rules
Versioned ordered assignment rules and atomic round-robin cursor.
Linked to Entities, Territories, Campaigns, Users - Routing assignments
Auditable routing/reassignment result retains former ownership and matched input evidence.
Linked to Leads, Routing rules, Users
- Accounts
Companies or households being sold to. The customer-360 anchor.
Linked to Territories, Users, Accounts (self), Entities - Contacts
Individual people at an account.
Linked to Accounts, Entities - Opportunity contacts
Buying-committee members on an opportunity.
Linked to Contacts, Opportunities - Activities
Calls, meetings, and tasks against leads / contacts / opportunities.
Linked to Users - Cases
Optional in-CRM cases when Customer Support is not a separate app. Used for service escalations touching sales conversations.
Linked to Accounts, Contacts, Users, Entities - Master changes
Independent effective changes, merges and realignments retain old/new identifiers and surviving history.
Linked to Entities, Document versions, Approval decisions - Communication preferences
Canonical recipient/channel/purpose preferences and most-restrictive suppression survive duplicate records and merges.
Linked to Entities - Entities
Legal/selling entities with explicit currency, operating policy and accounting handoff ownership.
Linked to Currencies, CRM policies - Users
CRM users — reps, managers, admins, marketers.
Linked to Territories, Commission plans, Entities, Currencies - Territories
Named-account or geo territories.
Linked to Users, Entities
- Opportunities
Qualified deals in the pipeline.
Linked to Accounts, Users, Contacts, Entities - Opportunity products
Products on an opportunity.
Linked to Products, Opportunities - Forecast periods
Periods for which forecasts are submitted.
Linked to Entities, Currencies, Document versions, Users - Forecast entries
Versioned rep submissions and explicitly identified manager rollups per period/category, each with immutable source membership.
Linked to Forecast periods, Users, Currencies, Document versions - Opportunity history
Immutable actual stage, owner, amount, currency and close transitions preserve funnel/forecast cohorts.
Linked to Opportunities, Users, Currencies - Forecast items
Immutable opportunity-level membership under a specific rep or manager forecast submission.
Linked to Forecast entries, Opportunities, Opportunity history, Currencies - Pipeline summaries
Reproducible grouped pipeline snapshot supplies the two aggregate screens with real summary columns.
Linked to Entities, Accounts, Users, Currencies
- Products
Sellable products and services.
- Price books
Named price lists (Standard, Partner, Enterprise, Regional).
Linked to Entities, Currencies - Price book entries
Product price in a specific price book.
Linked to Products, Price books, Document versions - Quotes
Customer-facing priced proposals.
Linked to Opportunities, Price books, Users, Entities - Quote items
Products and prices on a quote.
Linked to Products, Quotes, Price book entries, Configurations - CPQ rules
Effective technical compatibility and configuration rules separate from commercial discount authority.
Linked to Entities, Products, Document versions, Users - Configurations
Chosen product/option combination and frozen rule results bound to exact quote version.
Linked to Quotes, Approval decisions, Document versions - Document versions
Immutable exact offer, terms, plan, message, forecast or statement content and authority population.
Linked to Entities, Users, CRM policies - Approval decisions
Scoped exact-version decision with actual actor, limit and conflict evidence.
Linked to Document versions, Users, Currencies - CRM policies
Independent approved version of commercial, commission, communication, receivable and workflow rules.
Linked to Entities, Users - Currencies
Approved ISO currencies and exact rounding scale.
- Exchange rates
Versioned directional rate evidence frozen on conversions and snapshots.
Linked to Currencies - Tax assessments
Configured tax authority, supply facts and exact assessed amount for proposal or invoice version.
Linked to Document versions, Currencies, Users, Integration events
- Contracts
Signed agreements with customers.
Linked to Accounts, Opportunities (source deal), Quotes, Contacts - Contract items
Accepted line commitment preserves net price, cadence, term and recurring versus one-time/usage basis.
Linked to Contracts, Quote items, Products, Document versions - Contract cycles
One accepted billing/delivery occurrence per line/period; recurrence cannot generate duplicate orders or invoices.
Linked to Contract items, Usage records - Renewals
Upcoming contract renewals tracked as a pipeline.
Linked to Contracts, Accounts, Users, Opportunities - Signature requests
All required signatures or reviewed equivalent acceptance on the exact current contract version.
Linked to Contracts, Document versions, Integration events, Users
- Orders
Fulfilment orders generated from closed-won contracts.
Linked to Accounts, Contracts, Entities, Currencies - Order items
Fulfilment line items.
Linked to Products, Orders, Contract items, Contract cycles - Invoices
Customer invoices generated by AR on order fulfilment.
Linked to Accounts, Orders, Entities, Currencies - Invoice items
Billed line items.
Linked to Products, Invoices, Order items, Contract cycles - Commercial allocations
Atomic accepted line/cycle quantities and amounts allocated to staged orders and eligible invoice scope.
Linked to Contract items, Contract cycles, Order items, Invoice items - Fulfilment events
Actual partial delivery/provisioning acceptance from verified external or manual evidence, not a header status.
Linked to Order items, Integration events, Users - Usage records
Measured accepted usage per contract line/period and source identity, with correction lineage.
Linked to Contract items, Contract cycles, Users - Payments received
Evidenced incoming cash or reconciled external AR receipt, with unchanged original amount and separate applications.
Linked to Entities, Accounts, Currencies, Integration events - Payment applications
Separate payment and invoice currency portions, noncash settlement and reversals, bounded by current available balances.
Linked to Payments received, Invoices, Approval decisions, Users - Credit adjustments
Positive credit-note magnitude with original invoice/line tax and net provenance, leaving historical cash intact.
Linked to Invoices, Document versions, Approval decisions, Users - Credit applications
Same-entity/customer/currency credit allocation or reserved surplus for a refund.
Linked to Credit adjustments, Invoices - Refunds
Independently authorised external cash refund funded either by unapplied receipt cash or surplus credit, never both.
Linked to Entities, Accounts, Payments received, Credit applications - Dunning actions
Unique eligible overdue-invoice reminder under balance, dispute, suppression and cadence rules.
Linked to Invoices, CRM policies, Message deliveries - Integration events
Authenticated external/manual evidence and one-time source effects across capture, signature, cash, usage, messages and payouts.
Linked to Entities, Migration batches - Outbound deliveries
Durable destination intent and acknowledgement separate from contract acceptance, invoice issue or payout settlement.
Linked to Entities, Document versions
- Campaigns
Marketing campaigns.
Linked to Users, Entities, Currencies, Segments - Campaign members
Leads/contacts attributed to a campaign with response tracking.
Linked to Campaigns, Leads, Contacts - Emails
Tracked email sends with open/click/reply events.
Linked to Users, Contacts, Leads, Campaigns - Segments
Versioned target criteria and recipient snapshot for channel campaigns.
Linked to Entities, Document versions - Message deliveries
One canonical recipient/channel/purpose message with current suppression check and actual send evidence.
Linked to Campaign members, Emails, Leads, Contacts - Campaign attributions
Frozen attributable pipeline/bookings/collection share prevents one sale being fully counted for every touch.
Linked to Campaigns, Campaign members, Opportunities, Contracts
- Users
CRM users — reps, managers, admins, marketers.
Linked to Territories, Commission plans, Entities, Currencies - Territories
Named-account or geo territories.
Linked to Users, Entities - Commission plans
Named commission schemes applied to reps.
Linked to Entities, Currencies, Document versions, Users - Quotas
Approved effective per-earner/territory/period quota versions with common currency and attainment basis.
Linked to Entities, Users, Forecast periods, Territories - Commissions
Immutable earned commission from the accepted or collected source event required by the frozen plan, with marginal attainment and original earner attribution.
Linked to Opportunities, Users, Commission plans, Commission statements - Commission statements
Monthly payout rollup per earner.
Linked to Users, Entities, Currencies, Forecast periods - Commission credits
Accepted earning attribution and quota basis per actual earner, independent of later account ownership.
Linked to Opportunities, Contracts, Users, Quotas - Commission adjustments
Attributable clawback, dispute resolution, SPIF or correction with independent review; never edit an earned commission.
Linked to Commissions, Commission statements, Users, Approval decisions - Commission payouts
Independent approved payout request and verified settlement, with durable uncertainty and rejection handling.
Linked to Commission statements, Document versions, Currencies, Users - Migration batches
Reviewed source/entity/cutoff import and nonposting baseline that suppresses historical automation.
Linked to Entities, Users - Migration items
Stable source-to-target mapping and immutable original financial/commercial/communication history.
Linked to Migration batches
Keys and references
Record identities remain stable when display names or document numbers change. Lines retain their parent and exact source references. Source allocations preserve the quantity and net amount already consumed, including reservations and compensating entries; a link to the contract header alone cannot establish what remains available for a partial order or invoice.
Currency and amount basis travel together. Where an original currency selector remains, it must agree with the linked currency record. Frozen rates explain cross-currency limits, forecasts, quotas and applications. Today’s rate or territory assignment must not rewrite an earlier accepted offer or earning.
Document versions, conversion keys, contract-cycle keys and provider event identities distinguish repeated delivery from new work. Reversals consume a bounded portion of the original effect and cannot also count as new forward processing. Current customer access is distinct from historical earning ownership, and both restrictions apply through joins and exports.
Migration order
- Register the batch, source namespace, cutoff and file digests. Load currencies, entities and user identities, then resolve manager, territory and commission-plan references in a controlled second pass.
- Load customer and contact identities with reviewed duplicate mappings. Preserve source evidence, ownership history and the most restrictive communication preferences across related lead and contact identities.
- Load product, price, configuration, routing, quota and earning policies with their effective versions and independent approval evidence. Unknown dependencies remain exceptions until resolved.
- Import pipeline history and selected forecast submissions with their original dates, source membership and currencies. Load accepted offers, contract versions, required signatures, renewal links and existing cycle identities.
- Reconcile original gross invoices, receipts and credits with their effective historical applications once. Preserve ordered, fulfilled and billed scope and its remaining availability. Opening summaries represent that same history; importing a net balance and subtracting its prior applications again would reduce it twice.
- Preserve commission credit, approved statement membership, paid history and unresolved payout requests. Historical Won, Active, Sent and Paid records remain nonposting evidence. Keep pending provider identities and reservations until their outcome is reconciled.
- Have the commercial, finance and marketing owners accept their relevant totals, access and lifecycle examples. Freeze the opening position before new operational events begin at the agreed cutoff.
Set up CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.