web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Historcial data migration

(7) ShareShare
ReportReport
Posted on by 84
We need to do the data migration for historical data for 1/3 year, so how to proceed with data migration. Should transaction level data be migrated? If not, then what should be migrated in historical data and how same should be migrated? And if only opening balances are to be migrated, then how same should be done?
 
What are the best practices for data migration? My client has to do data migration from Sage-300 to Business Central. 
 
Thankyou for help in advance!
I have the same question (1)
  • Suggested answer
    OussamaSabbouh Profile Picture
    12,878 Super User 2026 Season 1 on at
    Hello,

    Best practice is not to migrate full historical transactions. Instead, migrate master data, opening balances, and open AR/AP documents as of a cutover date. Post opening balances using G/L, Customer/Vendor, Item, and FA journals, then reconcile to Sage. Keep Sage as read-only for history/audit. This approach is lower risk, faster, and aligns with standard BC implementations.
     
    Regards,
    Oussama Sabbouh
  • Suggested answer
    Sumit Singh Profile Picture
    11,757 Super User 2026 Season 1 on at
    Hi, 
     
    As per my opinion, do not migrate all historical transactions unless legally required. Keep full history in Sage for reference and migrate only what Business Central needs for day‑one operations.
    What to migrate:
    • Masters & Setup: Chart of Accounts, posting setup, dimensions, customers, vendors, items, banks.
    • Operational Data: Open AR/AP invoices, inventory on-hand, fixed assets with book values, bank balances.
    • Financial Opening Balances: Post opening balances via General Journal with a balancing account

     
  • Suggested answer
    Khushbu Rajvi. Profile Picture
    22,128 Super User 2026 Season 1 on at
  • Suggested answer
    TAHER_El_Mehdi Profile Picture
    836 on at

    I’ve already managed a full data migration project from Sage 100 to Dynamics 365 Business Central (Cloud), so I can share some concrete best practices that helped ensure a smooth and clean transition.

    Here are the most important best practices for migrating from Sage → Business Central:

    ✅ 1. Clean and prepare data before migration

    Remove duplicates, close old documents, fix negative inventory, and standardize master data. Migration quality depends heavily on the quality of the source data.

    ✅ 2. Use staging files (Excel or Power Query) for mapping

    Prepare clear mapping sheets for:


    • Customers
    • Vendors
    • Items
    • Posting groups
    • Chart of Accounts
      This avoids mismatches and makes validation easier.

    •  

    ✅ 3. Migrate only what you need

    We usually avoid migrating full transaction history.
    Historical transactions should only be loaded into a sandbox/environment to check and verify, not into the production database.

    ✅ 4. Focus on opening balances + open entries

    This ensures continuity without polluting the new system with old transactions.

    ✅ 5. Run at least two mock migrations

    This helps confirm the data structure, fix issues early, and shorten the final go‑live migration window.

    ✅ 6. Freeze the old system before the final load

    This avoids new entries being created in Sage during the final migration.

     

    🔎 Regarding historical data

    Historical data is usually imported only into a test environment so the client can verify and consult old records.

    In production, the recommended approach is:


    • Migrate masters + opening balances + open entries

    • Keep full historical data in an archive or Power BI for consultation


    •  
     

    This is the approach that works best with Business Central and aligns with Microsoft recommendations.

  • Suggested answer
    Valentin Castravet Profile Picture
    32,157 Super User 2026 Season 1 on at
    Most common migrations transfer opening balances. If you want to bring historical data then yes you'll need to bring over all transactions. 
     
  • Suggested answer
    YUN ZHU Profile Picture
    99,084 Super User 2026 Season 1 on at
    Because posted data cannot be directly imported into BC, you need to import the pre-posting data first, and then post them from BC.
    For example, if you want to import Posted Sales Invoices, you need to import Sales Orders/Invoices first, then post them, and you also need to verify the Opening Balance. This is quite time-consuming.
    PS: Dynamics 365 Business Central: How to use Configuration Package to post documents (Sales Order, Purchase Order, Transfer Order, General Journal, etc.)
     
    Thanks.
    ZHU
  • Suggested answer
    RockwithNav Profile Picture
    8,947 Super User 2026 Season 1 on at
    It will be a like a fresh migration, so you need to load all the Masters first from spreadsheet.
    Once this is done you need to configure the system and start loading the balances manually.
    2 3 year GL Balance.
    AP AR Balance. 
    Bank Balance.
    Open SO.
    Open PO.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,946 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,177 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 555 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans