Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
All skills
Data

Reconcile a data migration

Prove the target matches the source, field by field.

Fill it in

Both sides.

Matching row counts hide truncated columns.

With enough context to diagnose each class.

Your prompt

Reconcile the migration.

Compare FIELDS, not counts. Matching row counts is the reassurance that hides
everything: a truncated column, a timezone shift, a decimal rounded, a null that
became an empty string. All of those preserve the count exactly.
Check the aggregates too: sums of every numeric column, min and max of every date.
Those catch a systematic shift that a row sample misses.

For each class of difference, show enough examples to diagnose it, and say how
many rows are affected.
Separate expected transformations from unexpected drift, and be explicit that
anything you cannot classify is unexplained rather than acceptable.
Continue and pick your folderOpens with everything above already filled in.

Why this works

Matching row counts hide everything that matters: a truncated column, a timezone shift, a null that became an empty string. This compares fields and aggregates, and is explicit that anything it cannot classify is unexplained rather than acceptable.

More data skills

  • Extract to a table
  • Analyse a spreadsheet
  • Chart this data

Use it now in a chat in 1 click

Use Reconcile a data migration
  • Clean a dataset
  • Write a data dictionary
  • Read out an A/B test