Using SowWindow

Save, back up and import a plan

A plan belongs to the browser where you save it. SowWindow has no account or automatic cloud synchronization. Use a versioned JSON backup when the editable plan matters, when moving to another browser, or before making a change you may want to undo.

Reviewed Oct 27, 2026

Save and check the result

Give the plan a recognizable name, save it, and read the save status. Saved means the browser accepted the local record. A task list still visible on the page is not enough to prove that saving succeeded.

If saving fails, keep the page open. Your current changes can remain in memory even when local storage is unavailable or full. Try saving again if appropriate, or download a JSON backup before closing the page. The error should not clear the work you are trying to keep.

Understand the storage boundary

Plans are local to this site in the current browser. Clearing site data can remove them, and another browser does not automatically have the same records. Private browsing is not a suitable place for your only long-term copy.

Deleting a local plan does not remove files you previously downloaded or calendar events you imported elsewhere. Keep those copies in mind when organizing or removing your information.

Make an editable backup

Choose the JSON backup format. It preserves the plan structure, stable crop identities, dates, task states, notes, parameter snapshots, and manual choices needed for recovery. Keep the downloaded file somewhere you can find it.

PDF, CSV, ICS, and SVG are working outputs for other tasks. They do not contain every part of the editable plan and are not substitutes for JSON when you want to restore all settings.

Import and review before replacing anything

Select a JSON backup and read the preview. If its stable plan ID already exists in the browser, choose whether to import it as a new plan or replace the existing one. A matching display name alone is not proof that two records are the same plan.

  1. Keep a backup of the current plan if you may want it later.
  2. Read the imported plan summary and any differences.
  3. Use Import as a new plan to keep the existing record.
  4. Choose replacement only when you intend to overwrite that identified record.

Handle an unsupported or invalid file

If the file uses a newer format than this version can read safely, keep the original file and use a compatible version or a supported backup. Do not remove its version field or alter identifiers to force an import. Existing plans must remain unchanged after a rejected import.

A malformed file, an unknown crop reference, or a file beyond the accepted limits is rejected without changing existing plans. Read the stated error and choose a supported file. Keep the original backup; do not delete unrecognized tasks merely to force an import.

Keep a season copy

Duplicate a plan when you want a separate season or experiment. Check its dates, statuses, and assumptions before using it. A saved data version makes the original choices traceable; a later source update should not rewrite them without your review.

Sources and conditions

Keep planning