Leaving Airtable? Bring your bases to Artavolo, checked record by record. See how
Move from Microsoft Access

From Microsoft Access to Artavolo, step by step

Export from Microsoft Access, bring the files in, and see what came over before anyone switches. It is read in your browser, and nothing in Microsoft Access changes.

  1. Export from Microsoft Access

    You get: The database file itself: .mdb or .accdb.

    1. Close Access, and copy the .mdb or .accdb file (from the shared drive, say).
    2. If it has a database password, have it ready: the import asks for it.
    3. Linked tables live in other files: bring those files too.
  2. Bring the files in

    1. In Artavolo, open Import on the home page and choose Access (opens it for you).
    2. Pick the database file. If it has a password, type it.
    3. The tables and their fields are shown with their types, and what was found (links, lookups, groups). Untick a table to leave it out, and make the base.
  3. Read the report

    It lists the tables and records made, the formulas and lookups checked against Microsoft Access’s own results record by record, and what is different, so nothing is dropped without a word. Keep Microsoft Access until the team works here.

What comes over

Your data, typed and linked

  • Every table, from Access 97 to 2019
  • Relationships as links between tables
  • AutoNumber, Currency, Yes/No, Date/Time, Memo and Hyperlink fields typed as such
  • Attachment fields with their files
What you rebuild

Named in the report, every one

  • Forms (as interfaces and form views)
  • Reports (as dashboards)
  • Queries (as views), macros and VBA (as automations): the report lists every one by name

Rather we did it? We move a base or a whole workspace for a fixed price, rebuild what the export leaves out, and check it with you. Ask for a quote.

Questions

Moving from Microsoft Access

Yes: Access 97, 2000, 2003, 2007, 2010 and later, .mdb and .accdb, with database passwords. It is read in your browser.

Yes: each relationship becomes a link from the child table to the parent's record (Orders.CustomerID becomes a Customer link), and records whose parent is gone are counted in the report.

They are listed by name in the report, to rebuild as interfaces, form views and dashboards. In a migration package we rebuild them for you.