Planva supports a seamless move from your current platform. Fields, field groups, crops, seasons, machines, tracker bindings, machine tasks and agro-operations are moved catalogue by catalogue, not as one file of outlines. Migration is included in the contract, and data stays in-country or on your own servers.
Start with the records you need to keep. Boundaries, crop rotation and completed work are different datasets. A file containing the outlines of your fields is not a complete copy of the account.
Check what the source platform can export
Cropwise publishes a boundary export guide for its US platform. It starts from Farm Settings and exports one farm at a time. Account versions and regions differ, so confirm the export available in your own account. Field boundaries can also be loaded into Planva from Shapefile or KML files.
| Record | What to agree before the move |
|---|---|
| Fields and groups | Field names, identifiers, areas and the coordinate reference of the export. |
| Crops and seasons | The seasons and crop records to keep against each field. |
| Machines and trackers | Machines, equipment and the tracker bindings needed for daily work. |
| Machine tasks and agro-operations | The date range you need for plan versus actual and for reports. |
Accept the move with your agronomist
- Inventory. List farms, fields, seasons and required records before export. Keep a copy of the source files.
- Trial move. Choose the catalogues to move. Include a field with an awkward boundary, a renamed field and an older season.
- Compare. For each catalogue Planva shows how many records were created, updated, left unchanged or not transferred. Reconcile field counts and areas against the source.
- Run a task. Create an agroplan, attach a machine task and check plan versus actual on the field.
- Cut over. Agree which system is authoritative from the switch date and how new work is recorded during the transition.
Put deployment and scope in the proposal
Pricing depends on acreage, modules, deployment model and implementation scope, and is fixed in the proposal and contract. Agree the records to move, support and data placement before onboarding. Support works 24/7, and agronomists are part of the support team.
Who should not buy
Do not switch until the trial preserves the records and workflows your team relies on. If a required report cannot be reproduced in the trial, keep the current process while that requirement is resolved.