โ† All ERP Flashcard Decks

Data Migration Flashcards

7 cards from real ERP practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Data Migration flashcards as text
  1. Which data migration strategy involves running the old and new ERP systems simultaneously for a period to compare outputs?

    Answer: Parallel running

    Parallel running operates both systems concurrently so results can be compared and discrepancies resolved before the legacy system is decommissioned.

  2. What is a 'data freeze' in the context of ERP data migration?

    Answer: Halting updates to source data before cutover

    A data freeze stops changes to the legacy system's data a set time before cutover to ensure a clean, consistent snapshot for migration.

  3. In ERP data migration, what does ETL stand for?

    Answer: Extract, Transform, Load

    ETL (Extract, Transform, Load) is the core process of pulling data from source systems, converting it to the target format, and loading it into the ERP.

  4. Which type of data is typically the MOST complex to migrate into a new ERP system?

    Answer: Open transactional data such as open purchase orders

    Open transactional data like open POs and outstanding invoices requires careful balance verification and is prone to errors if balances don't reconcile at cutover.

  5. What is the primary purpose of a data reconciliation report during ERP migration?

    Answer: Confirming record counts and totals match between source and target

    Reconciliation reports verify that the number of records and financial totals in the new ERP match the legacy system to confirm migration completeness.

  6. During ERP data migration, which stakeholder is typically responsible for signing off on data quality before go-live?

    Answer: Business data owners

    Business data owners are accountable for the accuracy and completeness of their domain's data and must formally accept the migrated data before go-live.

  7. What risk does migrating 'dirty' legacy data into a new ERP system pose?

    Answer: Perpetuating data quality problems in the new system

    Migrating uncleansed data carries existing errors and inconsistencies into the new ERP, undermining the value of the implementation from day one.