How to switch from one POS system to another at a gas station.

Why this is the riskiest move you can make

The POS is the central nervous system of your gas station. It runs the register, controls the fuel pumps, processes credit cards, tracks inventory, and feeds your accounting system. When the POS is down, you cannot sell anything in any meaningful way.

Most POS migrations at independent gas stations take 6 to 12 weeks of preparation plus a cutover weekend where you operate manually or on reduced capacity. The total cost (equipment, training, integration, lost productivity) usually equals or exceeds the software cost itself.

Reasons to switch POS systems

Migration is so disruptive that most operators only do it when they have to. Common triggers:

• Old POS is dying. The current system is on legacy hardware that cannot be repaired or supported. The vendor has discontinued the product line. Service calls have become slow or impossible.
• Brand requirement. You signed a new brand agreement (Shell, BP, Chevron, etc.) and the brand requires a specific POS or set of POSes.
• Major capability gap. You need features the current POS cannot deliver and cannot be added (loyalty integration, fleet card support, modern card chip technology, etc.).
• Vendor out of business or sold.Your POS vendor was acquired and the new owner is discontinuing your product line. Migration is forced; the only question is when.
• Cost reduction. Rare but real. If your current POS has high monthly fees or per- terminal license costs and a cheaper option offers equivalent capability, the math may favor switching.

Reasons that are NOT worth a POS migration:

• Frustration with one feature you can work around.
• A salesperson's claim that the new POS is "30 percent better."
• One bad weekend with the current vendor's support.
• Marketing pitches for "modern" or "AI-powered" capability you do not actually need.

Step by step: the 12-week POS migration

Week 1 to 2: Decision and procurement

Pick the new POS. Sign the contract. Review the equipment list and order anything needed. For most gas station POS systems (Verifone Commander, Gilbarco Passport, NCR Voyix, Toshiba) equipment is custom and has 2 to 4 week lead times.

Week 3 to 4: Data export and item file work

Export everything from the old POS:

• Item file (every SKU with cost, retail, category, tax).
• Customer database (if you have loyalty).
• Transaction archive (last 90 days minimum).
• Vendor list.
• Promotional and discount configurations.

Clean the data before importing into the new system. Most operators discover their item file has dead SKUs, wrong tax flags, and incorrect category mappings. Migration is the time to fix these.

Week 5 to 6: Equipment installation and configuration

New equipment is installed in the back office (or wherever it lives at your station). Initial configuration: tax rates, store info, employee accounts, payment processor connection, fuel-pump connection, integration with any external systems (accounting, loyalty, fleet cards).

Week 7: Item file import

Cleaned item file imports into the new POS. Test scan 20 random SKUs to verify each scans correctly with the right price, tax, and category. This is where configuration errors surface.

Week 8: Integration testing

Test the credit card processor connection (run $1 test transactions). Test the fuel-pump connection (authorize and complete a fuel transaction at each pump). Test the accounting export (run a daily close and verify the journal lands in QuickBooks). Test the loyalty connection if applicable.

Week 9 to 10: Clerk training

Every clerk who will use the new POS needs hands-on training. The new system is different from the old one. Common error patterns at the new system: clerks ringing items at wrong prices because of muscle memory, void procedures that look different, age- verification prompts that work differently.

Week 11: Parallel operation day

Run both systems in parallel for one full day. Sales rung on the new POS; the old POS still active for any fallback. At end of day, reconcile totals between the two systems and your bank deposit. Catches almost all remaining configuration errors.

Week 12: Cutover

Pick a Sunday or low-traffic weekday morning. Cut all transactions over to the new POS. Keep the old POS available as a fallback for 30 days but stop using it for live transactions.

What can go wrong

• Item file with wrong tax flags.The most common migration error. SKUs that should be tax-exempt (food stamps eligible, prescription) end up taxable, or vice versa. State sales tax gets wrong for weeks before anyone notices.
• Fuel pump integration failure.Pumps fail to authorize or fail to complete sales. Customers cannot pay at pump and have to come inside. Volume drops 20 to 40 percent until resolved.
• Credit card processor connection failure. Card sales fail. You operate on cash and check for hours or days. Loss of card sales at a gas station is severe.
• Clerk training gap. Clerks make wrong-price rings or void mistakes for weeks after cutover. Variance spikes. Correct with retraining and patience.
• Accounting export breakage.Daily close stops feeding QuickBooks. Bookkeeper has to hand-key everything until the integration is fixed.
• Hidden contract terms with old vendor. Service contracts, software licenses, and equipment leases may have early termination fees. Audit before cutover.

How to pick the cutover weekend

What to keep from the old POS

Do not discard the old POS the day after cutover. Keep it powered and accessible for 30 to 60 days because:

• Refunds for old transactions may need the original transaction history.
• Tax filings for the prior period draw from old POS data.
• Chargeback disputes require the old transaction record.
• Year-end reconciliation may need access to old data.

After 60 days, archive the data (export to CSV, save to cloud storage) and you can retire the equipment. Keep the data archive for at least 7 years for tax and audit purposes.