Migration checklist

This checklist is a complete roadmap to migrate data and operations from a legacy system to Centriu (or to the new stack) without chaos. It covers a step-by-step approach by area, data cleansing, and a communication plan.

The 3 layers of migration:

People: Who decides, who executes, who is impacted.
Data: What moves, what stays, how it is cleaned and tested.
Communication: How to align expectations before, during, and after.

Phase 0Prerequisites

Decision madeBased on the Stack Map and Decision Framework.

Sponsor definedSomeone in leadership who backs the project.

Minimum team assembledProject owner + IT + Department representatives.

Clear objectives and scopeWhich systems are included and what success means.

Phase 1Step by step by area

Leadership / Business

Validate business objectives.
Approve change windows (avoid peak periods).
Define success criteria.

Sales / CX

List dependent daily activities.
Map critical fields (pipeline, status).
Validate templates in Centriu.

Support / Service

Map queues and SLAs.
Define history migration (open tickets?).
Validate chat/WhatsApp integrations.

IT / Operations

Map export (CSV/API).
Validate technical limits and create a sandbox.
Plan new integrations.

Phase 2Data cleansing

Golden rule: "Garbage in, garbage out." Don't migrate bad data.

Define data scopeWhich entities? Full history or only active ones? What goes to the archive?

Standardize fieldsLowercase emails, phone numbers with area codes, standardized cities.

DeduplicationMerge duplicate customers by email, phone, or ID document.

LGPD and SecurityRemove unnecessary sensitive data before migrating.

Phase 3Technical Planning

Field mapping (Source/Target)
A table relating each field of the legacy system to the new one.
Strategy: Big Bang or Waves?
All at once or in parts? Set freeze (cutover) dates.
Pilot Test and Validation
Run with a real sample and ask a key user to validate ("can I do my work?").
Rollback Plan
A full backup beforehand and a criterion to abort if a critical error occurs.

Phase 4Communication Plan

Suggested timeline

T-30 days: Official announcement (internal).
T-15 days: Scope details and cutoff dates.
T-7 days: Practical guide "What your day-to-day will look like".
D-Day: Instructions for immediate use.
T+7/30 days: Follow-up and adjustments.

What to communicate

For Leadership: Benefits, risks, and milestones.
For Operations: Changes to the routine, cutoff dates, and where to ask for help.
For Customers: Only if there is a direct impact.

Phases 5 and 6: Execution and Post-migration

D-Day: Run scripts, monitor logs, and validate with the teams. Legacy system set to "read-only".

Post (Intensive support): A help desk for questions during the first 2 weeks. Fine-tuning of rules.

Closure: Confirm that no one is still using the legacy system, export the final history, and terminate contracts.

Need help with your migration?

Our team of specialists can support your switchover to ensure it goes safely.