# Family Historian 7 interop checklist

Use this checklist when moving a tree between Heartwood and Family Historian
7. It covers both directions and calls out the checks that cannot be automated
without a licensed FH7 installation.

## Prerequisites

- A licensed copy of Family Historian 7 on Windows.
- A Heartwood tree with representative data: multiple personas, events
  with dates/places, notes, at least one refuted/superseded assertion
  (to exercise the `_HW_*` extension namespace), and at least one living
  person (to exercise egress suppression).

## Steps (both directions, each release)

1. **Heartwood → FH7 (5.5.1):** `gedcom.export` (or `POST
   /v1/gedcom/export`) with `gedcom_version: "5.5.1"`. Open the resulting
   file in Family Historian 7. Confirm: individuals/families/events/notes
   import cleanly; no FH7 parse errors or warnings about unrecognized
   structure (bare `_HW_*` tags are expected to show as FH7's own
   "unknown custom tag" — not an error); living persons present in the
   source tree are absent from the export (egress suppression, D6/D12).
2. **Heartwood → FH7 (7.0):** repeat with `gedcom_version: "7.0"`. Confirm
   FH7 7.x import support for `SNOTE`/`SCHMA` (or documents its own
   flattening) and that the `_HW_*` tags are declared in `HEAD.SCHMA`
   with the registry URI.
3. **FH7 → Heartwood:** from Family Historian 7, export the *same* tree
   (loaded from step 1 or 2) back out as GEDCOM. `gedcom.import` (or
   `POST /v1/imports/gedcom`) that file into a fresh Heartwood tree.
   Compare the resulting `LossReport` against the original export's
   `LossReport`: any newly-introduced `dropped`/`downgraded` entries not
   present in the original round trip indicate an FH7-side
   reinterpretation worth noting below.
4. **Diff and record:** note anything FH7 did unexpectedly (silently
   dropped a structure, misrendered a date, chocked on an `_HW_*` tag in
   a way that corrupted neighboring data) in the dated log below, filed
   as a follow-up issue if it represents a Heartwood-side bug (not an FH7
   limitation).

## What the automated gate covers

Heartwood's own fixtures continuously exercise import, export, validation,
and re-import, including loss-report accounting. This FH7 checklist adds a
real third-party application's interpretation of the resulting files; it does
not replace the automated round-trip gate.