How will perennial crops assessed as "other crop" in CFT be migrated?
Perennial crops in CFT that do not have a corresponding perennial typology in CFP or where the typology is unknown - e.g. if assessed as "tree crops" in CFT will not be migrated as perennials. Instead, they will be migrated into the CFP annuals pathway and mapped to the crop type “other annual crop”. This includes:
- Raspberry
- Blueberry
- “Tree crops” - either no specific CFP perennial typology exists, or the typology is unknown and therefore cannot be transferred as perennials. This may include cocoa, citrus fruits, almond or oil palm.
This approach was chosen because in most cases, there is currently no suitable perennial typology for these crops in CFP, and creating temporary or generic perennial options would require significant extra methods and development work and could introduce misleading or “made‑up” default values. For "tree crops", a matching typology may exist in CFP, but there is too much risk to assume this match and assign assessments to existing typologies without concrete proof. Therefore, all tree crops will be migrated to the annual pathway (e.g. "tree crop" assessments with names such as "mandarine" or "almond").
As a result, users will see above perennials assessments as “other annual crop” in CFP. Assessments will still run, but residue and pesticide results may be more conservative and may differ from CFT, reflecting the generic “other annual” treatment rather than a specific perennial model.
New assessments for these crops can be created in CFP in the available pathways - either as "other crops" in annuals (raspberry, blueberry) or as perennial if the applicable typology exists. Also see this article for perennials with no typology.
*Consideration:
Related Articles
How will perennials with a matching typology in CFP be migrated?
Perennial crops assessed in CFT that already have a corresponding perennial typology in CFP will be migrated into the CFP perennials pathway, not the annuals pathway. All new/additional fields required by the CFP perennial model will be left blank ...
Canada-specific beef system not migrated to CFP
In the CFT beef pathway, user were allowed to select a production system specific to Canadian Farms. At this stage, however, this Canada-specific beef module as well as the related properties and assessments will not be migrated to CFP and not ...
What will NOT be migrated in 2026?
At this stage, we will not yet migrate Biodiversity, Water, Food Loss & Waste, and Other Livestock assessments. They will continue to exist in CFT until they are ready to be migrated to CFP. Please note: CFT crop GHG assessments including Water/FL&W ...
Exception for beef: results will not be migrated from CFT to CFP
Given the current technical setup, we will be able to migrate the input data of beef assessments created in CFT, but not the results. Users will need to re-run their assessments in CFP 3.0 to generate 3.0 results. The comparison of results from rerun ...
My crop is not listed in the CFP perennials pathway. Can I use it for other crops?
The current methodology behind the Cool Farm perennials pathway only supports the crops you see in the dropdown list. Unfortunately we cannot recommend to use any of the options as proxy/alternative, as each perennial crop exhibits a unique growth ...