1. Agriculture ERP
  2. Data model and import order
Reference

The tables behind Agriculture ERP

Agriculture ERP 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
7
Change it
Add fields and tables in Proto

How the model is organised

Field register

Fields provides identity and readiness; field observations attaches measurements to the plot.

Crop planning

Crop plans holds planting intentions, while crop cycles carries the field reference and season stage.

Field work

Field tasks connects Fields, crop cycles and the assigned People record.

Input lots and usage

Input stocks holds lot balances; input usage connects the quantity applied to the lot and task.

Harvest acceptance

Harvests references crop cycles and People through accepted by.

Yield grading

Yield grades references its source Harvests record.

Season review

Crop, task and harvest links support the operating review. Users and People supply account and operator identity.

Every table, by feature

Field register

5 tablesAbout this feature
  • Fields

    Farm fields and plots with area and operational status

  • Field observations

    Field measurements and notes captured during the season

    Linked to Fields
  • Crop plans

    Planned crop variety, planting and expected harvest per field

    Linked to Fields
  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields
  • Field tasks

    Assigned field work with lifecycle status and completion date

    Linked to Fields, Crop cycles, People

Crop planning

5 tablesAbout this feature
  • Crop plans

    Planned crop variety, planting and expected harvest per field

    Linked to Fields
  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields
  • Fields

    Farm fields and plots with area and operational status

  • People

    Farm staff and operators referenced by operational records

    Linked to Users
  • Users

    Users

    Linked to Users

Field work

7 tablesAbout this feature
  • Field tasks

    Assigned field work with lifecycle status and completion date

    Linked to Fields, Crop cycles, People
  • Fields

    Farm fields and plots with area and operational status

  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields
  • People

    Farm staff and operators referenced by operational records

    Linked to Users
  • Users

    Users

    Linked to Users
  • Input usage

    Input quantities applied against a field task

    Linked to Field tasks, Input stocks
  • Input stocks

    Agricultural input lots with quantity on hand and expiry

Input lots and usage

5 tablesAbout this feature
  • Input stocks

    Agricultural input lots with quantity on hand and expiry

  • Input usage

    Input quantities applied against a field task

    Linked to Field tasks, Input stocks
  • Field tasks

    Assigned field work with lifecycle status and completion date

    Linked to Fields, Crop cycles, People
  • Fields

    Farm fields and plots with area and operational status

  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields

Harvest acceptance

5 tablesAbout this feature
  • Harvests

    Harvested quantities per crop cycle with grade and acceptance

    Linked to Crop cycles, People
  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields
  • Field tasks

    Assigned field work with lifecycle status and completion date

    Linked to Fields, Crop cycles, People
  • People

    Farm staff and operators referenced by operational records

    Linked to Users
  • Users

    Users

    Linked to Users

Yield grading

3 tablesAbout this feature
  • Yield grades

    Accepted and rejected weights graded from a harvest

    Linked to Harvests
  • Harvests

    Harvested quantities per crop cycle with grade and acceptance

    Linked to Crop cycles, People
  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields

Season review

6 tablesAbout this feature
  • Crop cycles

    Crop cycles planted on a field from planning through closure

    Linked to Fields
  • Fields

    Farm fields and plots with area and operational status

  • Field tasks

    Assigned field work with lifecycle status and completion date

    Linked to Fields, Crop cycles, People
  • Field observations

    Field measurements and notes captured during the season

    Linked to Fields
  • Harvests

    Harvested quantities per crop cycle with grade and acceptance

    Linked to Crop cycles, People
  • Yield grades

    Accepted and rejected weights graded from a harvest

    Linked to Harvests

Keys and references

The model contains 11 tables. Preserve the exact source references during import. People.User resolves an account, while field tasks.assigned to and Harvests.accepted by reference People. Resolve the required Users.User self-reference using the account mapping agreed for the import.

Crop plans and crop cycles each reference Fields. Use the crop-plan command’s returned source links to follow its matching cycle. Yield grades reaches the cycle through Harvests.Cycle. Input usage reaches the field through field tasks.Field. Match by stable record identity rather than relying on a display name that may be shared or changed.

Migration order

  1. Prepare Users mappings, then People with verified User references.
  2. Import Fields with reviewed identity, area and Status, then input stocks with units and opening quantities.
  3. Import crop plans and crop cycles, resolving Field references and checking the plan-to-cycle match.
  4. Link field tasks to Field, Cycle and assigned to; attach field observations to the intended Fields.
  5. Import input usage with resolved Task and Input references. Reconcile the opening lot quantities without replaying historical deductions.
  6. Import Harvests with Cycle and accepted by resolved, then yield grades with exact Harvest references. Review entry and acceptance together before opening the next operating cycle.

Set up Agriculture ERP your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started