How to Plan Your First 30 Days of a Bravo Switch
Use these milestones to build a store-specific plan for data, configuration, training, validation, launch, and issue handling. They are planning stages, not a universal delivery timeline.
A four-stage planning framework
Your actual schedule depends on the source system, record types, data condition and volume, locations, hardware, integrations, approvals, and staff availability. Ask Bravo to put the milestones, owners, included services, unresolved questions, and launch criteria for your store in writing.
Scope the switch
A short call with the Bravo team to map three things:
- Your data: source system, record types, date ranges, attachments, export access, quality, and required retention
- Your operating setup: locations, users, rules, hardware, payments, integrations, and workflows that must be tested
- Your responsibilities: who exports, cleans, maps, validates, configures, trains, approves, and escalates each item
Prepare and test the data
Ask Bravo to confirm which records can be converted from your system, which cannot, the required export format, and how exceptions will be handled. Your team should review counts, balances, samples, attachments, and required history before approving converted data.
Configure, train, and rehearse
Document who configures rules, permissions, hardware, payments, reports, and integrations. Confirm which training resources and support are included in your quote. Then run representative transactions, corrections, record lookups, reports, and failure cases before launch approval.
Approve the launch plan
Set a launch date only after critical data and workflows pass the agreed tests. Record the final export and cutover steps, operating procedure during the transition, support contacts, escalation path, rollback decision, and owner for every unresolved item.
Validate and close open items
Reconcile key balances and counts, sample records, verify integrations and reports, and track each issue to an owner and resolution. Confirm the support channels, hours, response expectations, and any fees that apply to your written agreement.
Questions stores ask about the first 30 days
Do I have to close my store during the switch?
Do not assume that no closure or interruption is required. Ask for a written operating and cutover plan based on your source system, final export process, hardware, payments, integrations, and vendor access. Document how the store will operate during every transition step.
What happens to my old records?
Inventory the exact records and date ranges you must retain or access. Ask Bravo to confirm which can be converted from your current system, which remain outside Bravo, who validates them, and how exceptions and old-system access will be handled.
How long does training actually take?
Training time depends on roles, workflows, experience, locations, and the training resources included in your agreement. Define role-based readiness tests and require each employee to practice representative workflows before launch.
Who runs the migration?
Ask Bravo to name the project and escalation contacts for your agreement. Then assign store-side owners for data export, data approval, configuration, hardware, payments, training, compliance review, testing, launch approval, and issue resolution.
What support do I get after go live?
Support can vary by agreement. Ask your quote to identify channels, hours, response expectations, launch coverage, escalation, self-service resources, and any separate charges. Confirm how open implementation issues transition into ongoing support.
See what your 30 days would look like
A short call should identify your data, operating setup, responsibilities, commercial scope, timing factors, validation plan, and unanswered questions.
Schedule a DemoRelated reading: how data conversion works · the one pager for your business partner · switching from PawnMaster · switching from AIM