Who this is for
An operations manager or small-business owner whose Airtable table repeats the same customer, supplier or project text on every row, so one correction means editing dozens of records.
Names have drifted into several spellings, reports double-count, and nobody trusts the table as the one place for that information.
The result
On a duplicate of the base, the child table has the same number of records as the original table had at the recorded snapshot, the parent table holds exactly one record per approved distinct key, every child links to exactly one parent apart from listed exceptions, and sampled looked-up values match the old text columns. A cut-over note gives the snapshot figures, a check for records added or deleted since, and the consequences of adopting the duplicate.
What is included
- One table in one base, split into one parent table and one child table linked through a single linked record field
- A key list and normalisation rules, agreed with you before any record is changed, saying which spellings are the same parent
- A snapshot taken when the duplicate is made, with its date and time, the original table's record count and its distinct key count recorded
- Creation of the parent table, linking of every child on the duplicate base, and lookup fields standing in for the old repeated columns
- Reconciliation of record counts, parent counts, empty links and a twenty-record sample you choose
- A cut-over note for adopting the duplicate as your working base: the consequences, and a check you run on the cut-over day for records added or deleted in the original table since the snapshot, which does not find edits to existing records
You receive
- The approved key list with the normalisation rule applied to each variant, and a list of exceptions needing your decision
- The restructured duplicate base, with the child table linked to the parent table
- A reconciliation sheet: the snapshot date and time, record counts before and after, parent count, empty-link count and the sample comparison
- A list of the views, formulas, automations, forms, share links and interface pages that referenced the old columns or the old base, each marked repaired on the duplicate or needing your rebuild
- A cut-over note: what changes when your team moves to the duplicate, the delta check for records added or deleted since the snapshot, and the order of steps for the day
What is not included
- Splitting more than one table, or moving the data to another platform
- Cleaning free text beyond the agreed key and normalisation rules, or deciding which of two genuinely different customers are the same
- Rebuilding interface pages, forms, sync configurations or automations beyond the ones named in the scope
- Repeating the split on your live base: that would redo the checked work on live data without the same verification, so it would be a separate quote with its own reconciliation
- Real personal data leaving your workspace, or any message sent to a real contact
What we need from you first
- The table name, its approximate record count and the columns that repeat parent information
- How many distinct parents you think there are, and which column is most reliable as a key
- Which views, automations, forms or interface pages depend on the table
- Do not send record exports, a base invitation or passwords in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- The child table on the duplicate base holds exactly the same number of records as the original table held at the recorded snapshot date and time.
- The parent table holds exactly one record for each key on the approved key list and none that is not on it.
- Every child record links to exactly one parent, apart from records on the signed-off exception list.
- For a twenty-record sample that you choose, each looked-up value equals the old text value, or differs only where the approved normalisation rule changed it and the sheet says so.
- The cut-over note's delta check, tested on the duplicate with two records added and one deleted after the snapshot, shows the net change of one record and lists all three records by key.
You inspect the reconciliation sheet, the duplicate base and the cut-over note, then sign off before payment. You decide when to adopt the duplicate, run the delta check that day and re-point what points at the old base.
When we would stop or decline
- The key column is free text with so many variants that nobody can agree which are the same, so a safe key cannot be set
- The table is synced from another base or source and linked records cannot be created in it
- The table is the live system of record for something that cannot pause or be moved to a different base, so a cut-over day cannot be agreed
- The table holds personal data and no secure handover route for the duplicate can be agreed with you
Questions
Will you change my live base?
No. The work happens on a duplicate base, which is a separate base. You decide when your team moves onto it, and the cut-over note lists what that changes. Repeating the split on your live base would be a separate quote.
What happens to edits made in the live table while you work?
The duplicate reflects the table at the recorded snapshot. On the cut-over day you run a short check that lists records added or deleted since. It does not find edits to existing records, so either stop editing the original table in the meantime or keep your own list of the edits and re-enter them.
What if two spellings are really two different customers?
That is your decision. We list the ambiguous cases as exceptions and wait for your answer before linking them.
Can you move my Airtable data to another tool?
No. This job restructures one table inside Airtable. A move to another platform is a different outcome.
Price and terms
From £595 · untested offer price. After the agreed checks pass and you sign off. No advance payment.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.