Compatibility workflow

Make this table match a target template

Open the source you already have, provide the target structure, confirm the mapping and create a compatible output without silent guesses.

Local mappingExplicit choicesNo account

1. Source

Waiting for a source table…

Open source table or spreadsheetCSV/TSV/text tables, Excel/OpenDocument/legacy spreadsheets, JSON, HTML or XML

If a compatible TaskThimble table already exists, it is loaded automatically. You can replace it here at any time.

2. Target template

Open target table or spreadsheetOnly the target column structure is used for mapping.

Designed for export/import mismatches

Many data problems are compatibility problems: one system exports Customer Name while another expects name, or the target import requires a fixed column order. This workflow lets you map those structures explicitly.

Start with the format you actually have

Compatible delimited text, spreadsheet, JSON, HTML-table and simple repeated-record XML sources can enter through the same local table layer. If a file contains several sheets or tables, TaskThimble asks you which one to use.

No silent semantic guesses

Header similarity can suggest a likely source column, but ambiguous mappings stay blank. TaskThimble does not infer business meaning such as converting a country name into a country code unless a dedicated transformation explicitly supports that rule.