Data migration
Objective
This guide describes, in practical terms, how historical data is analyzed, prepared, migrated, validated, and switched over to Unifize. It focuses on scope, responsibilities, accepted file formats, timelines, risks, and acceptance criteria. The goal is a predictable migration with auditable outcomes.
Roles and Responsibilities
Successful migration depends on defined ownership. The roles below are used throughout this guide.
Customer Champion
Leads the customer side of the project. Defines what must be migrated versus archived, confirms continuity requirements, coordinates SMEs, and signs off on scope, validation results, and cutover readiness.
Customer Subject-Matter Experts (SMEs)
Provide business rules (e.g., which suppliers are active, part numbering conventions), prepare source data, and perform business validation during testing.
Unifize Implementation Team
Advises on feasibility and scope, provides templates and mapping guidance, performs scripted imports, configures Unifize processes, supports validation, and manages hypercare after go‑live.
Supported Source States and Typical Timelines
The activities and ranges below assume a named Customer Champion, timely access to source data, and SME availability for validation. Ranges extend if prerequisites are not met.
Paper‑based
Binders, signed forms, scanned PDFs
Scan documents; apply OCR where text is required; upload final controlled documents; re‑enter key master data; decide continuity vs. archive for historical records
8–12 weeks
Excel trackers
NCR/CAPA/audit logs in XLS/XLSX/CSV
Normalize headers; export CSV; scripted imports; upload supporting evidence separately
6–8 weeks
Excel + linked documents
Trackers referencing files in SharePoint/OneDrive/Drive
Map tracker rows to Unifize record types; resolve/repair links; scripted imports; bulk upload disconnected files
8–10 weeks
Legacy/homegrown systems
Access/FileMaker; QMS/PLM/CMMS/DMS; vendor‑provided exports
Obtain CSV/XML/JSON exports; perform schema mapping; transform and run scripted imports
10–14 weeks
Hybrid
Mixture of paper, spreadsheets, and systems
Prioritize master data and live processes; phase migration of historical records by compliance priority
12–16 weeks
*Assumes timely data access, prepared CSVs, and SME participation in validation.
What Gets Migrated (Scope and Rules)
Migration is scoped to ensure regulatory continuity and effective operations in Unifize. Items that do not require continuity should be archived externally and referenced as needed.
Master Data
Scope
Employees, customers, suppliers, products, parts, plants, locations.
Rule
Deduplicate records, deactivate obsolete entries, and standardize codes and naming.
Acceptance
Sample checks pass; code systems and relationships are consistent and documented.
Documents (Controlled Content)
Scope
SOPs, policies, forms, work instructions.
Rule
The historical import contains the final approved version only. Future revisions are created and managed via Unifize document workflows.
Acceptance
Title/ID/owner/effective date are present; the file opens; the content matches the source copy.
Filled-Out Records (Quality Events and Logs)
Scope
NCRs, CAPAs, change controls, inspections, audits, product specifications.
Rule
If continuity required: Import as active records to preserve reporting and audit history.
If continuity is not required: Retain as an external archive; add references in Unifize if needed.
Acceptance
Representative samples reconcile to source counts and key fields; all evidence links open successfully.
Supported File Types and Formatting
Structured data
CSV, XLS, XLSX
Documents
PDF, DOCX, XLSX, PPTX, TXT
Images and evidence
JPG, PNG, TIFF
System exports
XML, JSON (transformation/mapping required)
Scans
PDF/TIFF with OCR where searchable text is needed
CSV/XLSX formatting requirements:
UTF‑8 encoding; single header row; one record per row.
Stable column names; separate columns for codes versus descriptions.
Unique keys/IDs where available; supply lookup tables for code systems.
Provide one file per entity (e.g., Parts.csv, Suppliers.csv) and one per record type.
Using the Unifize API for Data Migration
For teams with technical capability, the Unifize API can be used to automate or supplement the migration process. The API provides endpoints for securely creating, updating, and validating records in your Unifize instance, making it suitable for scenarios where scripted imports or ongoing integrations are required.
When to use the API
Complex migrations where data transformations are easier to script than prepare in flat files
Incremental or phased migrations requiring controlled, repeatable imports
Building integrations with existing systems for live or ongoing data synchronization
Key resources
For most migrations, CSV/XML/JSON exports with scripted imports remain the recommended approach. The API is best suited as a complementary option for specialized use cases.
Switchover Strategies
Switchover timing is chosen after scope and continuity decisions are finalized.
Big-bang
A single switchover after import and validation. Appropriate when the scope is bounded and the data is clean. Risk increases if outstanding cleanup or validation remains.
Phased
Staged migration by process, site, or department. Appropriate for hybrid states and large historical scopes. Requires managing parallel operations during transition.
Unifize recommended practice
Big‑bang for master data and controlled documents; phased migration for historical quality records in compliance priority order.
Standard Migration Workflow (Ownership and Risks)
1. Discovery and scoping
Inventory sources: define in‑scope entities and continuity level; appoint Champion; plan timeline
Customer + Unifize
No Champion; unclear scope; unrealistic dates
2. Extraction
Scan/OCR (paper); export CSV/XLSX; obtain XML/JSON from systems
Customer (Unifize guidance)
Missing access; corrupted exports; IT bottlenecks
3. Cleanup and mapping
Deduplicate; standardize codes; deactivate obsolete entries; map fields to Unifize
Customer (business) + Unifize (technical)
Dirty data; inconsistent naming; unmapped fields
4. Import execution
Manual uploads for simple files; scripted imports for bulk/master data and linked documents
Customer (files) + Unifize (imports)
Invalid formats; missing attachments; transform errors
5. Validation (IQ/OQ/PQ)
Reconcile samples to source; verify workflows operate on migrated data; run PQ with realistic usage
Customer (business) + Unifize (system)
Gaps in checks; overlooked records; misconfigured flows
6. Switchover and go‑live
Apply big‑bang/phased plan; disable legacy write paths; designate Unifize as system of record
Customer + Unifize
Parallel entry; change‑management gaps
7. Hypercare
Triage issues; minor data corrections; reinforce new procedures
Unifize + Customer
Reversion to shadow trackers
Risks and Constraints
Continuity vs. archive: Not all historical records require import. Prioritize compliance‑critical items.
OCR limitations: Expect manual verification for data derived from scanned documents.
Export dependencies: XML/JSON exports often require IT support; plan lead time.
Bandwidth: Cleanup and validation require SME time; this is the most common schedule driver.
Link resolution: Spreadsheet‑to‑file links frequently need remediation prior to import.
Mitigation actions include early scoping, dry‑run samples, documented acceptance criteria, and phased cutover for higher‑risk areas.
Deliverables and Acceptance
Customer inputs: Source extracts and scans, mapping decisions, code lists, and continuity/archival decisions. Unifize outputs: Templates, field mappings, import scripts, migration runbook, validation support, and a hypercare plan.
Acceptance to proceed to go‑live:
Agreed scope is complete and imported.
Switchover checklist executed and legacy write paths disabled or governed.
Champion signs off on readiness.
Appendix: Timeline reference by starting state
Paper-based
8-12 weeks
Excel trackers
6-8 weeks
Excel + linked documents
8-10 weeks
Legacy/homegrown systems
10-14 weeks
Hybrid
12-16 weeks
Last updated