Current PMA Beta guidance

PMA Migration Bridge — Husbandry.Pro Direct Migration

Migration Bridge turns supported Husbandry.Pro CSV exports into one review project. PMA identifies each file by its columns, shows how values will map, prevents repeat source IDs from being created twice, and changes live records only after an owner or administrator confirms the reviewed import.

Review-first safety boundary

Uploading and previewing do not create PMA records. Unitless measurements, unsupported files, and ambiguous genetics remain evidence or review items. PMA does not silently overwrite structured genetics or create a second record for a source identity already imported successfully.

Before you begin

Use a PMA owner or administrator account.
Export every available Husbandry.Pro CSV you want reviewed, then keep an untouched copy.
Select related CSV files together so PMA can reconnect animals, occupied Housing references, contacts, and supported historical snapshots.
Do not rename columns or change IDs before the first PMA preview.

1. Select the export files together

Open Administration → Import Review.
Choose the Husbandry.Pro CSV files in one file-picker action. PMA recognizes the supported detailed-animal, contact, and compact animal-catalog schemas.
Wait for the Detected Import Adapter card to report Husbandry.Pro Direct Migration.

Expected result: PMA combines the selected files into one review project and explains any unsupported or misleadingly named source.

2. Review detection and mappings

Check each detected source, target record type, required mapping, transformation, warning, and relationship reference. A file named as a clutch export may actually contain an animal-catalog schema; PMA follows the headers and will not invent clutch records.

Expected result: Detailed animals map to PMA Animals; contacts map to Customers; occupied rack positions become Housing records; the compact catalog supplements detailed animals by source ID.

3. Inspect the dry-run preview

Resolve blocking rows before commit. Confirm the animal count, customer count, derived Housing count, last-feeding snapshot count, duplicates, warnings, and skipped rows. Weight or length without a unit remains in source evidence and notes rather than becoming a measurement.

Expected result: No live PMA record changes during preview. Every row has a proposed action and reconciliation reason.

4. Commit and reconcile

Commit only after the preview totals match the source.
Open the completed migration in History and verify imported, skipped, conflicted, and failed totals.
Review Structured Genetics items. Apply only exact suggestions you personally confirm; leave uncertain text unconfirmed.
Open imported animal profiles, Housing, contacts, and historical events to confirm dates and relationships.

Safe retry and rollback

If you safely retry the same source data, PMA recognizes records that were already imported and skips them instead of creating duplicates. Automatic rollback is available only when the original migration created records and no later edits or live dependencies make removal unsafe. A successful rollback also clears its source registry entries.

Current migration limits

The supplied samples prove animals, contacts, and a compact animal catalog—not full clutch, breeding, Housing hierarchy, media, medication, shed, cleaning, or complete feeding history exports.
Only the last-feeding snapshot can be derived from the observed animal file.
Structured genetics requires an exact verified PMA trait and unambiguous allele. Combinations remain manual review.
Additional export profiles will be added only after representative fixtures are available.

Troubleshooting

The file is ignored: preserve its original headers and verify it matches a supported observed schema.

An animal is skipped: inspect duplicate reason; the same source ID may already be registered.

Genetics says Needs review: PMA could not prove one verified trait and allele or found a conflict. Keep the source text and review Genetics manually.

Rollback is blocked: an imported record was edited or connected to later activity. Do not delete dependencies merely to force rollback.