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.
- Technology CRM
- Data model
The tables behind Technology CRM
Technology CRM ships with 11 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
- 11
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Account scope
Organizations owns Accounts and team members. Team members.User references Users. Opportunities.Counterparty identifies the account, and Owner identifies the responsible member.
Pipeline and qualification
Opportunities retains Status, expected close date, expected value USD, probability percent and Revision. Relationship activities holds the interaction evidence used during qualification.
Relationship activities
Relationship activities.Parent references Opportunities. Line number and Revision identify the activity context; activity type, due at, completed at and Outcome describe the work.
Technical evaluations
Technical evaluations.Parent references Opportunities, with its own Organization, Status and Revision. Environment, trial ends, active seats and security review describe the evaluation evidence.
Proposal and outcome review
Review decisions.Parent references Opportunities, and Reviewer references team members. Source revision ties the decision to the submitted content. Won at and loss reason describe closed outcomes on Opportunities.
Evidence and reconciliation
Record attachments links files to Opportunities and uploaded by to team members. Operation receipts connects operation key, expected revision, result state and effect references to the parent opportunity. Exchange rates holds read-only effective-rate reference data.
Every table, by feature
- Account scope5
- Pipeline and qualification5
- Relationship activities4
- Technical evaluations5
- Proposal and outcome review6
- Evidence and reconciliation6
- Shared and settings1
- Accounts
Customer and prospect accounts belonging to an organization.
Linked to Organizations - Organizations
Operating organizations that own accounts, opportunities and team membership.
- Team members
Named team members with their organization, platform identity and role scope.
Linked to Organizations, Users - Users
Users
Linked to Users - Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts
- Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Accounts
Customer and prospect accounts belonging to an organization.
Linked to Organizations - Team members
Named team members with their organization, platform identity and role scope.
Linked to Organizations, Users - Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Linked to Opportunities - Operation receipts
Durable receipts for guarded operations with stable operation keys.
Linked to Opportunities
- Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Linked to Opportunities - Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Record attachments
Evidence files attached to an opportunity with visibility scope.
Linked to Opportunities, Team members - Operation receipts
Durable receipts for guarded operations with stable operation keys.
Linked to Opportunities
- Technical evaluations
Technical evaluation records supporting a recorded evaluation outcome.
Linked to Opportunities, Organizations - Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Organizations
Operating organizations that own accounts, opportunities and team membership.
- Record attachments
Evidence files attached to an opportunity with visibility scope.
Linked to Opportunities, Team members - Operation receipts
Durable receipts for guarded operations with stable operation keys.
Linked to Opportunities
- Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Linked to Opportunities - Review decisions
Independent review decisions recorded against an opportunity revision.
Linked to Opportunities, Team members - Record attachments
Evidence files attached to an opportunity with visibility scope.
Linked to Opportunities, Team members - Operation receipts
Durable receipts for guarded operations with stable operation keys.
Linked to Opportunities - Team members
Named team members with their organization, platform identity and role scope.
Linked to Organizations, Users
- Operation receipts
Durable receipts for guarded operations with stable operation keys.
Linked to Opportunities - Record attachments
Evidence files attached to an opportunity with visibility scope.
Linked to Opportunities, Team members - Review decisions
Independent review decisions recorded against an opportunity revision.
Linked to Opportunities, Team members - Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Linked to Opportunities - Technical evaluations
Technical evaluation records supporting a recorded evaluation outcome.
Linked to Opportunities, Organizations
Keys and references
Preserve source identifiers when importing. Most records use Id; exchange rates uses ID. Opportunities.record number and account and organization codes provide readable identifiers. Users.User is a self-reference that must be resolved intentionally during identity setup.
Keep the account, owner and technical evaluation inside the opportunity’s organization. Map the authenticated user through team members.User before applying ownership filters. Compare review decisions.source revision and operation receipts.expected revision with the revision involved in the actual action, rather than assuming that the latest opportunity state proves an earlier result.
Migration order
- Establish Users and Organizations, including user references and operating time zones.
- Load team members and Accounts with organization references and eligibility context.
- Establish the governed exchange rates source where required, preserving read-only ownership.
- Load Opportunities, then their relationship activities and technical evaluations.
- Import record attachments, review decisions and operation receipts with original parent references, revision evidence and dates intact.
Set up Technology CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.