Forum Discussion

Darian's avatar
Darian
Qrew Trainee
1 month ago
Solved

Data Migration

Since QuickBase is making new RecordID how do i go about migrating into the RecordID used by QuickBase instead of relying on PersonID and OrderID/PersonID of the old database where the exports are coming from? 

I have some ideas that i can export the main customer table after inporting into QB and get the RecordID there and then future exports can have the RecordID added to them before importing.

Can I override the default RecordID or something like that?

What is the best way to go about importing from another database?

Export From:
Table (client) - PersonID
Table (orders) - PersonID one to many

Import to QuickBase:
Table (Client) - receives a new Record ID made by QuickBase.
Table (Orders) - receives a new RecordID made by QuickBase relationship joined to RecordID in client as one to many

Relationships
  • MarkShnier__You's avatar
    MarkShnier__You
    1 month ago

    If you have a unique field in the parent record which is marked as being unique, then there is a recent feature in the last year or two, which makes it highly convenient to import child records. When you include that key field in the import for the children it will automatically link those children to the correct parent in Quickbase, even if the Key field in the Parent is still [Record ID#]. That means that you don't need to mess around with VLOOKUP in Excel anymore.

6 Replies

  • Denin's avatar
    Denin
    Qrew Captain
    1 month ago

    You can set a different field to act as the key in Quickbase. But what I normally do is:

    1. Create the parent table and import the parent data so Quickbase assigns Record IDs.
    2. Export the parent table from Quickbase as a CSV.
    3. Create the child table (schema only, don’t import data yet).
    4. Create the relationship between the parent and child tables.
    5. In Excel, add a “Related Parent” column to your child dataset. Use VLOOKUP (or XLOOKUP) to match your original key to the parent CSV and pull in the correct Record ID.
    6. Import the child data into Quickbase. The “Related Parent” column will automatically link each child record to the correct parent.
    • Darian's avatar
      Darian
      Qrew Trainee
      1 month ago

      That's kind of what I thought i would have to do.  I will create a new table in the SQLServer with the RecordID for when I need to export data into QuickBase.  I didn't know if there was another way or not.

      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend
        1 month ago

        If you have a unique field in the parent record which is marked as being unique, then there is a recent feature in the last year or two, which makes it highly convenient to import child records. When you include that key field in the import for the children it will automatically link those children to the correct parent in Quickbase, even if the Key field in the Parent is still [Record ID#]. That means that you don't need to mess around with VLOOKUP in Excel anymore.