Crossary

About Crossary

Crossary produces source-to-target field mapping workbooks for integration and migration work, and its governing principle is that a wrong mapping is worse than an honest gap. You upload the source and target specifications in whatever form they exist — xlsx, pdf, csv, json, xml, xsd, sql or yaml — and a strict five-stage pipeline runs: artifacts are ingested and, if a file cannot be fully read, it tells you exactly how much it dropped; a field inventory is extracted from both sides so you map against the real surface rather than a summary; each target field gets a proposed source, a mapping type, verbatim evidence quoted from the source spec with its sheet and row, the reasoning and assumptions behind the proposal, and a confidence level, abstaining rather than guessing when there is no clear source; a deterministic validation pass checks structural and cardinality blockers with no AI and no spend; and export produces a signed .xlsx. The round trip is the part that makes it usable in a real engagement: the export is an ordinary workbook, not a locked app view, so a developer or client can edit decisions and add notes in Excel, Google Sheets or Numbers without a Crossary login, and on re-import it applies what matched, skips rows that moved underneath it rather than overwriting them, and turns every note into a tracked question. Reviewing, validating, exporting and re-importing never call the AI and are free forever on every plan.

Key Features

Tags