Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Data Migration Without Drama: A Practical Sequence - Kemlat Insights
Kemlat2026-10-21T17:03:43+03:00
All insightsاقرأ بالعربية
Enterprise Systems

Data Migration Without Drama: A Practical Sequence

The new system can be perfect and still fail on day one if the data is wrong. A step-by-step sequence for moving data calmly, with trial runs and checks that catch problems early.

24 October 20265 min read
Share
Data Migration Without Drama: A Practical Sequence - Kemlat Insights

It is Saturday night before go-live. The new ERP (enterprise resource planning) system is configured, the team is trained, and the data load has just failed for the third time because some product codes contain spaces and several hundred customers have no tax number. By Sunday morning, people are typing records by hand.

Data migration is usually treated as a technical task at the end of a project. In reality it is a business task that should start near the beginning, and many go-live problems trace back to it.

Decide what to move before deciding how

Before choosing any migration tool, agree which data the new system actually needs. Moving everything feels safe, but it imports old errors, slows the project and clutters the new system with records nobody uses.

Take a building supplies trading company in Amman replacing a fifteen-year-old local accounting package with a modern ERP. A sensible scope might look like this:

DataTypical approachNotes
Active customers and suppliersMigrate, after cleaningDefine “active”, for example any transaction in the last two years
Products and pricesMigrate, after cleaningA good moment to retire obsolete items and standardise units
Open sales and purchase invoicesMigrate as open itemsEach one must match the customer or supplier balance exactly
Stock on handMigrate quantities and values at cutoverUsually based on a physical count close to go-live
General ledgerOpening balances, sometimes monthly totalsAgree with finance and your auditor how much history is needed
Closed transactions from past yearsArchive, do not migrateKeep the old system or an export available read-only for reference and audit

Agreeing this table early prevents months of debate later. It also sets a realistic workload for the cleaning that follows.

Write the agreed scope down and have finance, operations and the project sponsor sign it. Requests to bring across one more year of history tend to appear late in a project, and a signed scope makes it easier to weigh each one on its cost rather than its urgency.

The sequence, step by step

1. Profile the existing data

Extract the data from the old system and look at it honestly. Count records, find blanks in important fields, spot duplicates, and check formats such as phone numbers, tax numbers and units of measure. This takes days, not weeks, and it tells you how much cleaning lies ahead.

2. Map old fields to new ones

For every field in the new system, note where its value comes from, whether it needs transformation, and what to do when it is empty. Old systems often store several things in one field, such as a customer name with the branch appended, which must be split. Business owners should sign off the mapping, not only the technical team.

3. Clean in the source or in a staging file

Decide where cleaning happens. Fixing records in the old system keeps everyone working on the same data, but some changes are impossible there. A staging file, meaning a separate spreadsheet or database where records are corrected before loading, gives more control. Whichever you choose, assign each cleaning task to a named person from the business: sales cleans customers, purchasing cleans suppliers, the warehouse cleans products.

4. Run trial loads

Load the data into a test copy of the new system at least two or three times before go-live. The first trial usually fails in places, which is exactly why you run it. Each run reveals format errors, missing mandatory fields and mapping mistakes while there is still time to fix them calmly.

5. Reconcile every trial

After each load, compare totals between old and new: number of customers, total receivables, total payables, stock quantity and value by warehouse, trial balance by account. Any difference must be explained. Repeated reconciliation is what turns a hopeful migration into a reliable one.

Rule of thumb: do not schedule go-live until a full trial load reconciles to the old system with every remaining difference explained and accepted by finance.

Planning the cutover

Cutover is the short window when the old system stops and the new one starts. It should feel like repeating a rehearsal, not improvising. A typical checklist includes:

  1. Freeze date and time agreed. After this point no new transactions go into the old system, and everyone knows it in advance.
  2. Final transactions posted. Last invoices, receipts and stock movements entered and checked in the old system.
  3. Stock count completed. Physical count finished and variances approved, so opening stock is trustworthy.
  4. Final extract and load. Using the same scripts or templates as the last successful trial, with no last-minute changes.
  5. Reconciliation signed off. Finance and operations confirm the opening position before users start working.
  6. Fallback plan ready. A clear decision point and a way back if something fundamental fails.

Choose the timing carefully. Month-end or year-end cutovers simplify opening balances, but they collide with the busiest period for finance. Many companies in the region also avoid peak seasons such as the weeks before Ramadan or the start of the school year, when order volumes spike.

The first weeks after go-live

Expect a period of small data issues: a customer with the wrong payment terms, a product with the wrong unit, a supplier missing a bank account. Set up a simple log where users report data problems, assign an owner to fix them daily, and track the count going down. Keep the old system available read-only so people can check history without guessing.

This is also the moment to put rules in place that keep the new data clean: mandatory fields, controlled lists, and a clear owner for creating customers and products. Some of these checks can be automated, such as alerts when a record is created without a tax number. Otherwise, within a year the new system can carry the same problems as the old one.

A migration that supports the new system

If your project is already under way, check two things this week: whether the scope table has been agreed and signed, and whether the plan includes at least two full trial loads with reconciliation before go-live. If either is missing, adding it now costs far less than discovering the gap on cutover weekend.

Data architecture and migration are a core part of our Enterprise Systems service. We help you scope, map, clean and reconcile your data, so the new system starts with information your team can trust.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Also related: Intelligent Automation

Explore our services

Related insights

Cleaning Historical Data Before a System Migration - Kemlat Insights
Enterprise Systems

Cleaning Historical Data Before a System Migration

Moving fifteen years of records into a new system just in case is a frequent reason migrations run late. Decide what to bring, clean it properly…

16 Nov 2026 · 5 min read
Mobile Apps for Field Teams: When They Are Worth Building - Kemlat Insights
Enterprise Systems

Mobile Apps for Field Teams: When They Are Worth Building

Paper job sheets sent by WhatsApp make the case for an app feel obvious. Sometimes a custom app is right. Often a simpler option fits the…

15 Nov 2026 · 5 min read
Budgeting for an ERP Project: The Costs People Forget - Kemlat Insights
Enterprise Systems

Budgeting for an ERP Project: The Costs People Forget

ERP budgets often overrun because of costs that were real from the start but never made it into the budget. These are the lines to add…

14 Nov 2026 · 5 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.