ivy-interactive/ivy-framework/ivy-convert-airtable

# Airtable to Ivy Conversion Plan
 
**Base ID:** [Base ID]
 
## Create Database
 
**Connection Name:** MyCompanyBase
**Namespace:** MyCompanyBase.Connections.MyCompanyBase
 
The base contains the following tables that should be converted to tables in a database:
 
### Table:Customers
 
**Airtable Table:** Customers
**Airtable Table ID:** tblXXXXXXXXXXXXXX
**Columns:**
-name: Name
  type: string
  nullable: false
  airtableType: singleLineText
  normalization: Trim(Value)
-name: Email
  type: string
  nullable: true
  airtableType: email
  normalization: Lowercase(Trim(Value))
-name: Status
  type: Enum
  nullable: false
  values: Active, Inactive, Pending
  airtableType: singleSelect
  normalization: <None>
-name: Tags
  type: string[]
  nullable: true
  airtableType: multipleSelects
  normalization: <None>
-name: AccountManager
  type: ForeignKey(Users)
  nullable: true
  airtableType: linkedRecord
  linkedTable: Users
  normalization: <None>
-...
 
### Table:Orders
 
**Airtable Table:** Orders
**Airtable Table ID:** tblYYYYYYYYYYYYYY
**Columns:**
-name: OrderNumber
  type: string
  nullable: false
  airtableType: number/formula
  normalization: <None>
-name: Customer
  type: ForeignKey(Customers)
  nullable: false
  airtableType: linkedRecord
  linkedTable: Customers
  normalization: <None>
-name: OrderDate
  type: DateTime
  nullable: false
  airtableType: date
  normalization: <None>
-name: Total
  type: decimal
  nullable: false
  airtableType: currency
  normalization: <None>
-name: Attachments
  type: string[]
  nullable: true
  airtableType: multipleAttachments
  normalization: Store URLs or download to blob storage
-...
 
## Apps
 
For each app, assign a **Type:**
-`CRUD` -- When the app is backed by a database table containing entity records that users would create, edit, and delete (e.g. contacts, orders, activities, deals). CRUD apps should include: DataTable with Add button in header, Sheet/Dialog for create/edit forms with validation, delete via row action with confirmation dialog.
-`Dashboard` -- For summary, analytics, or reporting views.
-`Ad-hoc` -- For utility or custom apps that don't fit the above categories.
 
Default to `CRUD` for any app backed by a database table with entity data. Only use read-only views when the user explicitly requests it or the data is reference/lookup data.
 
### App:Customers
 
**File:** /Apps/CustomersApp.cs
**Icon:** User
**Table:** Customers
**Type:** CRUD
**Description:**
Full CRUD management for customer records: DataTable with Add button, Sheet for create/edit forms with validation, delete via row action with confirmation. Include filters for Status and search by Name/Email.
 
Airtable Views to consider:
-"All Customers" (default view)
-"Active Only" (filtered by Status = Active)
-"Recently Added" (sorted by Created Time desc)
 
### App:Orders
 
**File:** /Apps/OrdersApp.cs
**Icon:** ShoppingCart
**Table:** Orders
**Type:** CRUD
**Description:**
Full CRUD management for order records: DataTable with Add button, Sheet for create/edit forms with validation, delete via row action with confirmation. Include Customer lookup/selector, date pickers, and currency formatting.
 
Airtable Views to consider:
-"All Orders" (default view)
-"Pending Orders" (filtered by Status)
-"By Customer" (grouped by Customer)
 
### App:Dashboard
 
**File:** /Apps/DashboardApp.cs
**Icon:** Dashboard
**Type:** Dashboard
**Description:**
Overview dashboard showing key metrics: total customers, active customers, total orders, revenue charts. Use BarChart, LineChart, and Stat widgets.
 
## Migration Notes
 
-**Attachments**: Airtable attachment URLs are temporary. Use the `export` command to download attachments locally before migration, or implement a migration script to upload them to blob storage.
-**Linked Records**: Airtable's linkedRecord fields should become foreign keys. Ensure referential integrity is maintained.
-**Formula Fields**: Airtable formulas should be evaluated and either converted to computed properties in C# or stored as static values during migration.
-**Rollup/Lookup Fields**: Convert to SQL views, computed properties, or aggregate queries.
-**Collaborator Fields**: Map to User table foreign keys if implementing user management.
 
## Other Notes
 
-Preserve view configurations (filters, sorts, groupings) as default UI states
-Consider implementing view presets that match Airtable views
-Migrate attachment files using `ivy-inspector-airtable export` command
-Test data migration with a subset before full migration