Skip to Content
Raion Hub

Move a field between databases

A field belongs to the whole workspace, so moving it to another database means adding it there and then taking it off this one; no value is lost.

  • Time: 2 min
  • Who: Field Configuration permission
  • Plan: All plans
  1. Database Configuration
  2. Customers
  3. Add field or section
  4. Add to…
  5. Leads

Steps

See which databases show the field

In Database Configuration, click Library, the chip at the far left; each field’s row names every database that shows it.

Budget (RM) shows in Leads and Customers. Not in any view means no database shows the field

The Library and a database's chip: the two places a field lives

The Library chip is the whole workspace’s field registry, as one flat list. The screen describes it as: Every field in the workspace — one shared definition. Click a field to edit or delete it. Add or remove a field from a specific view inside that view.

Each row shows the field’s name, a type pill, and chips naming the databases that currently show it. Extra databases collapse into a +N chip you can hover to read the rest. A field that no database shows reads Not in any view in italics: it still exists and still holds its data. A dashed New field button sits at the bottom of the list.

A database’s chip shows the other view of the same fields: only the ones that database holds, in the order its table uses them. That is where you add a field to a database or take it off.

Open the database the field should move to

Click that database’s chip in the row along the top, for example Customers.

Switching chips keeps anything you have not saved yet

Add the field there

Click Add field or section, find the field, and pick a group in its Add to… dropdown.

This database already shows every field here, so the popup reads Every field is already in this view

What Add to… offers, and why a field is not in the list

Add to… lists Pinned first, then every section of this database by name. The field drops into that group and its row flashes. Pinned drops off the list once this database has no pinned slots left.

The popup only lists fields this database does not show yet. If the field is not there, this database already has it: skip to the next step. If your search matches nothing the popup says No matching fields.

Clicking a row’s name instead of its dropdown opens that field’s editor rather than adding it.

Take it off the first database

Click the first database’s chip, open the field, click Remove at the bottom left and choose Remove from Leads.

The label names the database you are in. Its sublabel reads Keeps the field + its data

Choose Remove from Leads, not Delete permanently. Delete permanently erases every value in that field, on every contact, in every database.

Keeping the field in both databases instead

Skip this step. The field then shows in both databases, and a value typed in one is the same value in the other, because it is the same field on the same contact.

Save

Click Save changes in the footer; the toast Database config saved confirms both changes at once.

What the contacts see afterwards

Every contact keeps its value. The field now shows on the record card in the database you moved it to, in the section you picked, and no longer in the first one. Whether it is also a table column is a separate switch, the eye on its row: see Choose and pin your table columns.

If something goes wrong

What happensWhyWhat to do
There is no Add field or section buttonYou do not have the Field Configuration permission, and the button is hiddenAsk a Workspace Owner for it in Settings → Roles
The field is not in the Add field or section listThis database already shows itNothing to add. Go on to take it off the first database
The Remove menu offers only Delete permanentlyYou are on the Library chip, which has no single database to remove a field fromClick the database’s own chip first
Name has no way to remove itName is the record’s identity and can never be removed from a databaseNothing to fix. Every database keeps Name
The field moved, but it is not a column in the new database’s tableBeing in a database and being a column in its table are two different thingsTurn its eye on: see Choose and pin your table columns
You chose Delete permanently by mistake and confirmed Delete “Budget” permanently?The field and every value in it are gone from every databaseIt cannot be undone. Create the field again and re-enter or import the values

Next

move field, move a field, move field to another database, move field between databases, share field between databases, copy field to another database, field in two databases, remove field from database, field library

Didn't find it on this page? Email us and the reply starts from the page you were on.

Email support