Best Practice for Automated Data Migration from SeaTable to Dataverse

(0) Share

Report

Posted on by CE-28060833-0 Microsoft Employee

Hi, I have a customer who is currently using SeaTable and is planning to migrate their data to Microsoft Dataverse

They are facing some challenges during the import process, particularly with:

Choice/Select fields

Relationships between tables

Lookup fields

Data type mapping

From my understanding, the recommended approach is to first create the schema in Dataverse (tables, columns, choice fields, relationships, etc.) and then import the data. However, this introduces additional effort because the data model must be recreated manually before the migration.

I would like to understand the best practice and most automated approach for migrating data from SeaTable to Dataverse.

Some specific questions:

Is there a recommended pattern for migrating SeaTable data into Dataverse?

Would you recommend using Power Automate, Dataflows, custom connectors, or another approach?

How do you handle Choice fields and relationships during migration?

Is there a way to automatically generate or synchronize the Dataverse schema from SeaTable metadata?

Any guidance, lessons learned, or real-world experiences would be greatly appreciated.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

11manish 3,849 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

For most migration projects, the most robust approach is to recreate the schema in Dataverse first, then migrate the data using an ETL process such as Power Query Dataflows or a custom integration that leverages the SeaTable API and Dataverse Web API. Although schema recreation requires some initial effort, it results in a cleaner data model, better performance, and more reliable handling of relationships and Choice fields.
If the migration is expected to be repeated or involves many SeaTable bases, investing in a metadata-driven migration utility that reads the SeaTable schema and automatically provisions Dataverse tables can greatly reduce manual effort and improve consistency.

Was this reply helpful? Yes No
Suggested answer

Haque 4,004 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @CE-28060833-0,

Unfortunately, no direct to tool to migrate data from SeaTable to Dataverse!

Migrating data from SeaTable to Microsoft Dataverse involves careful planning, especially around schema creation, data type mapping, and preserving relationships. Here’s a detailed guide addressing your questions and best practices:

Approach-1: Yes, manual effort is needed - to keep the data integrity we need to create schema in Dataverse (Table, columns, choice fields, relationships) while you plan to migrate.

Approach-2: We can export data from SeaTable in a structured format like CSV, Excel or via API. Transform data to match Datavesre schema specially from choice fields,lookup fields (mapping all complex data) etc.

Approach-3: Use Power Automate - good for small to medium data volumes and automating incremental data syncs but less suited for large bulk migrations.

Approch-4: SeaTable offers and official Python SDK. We can write script to download data from SeaTable and batch upload it into Dataverse via Dataverse Web API or .NET SDK.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
CE-28060833-0 Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks everyone for your responses. However, most of the fields are Choice fields, and there are many tables involved. Wouldn't it be quite a substantial effort to require the customer to manually recreate all the Choice fields and schema elements in Dataverse before performing the migration?

Was this reply helpful? Yes No
Suggested answer

Haque 4,004 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @CE-28060833-0,

You brought up tedious part! Complex datatypes (Choice and Lookup) and relationsional tables invite hiccups for migration. Knowlingly, I/we don't see any tool that could help things in lightning time!

Based on the situation it is impractical for large and complex schemas with complex data types fields. Only scripting can help us in this reagard or building a custom connectors might be the best practice to reduce time and effort.

To me, when I migrated SharePoint on-premise to SharePoint online using ShareGate - that data migrated very quickly but lots of factors had to consider to plan and post staging stuff.

We had a resolved thread where I answered and was accepted - let's see if it helps.

Plus this article is powerful to follow a solid migration steps.

Finally, as there is export option in see table and import data from Excel - only thing we need is creating schema, ordering sequnce and import into dataverse.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No