Airtable to HubSpot migration.
Bases become objects. Airtable is where a lot of companies design their data model before they know they are designing one. Moving it into HubSpot means turning computed columns into stored properties and linked records into real associations.
The base is the schema nobody agreed to.
Somebody built a base, it worked, and four departments started using it. Now it holds the customer list, the pipeline, the delivery tracker and the reporting, computed live through formulas that only exist inside Airtable.
Computed on read. Gone on export.
Airtable — the formula layerWhat a CSV of a base does not contain.
Formulas and rollups compute on read
A rollup summing linked records exists only while Airtable is rendering it. Each one becomes a stored property written by workflow, a HubSpot calculated property, or a report — and the choice matters for what you can filter on later.
Linked records become associations
A link field is an association with no label and no direction. HubSpot associations are typed and labelled, which is better, but the mapping has to be designed rather than inferred.
Interfaces have no equivalent
Airtable Interfaces are custom apps. In HubSpot that surface becomes record page layouts, custom cards or, where it genuinely needs to be an app, a CRM extension built as a project of its own.
Views are not reports
Grouped, filtered and sorted views are how most teams read an Airtable base. They rebuild as HubSpot views and reports, which behave differently enough that the team needs walking through it.
Automations and scripts
Airtable automations and script blocks carry business logic. They rebuild as HubSpot workflows, or as custom-coded workflow actions where the logic genuinely needs code.
Attachments live in Airtable
Attachment fields hold files on Airtable infrastructure with expiring URLs. They have to be downloaded and re-uploaded rather than referenced, or they quietly disappear later.
The sequence, start to cutover.
Discovery
Object counts, custom fields, automation and the integrations that will break on the way out, read from the source system rather than from a questionnaire.
Mapping
Field by field, including what will not carry across, agreed and signed before anyone exports anything.
Dry run
A complete rehearsal into a sandbox portal, reconciled against source counts so the gaps surface a month early rather than on cutover night.
Automation rebuild
Workflows, sequences and routing rebuilt to the new model rather than transliterated from the old one, which is how a migration inherits a decade of workarounds nobody remembers writing.
Cutover
A dated switch with the legacy system read-only for a defined window, and a rollback that was tested rather than assumed.
Post-migration support
A named engineer through the first full reporting cycle, which is when the questions actually arrive.
Not everything wants to be an object.
The instinct is to recreate every table as a custom object. Most tables are properties on an existing record, a pipeline, or a report. Custom objects are billed by tier and add permanent complexity, so each one has to earn its place rather than inherit it from a base.
What people ask before they commit.
Can we keep Airtable for some things?
Often the right answer. Airtable is excellent for internal operational tracking. The customer data belongs in the CRM, and we build the sync across the boundary rather than forcing everything into one tool.
What happens to our formulas?
Each becomes a stored property maintained by workflow, a HubSpot calculated property, or a report column. We go through them individually because the answer depends on whether you need to filter and segment on the value.
How long does it take?
Three to eight weeks. The modelling decisions take the time, not the record volume, and the number of linked tables is the best early predictor.
Do we need HubSpot custom objects?
Sometimes, and they require Enterprise or a specific tier. We tell you before the project starts whether your model needs them, because it changes the licence conversation.
Will our team lose the flexibility they liked?
Some of it, honestly. Airtable lets anyone add a column; HubSpot properties are governed. That governance is usually the reason you are migrating, but it is a change worth naming out loud.
Where people go from here.
Turn the base into a model.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.