Migrate to Odoo from SAP Business One, Microsoft Dynamics or QuickBooks
TDS (Talents Digital Services), an Odoo Gold Partner, plans and delivers ERP migrations to Odoo for companies in Egypt and Saudi Arabia. Published TDS case studies include moves from SAP Business One, Microsoft Dynamics GP, Microsoft Dynamics and QuickBooks.
Request a migration assessment (Egypt) Request a migration assessment (Saudi Arabia)
Migrations in published TDS case studies
Each engagement had its own scope. The case studies describe the business context, solution scope and delivery milestones.
ECOTEL
SAP Business One to Odoo · Telecom and ICT infrastructure
ECOTEL moved from SAP Business One to the TDS ICT solution built on Odoo, designed around project profitability, commercial discipline and connected operations.
Read the ECOTEL case studySeaharvest
Microsoft Dynamics GP to Odoo · Oil and gas services, Egypt
TDS migrated Seaharvest, a member of the Afaq Holding Group, from Microsoft Dynamics GP to a single Odoo platform.
Read the Seaharvest case studyBMA (Al Basateen Village Compound)
Microsoft Dynamics to Odoo · Facility management
BMA, which provides facility management services for Al Basateen Village Compound, moved from Microsoft Dynamics to Odoo to work on one streamlined system.
Read the BMA case studyVenus International Free Zone
QuickBooks to Odoo · Grain trading and marine services
Venus moved from QuickBooks to Odoo, covering sales, freight tracking, CRM and accounting.
Read the Venus case studyHow TDS runs a migration to Odoo
1. Discovery and process mapping
Review the current system, reports, customizations, integrations and the processes each department depends on.
2. Solution design and data mapping
Map the chart of accounts, items, bills of materials, projects and open balances to Odoo, and agree how much history to move.
3. Configuration and agreed extensions
Configure Odoo, including Saudi ZATCA or Egyptian Tax Authority e-invoicing where relevant, and build only the extensions agreed in scope.
4. Trial migrations and reconciliation
Load data into a test database and reconcile balances, stock and open documents against the legacy system before go-live.
5. User acceptance and training
Test representative transactions with your team and train users on the processes they will run in Odoo.
6. Cut-over and support
Freeze the legacy system at an agreed date, load final balances, go live and support the team through the first closing periods.
Frequently asked questions
Which systems can TDS migrate to Odoo?
Published TDS case studies cover migrations from SAP Business One, Microsoft Dynamics GP, Microsoft Dynamics and QuickBooks. Other legacy and in-house systems are assessed during discovery.
How long does a migration take?
It depends on the modules in scope, data volume, the number of companies and integrations. TDS agrees a phased plan and timeline after discovery.
Can historical data be moved?
Master data and open balances are normally migrated. How much transaction history moves, and in what form, is agreed during solution design.
Can we keep using the old system during the project?
Yes. The legacy system normally stays in use until the agreed cut-over date, while trial migrations are loaded and reconciled in a test database.
Do you support e-invoicing in Saudi Arabia and Egypt after migration?
Yes. Saudi deployments use Odoo’s ZATCA e-invoicing localization, and Egyptian deployments cover Egyptian Tax Authority e-invoicing.