crossary
How it worksPricingFree templateLog inStart free

Source → target field mapping, reviewed

Two specs in. One mapping out.

The AI proposes the mapping and quotes the spec behind each rule. You sign off.

Start freeWatch the film0:30
HubSpot 9 fields
Salesforce 11 fields
  • Record ID to ContactId.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • First Name to FirstName.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • Last Name to LastName.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • Email to Email.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • Phone Number to Phone.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • Company Name to AccountName.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • Job Title to Title.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, high confidence.
  • Country to MailingCountry.

    No source quote on this row — a direct mapping is self-evident from the field name.

    direct, medium confidence.
  • Create Date to CreatedDate.
    Salesforce field rules.md:
    Store as ISO 8601, UTC.
    transformation, medium confidence.
  • = "HubSpot Import"
    "HubSpot Import" to LeadSource.
    Kickoff call - notes.txt:
    Stamp every contact with the constant value "HubSpot Import" so we can find this batch later.
    constant, high confidence.
  • Region.
    no clear source.

    No HubSpot field tracks sales territory, and it must not be guessed from Country. The kickoff notes mark this as an accepted, pre-decided gap — so it's flagged, not asked.

    unknown, none confidence.

Tap any field.

10 / 11 target fields mapped · 1 the run declined to guess

crossary
How it worksThe guided sampleWorked examplesGuidesFree mapping templatePricingTrust mechanicsFAQSecurityPrivacy & dataSupportTermsLog in
© 2026 Crossary
TermsPrivacyCookiesSubprocessorsDPA

Hover any field.Tap any field.

3 integration credits free · no card

Built for

  • Integration & interface
    engineers
  • Implementation & onboarding
    consultants
  • Data & migration
    engineers
  • EDI & interface
    analysts
  1. Drop.

    • HubSpot contacts export.xlsx
    • Salesforce Contact fields.json
    • Salesforce field rules.md
    • Kickoff call - notes.txt
    xlsxjsonmdtxt

    Source, target, and your notes.

    pdf · xlsx · csv · txt · md · json · xml · xsd · wsdl · sql · yaml · yml · tsv

  2. Review.

    Salesforce field rules.mdStore as ISO 8601, UTC.
    Create Date→CreatedDatemediumsuggestedapplied✓

    Rules show their proof.

  3. Sign.

    .xlsx
    Contacts — HubSpot → SalesforceExported

    A real .xlsx, signed off by you.

That workbook layout is yours either way — take the source-to-target mapping template as a sample-filled .xlsx. No email, no account.

A wrong mapping is worse than an honest gap.

One mapping outthe film · 0:30

Watch with sound

This is the real thing.

Crossary's mapping review table for a HubSpot to Salesforce contact sync: eleven source-to-target rows with mapping type, confidence and status. Sorted riskiest-first, so the top row is the target field Region with no source and one issue flagged.
The mapping drawer for the CreatedDate field: a transformation expression, high AI confidence, the reasoning and assumption behind it, and the passage from the kickoff-call notes it is based on — highlighted and labelled verbatim.
The validation panel showing structural checks passed, coverage of ten of eleven target fields, zero blockers, one warning about the unmapped Region field, and a disclosure titled What Validated means.
Every row, and the one it wouldn't guess.
Run the sample →

Trust isn’t asked for here — it’s enforced in code, and written down.

We check

  • every required field is mapped
  • the source fields exist
  • no duplicate rows
  • obvious type mismatches
  • no blocking question is still open
  • the overall structure holds up

We don’t check

  • whether each mapping is actually correct
  • whether the AI's confidence rating is calibrated
  • whether your transformations actually run
  • how it behaves on real data
  • whether your customer has approved it
  • whether it succeeds downstream

“Validated” means one thing.

A deterministic structural check — zero AI, zero spend — that tells you plainly what it did and did not verify.

exportre-import
.xlsx
?

Never loses your note.

Edit the sheet anywhere. Every note comes back as a question.

no clear sourceindustry_vertical your library
→Industrysuggested

A gap you filled once stops being a gap.

It only fills what the AI left empty, and you still approve it.

your workspacemappingsdecisionsnotes
shared
model

It never trains a shared model.

It maps the spec, not your data.

Privacy & data terms →Subprocessor list →Security →

Start free. Pay for AI runs, never for reviewing.

Reviewing, validating, exporting, and round-trip re-import don't call the AI — so they're always free, on every plan.

Free

$0

For your first real integration.

  • 3 integration credits, one-time
  • Free review, validate & export
  • Round-trip re-import
  • Mapping Memory included
  • 1 workspace · up to 2 members
Start free

Pro

Most teams start here
$99/ month

~20 integrations a month.

  • Everything in Free
  • ~20 integration credits / mo
  • Heavier reasoning pass (more compute per run)
  • Unused credits roll over
  • 3 workspaces · up to 3 members
Start with Pro

Team

$399/ month

~75 integrations a month.

  • Everything in Pro
  • ~75 integration credits / mo
  • Unlimited workspaces · up to 10 members
Start with Team

Plus applicable taxes.

Run out? Existing work is never blocked — review, validate, export & re-import stay free. Unused credits roll over, you can buy more anytime, or upgrade. Only new AI runs pause.

Bigger team, procurement review, or a counter-signed DPA? Talk to us.

The honest answers, before you sign up.

What's a credit?

Roughly one standard integration. Higher Accuracy and unusually large or heavily re-run jobs use more — and you can see what each integration cost.

What's always free?

Reviewing, validating, exporting, and round-trip re-import. They don't call the AI, so they never use a credit.

What if the first pass isn't right?

Editing rows by hand, re-validating, re-exporting, and round-trip re-import are always free. Asking the AI to have another go isn't: re-running extraction or mapping costs roughly what the first run did, and submitting answers to a flagged question re-runs that phase too, so it's charged the same way. Credits are metered on actual usage rather than per click, and you can see what each integration cost.

What does a “signed” workbook mean?

That a person attested to it. Before an export you confirm you reviewed the mappings, and that attestation — who, when, and what validation had passed — is stamped on the workbook's cover sheet. It's a record of human review, not a cryptographic signature, and the file opens normally in Excel, Google Sheets, or Numbers.

Is accuracy gated to higher plans?

Every plan gets the same core mapping quality. Higher Accuracy — an optional, heavier pass — is on paid plans; Mapping Memory is included on every plan.

What happens when I run out?

Existing work is never blocked — review, validate, export and re-import stay free. Unused credits roll over, you can buy more anytime, or upgrade. Only new AI runs pause.

How do I upgrade?

Click subscribe on the plan you want — secure checkout, and your plan activates immediately.

Does my data train your model?

No. Mapping Memory is scoped to your workspace and never crosses it; no shared model learns from your mappings.

Map your first integration in the next ten minutes.

Upload a source and a target spec. Get back a reviewed, evidence-backed mapping workbook — with every honest gap flagged for you.

Start free

3 integration credits free · no card · no lock-in.