# Upgrading from T3RRA Cutta V1 to V2

Transitioning from **T3RRA Cutta V1** to **T3RRA Cutta V2** has been designed to be as straightforward as possible. The familiar wizard-based workflow has been retained, along with the core operating principles used throughout V1. While the user interface has been refreshed, existing users should find the overall workflow familiar.

## What's New?

T3RRA Cutta V2 introduces several significant enhancements while preserving the concepts that experienced users already know.

The most notable additions include:

- The ability to combine different design types within separate regions of the same field.
- Support for creating designs on top of existing designs.
- The introduction of **As-Applied** functionality, allowing completed earthworks to become part of the project's working surface.

These features provide substantially greater flexibility but may require a small adjustment to established workflows.

When creating or modifying designs, pay particular attention to the surface being used as the design reference, such as the **existing elevation** or an **existing design surface**.

## Understanding As-Applied

The introduction of **As-Applied** functionality represents one of the largest workflow changes between V1 and V2.

We strongly recommend reading the **Understanding As-Applied** section of this manual before using the feature. Understanding how As-Applied surfaces interact with existing designs will help avoid confusion and ensure predictable design behaviour.

If preferred, As-Applied functionality can be disabled, allowing operation in a manner similar to previous versions.

## Migration Guide

Users upgrading from T3RRA Cutta V1 are encouraged to review the **T3RRA Cutta V1 to V2 Migration Guide** before beginning work. The guide highlights the key workflow changes and explains how familiar V1 concepts have evolved in V2.

## File Compatibility

T3RRA Cutta V2 has been designed to maintain compatibility with T3RRA Cutta V1 wherever practical.

In most cases:

- Projects created in **V1** can be opened in **V2**.
- Projects created in **V2** can be opened in **V1**, provided they do not contain features that are unique to V2.

Because V2 introduces additional project layers and capabilities that are not supported by V1, some projects may not be fully compatible when opened in older software versions.

This compatibility allows V1 and V2 systems to continue working together during transition periods, provided project features remain compatible with both versions.