Help

The Community will be undergoing maintenance from Friday February 21 - Friday, February 28 and will be "read only" during this time. To learn more, check out our Announcements blog post.

Re: How to move a table to a new base and preserve linked records?

408 0
cancel
Showing results for 
Search instead for 
Did you mean: 
Peter_Galletta
5 - Automation Enthusiast
5 - Automation Enthusiast

I have a base with several tables and lots of linked records between the tables. It has become necessary for various reasons to move one of those tables to its own base.

Is there a way to move that table to its own base while preserving all the linked records to the other original base?  I'm struggling to find a good example or guidance how to approach that.

thanks!

4 Replies 4
Mike_AutomaticN
10 - Mercury
10 - Mercury

Hey @Peter_Galletta,

In orden to achieve that you’ll want to explore Airtable’s Sync feature

Mike, Consultant @ Automatic Nation

ATSolutionist
6 - Interface Innovator
6 - Interface Innovator

Hi Peter 

Not sure what type of plan you currently have with Airtable but I can try to give you some guidance for Business or Enterprise level. 

I would first sync the data into a new base, then turn the sync feature off once I've confirmed all my data has migrated over. 

Once you've chosen the base, table & view you want to sync, it'll ask you if you wish to sync any linked fields that appear in the view (ensure that synced settings are turned on in at least one view in each of the tables) 

ATSolutionist_0-1737179438836.png

 

You'll need to have synced views turned on for at least one view in each table that you wish to migrate over. 

Once you have your new data imported and the sync is complete - duplicate the 'synced' linked record box - the new duplicate will be native to this new base 

ATSolutionist_1-1737180114196.png

then update your synced configurations so it stop syncing 

ATSolutionist_2-1737180184498.png

once you've turned it off the new duplicate stays active as a linked record to the synced data source 

ATSolutionist_3-1737180255095.png

I've done some syncs without the full features of the business/enterprise plan and it can still be done - you'd just want to be mindful of your 'Primary Field'  (ensuring its unique, set to formula to ensure when you go to re-link it it'll pick up on the information) 

This may or may not be the solution to your question,  but happy to continue troubleshooting if you are able to provide a little bit more context! 

 

P.S: Ensure the view you are syncing has all the fields and records unhidden that you want to bring over (no hidden fields / filters in some cases)  before deleting the table in your original base

 

 

Katelyn
info@consultasolutionist.com
matthew_b
7 - App Architect
7 - App Architect

Hi Peter,

One option is to use Whalesync's Airtable <> Airtable sync which supports linked records. Steps would be:

1. Set up your new Airtable base with your two tables
2. Whalesync from original Airtable base to new Airtable base

https://www.whalesync.com/connect/airtable-airtable

Is there a way to move that table to its own base while preserving all the linked records to the other original base?

Hmm, let's call your current base Base 1 and the new base Base 2.  In Base 1, Table A is linked to Table B, and now you want to move Table A to Base 2, and want changes made in Base 2 to show up in Base 1, Table B, is that right?

If so, and you're alright with there still being a copy of Table A in Base 1, then you could look into the Sync feature like Mike mentioned.  If you're on a Business or above plan you're pretty much sorted; changes you make in Base 2 will show up in Base 1 automatically, so you don't have to do anything else

If you're on a Teams plan, then you'll need to find another way to propagate your change from Base 2 to Base 1, be it via a script or third party tool like Zapier or Make or something

If you don't want Table A to show up in Base 1 at all, this is also possible and you'd use the abovementioned script or third party tool option

Could you talk more about the business logic here and what the workflows would be?