Transfer car wash memberships through a documented plan covering customer terms, provider approvals, payment arrangements, account mapping and wash access. Define billing cutoffs and exception ownership before closing. Reconcile transferred records to the original cohort, then verify permitted service access and actual renewals; an imported member count alone does not prove recurring cash continuity.
- Separate legal transfer, billing migration and service access.
- Obtain provider-specific approval and an agreed transition sequence.
- Reconcile stable account identifiers and material plan terms.
- Verify renewals and settle exceptions after the cutover.
What must continue when a wash changes hands?
Customers need the service and billing treatment promised by their terms, while the buyer needs proof of authorized collections. These duties are related, but importing a member list does not establish that either one has been met.
The buyer hub places transfer within purchase diligence. An agreement may name memberships as an acquired asset. The work can still involve the wash platform, processor, merchant account, customer records and access hardware, so identify each dependency before treating a count as transferable.
The membership churn guide explains ordinary member movement. During transfer, an apparent loss may be a mapping error or delayed bill. A reported active account may also fail to enter the wash, so keep service and payment outcomes distinct.
Define the intended cutover and who is responsible for each layer. Record the seller and buyer entities, systems and service scope. The transfer plan should explain what must continue, what can change and what evidence will show the promised result.
Which approvals and provider instructions are needed?
Ask installed providers for written answers tied to the actual sale and seller and buyer entities. Review customer terms and contracts with advisers, rather than inferring approval from a general product description or salesperson’s comment.
An asset purchase and an ownership change in an existing entity may pose different questions. Platform ownership, merchant underwriting, settlement banks and licenses need their own review. This guide does not establish a universal assignment right or consent rule.
Sonny’s POS specification describes member management and reports. It does not prove target exports or payment transfer. Confirm version, setup and contract scope. Keep acceptance reports with their actual limits.
Stripe’s payment-data import guidance illustrates secure migration and ID mapping, not proof the wash uses Stripe. Follow actual provider instructions and keep card data out of ordinary data rooms. Payment data, member terms and billing schedules need separate checks; one completed step does not prove all are ready.
List each approval, owner and evidence. State the platform, account and processor plan. Its effects on IDs, payment methods, dates and cutover need review.
Which baseline records should be frozen?
Save a dated, access-controlled snapshot of the member population before the agreed cutover. Track later changes so the final file can reconcile to the snapshot, rather than silently treating the first export as the final transferred group.
Include stable account ID, plan, recurring price, discount rights, next billing date, paid-through date and access ID. Keep cancellations, pauses, payment failures and multiple-vehicle arrangements distinct. Confirm report definitions rather than relying on one active-account total.
The profit-and-loss review guide links records to payments and settlements. Access data answers whether service should be available. Bills and payment records answer what was owed or collected; neither dataset replaces the other.
Follow data minimization and access controls in the FTC information-security guidance. Give authorized reviewers only what they need. Use the approved process to retain evidence. Have responsible parties review retention and disposal; do not leave broad sensitive-data copies in shared folders after their purpose ends.
How should accounts be mapped and reconciled?
Map each original account to a destination record or a stated unresolved category. Compare terms and service rights as well as row counts, because a matching count can hide a wrong price, date or vehicle-access mapping.
In a fictional baseline of 1,000 records, a provider maps 970, flags 20 for review and finds 10 possible duplicates. The counts reconcile records, not 970 paying customers. They do not permit deleting the other 30 without review.
| Disposition | Records | Evidence still needed |
|---|---|---|
| Mapped destination records | 970 | Terms, billing dates, access and renewal verification |
| Review exceptions | 20 | Named owner, reason and approved resolution |
| Possible source duplicates | 10 | Identity review and documented reconciliation |
Keep the mapping file and its history. Vehicle changes, family plans or shared emails can complicate matching, so email alone is not a unique member ID. Confirm supported identifiers and explain merges or exclusions, keeping each open record visible until its identity, terms and approved disposition are established by the responsible team.
How are billing cutoffs and cash ownership defined?
Document who collects each bill and how cash, refunds and open items are allocated under signed terms. The operating schedule must implement that allocation, rather than create a new rule based only on which account receives cash.
Separate service period, invoice date, payment date and bank settlement date. A preclosing charge can settle later, and an old refund can occur still later. Reconcile those dates instead of assigning every item solely by the day cash reaches the bank.
Name who can change settings, verify the old process stops where appropriate and authorize the new one. Review controls against duplicate or missed charges with providers. Do not run both systems against the same bill just to see which succeeds.
Keep disputes in an exception register with source evidence and the assigned party. If signed terms leave a category open, get adviser-reviewed clarification. The register tracks agreed duties; a spreadsheet entry should not invent refund, collection or dispute ownership that the parties have not resolved.
What should the cutover acceptance checklist include?
Check each layer through the provider-approved process and record its result. A broad statement that the software works does not show that approvals, terms, billing and access all passed, so preserve the limits of each check.
- Confirm required approvals, account ownership and permitted settlement arrangements.
- Reconcile the frozen population and changes since the snapshot.
- Verify representative plan prices, discounts, dates and vehicle-access mappings.
- Confirm the agreed old/new billing sequence and controls against duplicate charges.
- Assign unresolved exceptions, monitoring responsibility and approved contingency actions.
Use methods approved by providers and authorized parties. Do not create live charges or appointments solely for diligence. State what was tested, what could only be reviewed from setup and what awaits the first actual scheduled renewal.
Keep failed checks and untested layers visible with an owner and next action. A sample proves only what it covers, so explain which plans or access arrangements need further review. Acceptance should follow the agreed scope and evidence, with approved contingency actions ready for unresolved items rather than a silent assumption that every record works.
How should continuity be monitored after closing?
Follow the transferred group through scheduled billing and access events using its original mapping. Keep new signups and later operating changes separate from transfer results, so growth does not hide a problem in the acquired group.
The first 90 days guide gives wider handover context. Assign daily exception review during the agreed initial period and retain outcomes. Check access denials, missing terms, unexpected charges and failures without assuming each issue is a cancellation.
Trace successful payments through refunds, fees and settlements. Show which accounts have reached a renewal date and which have not yet had that chance. An import percentage on closing day cannot replace later collection evidence.
Prepare staff to route issues to the assigned person using approved explanations. Keep communications and resolutions. This record helps distinguish short-lived transition errors from lasting losses and supports any adjustment process the parties agreed, without treating an access fix as proof that an unpaid renewal was collected.
What evidence supports treating the transfer as complete?
Completion needs evidence across the promised scope: approvals, reconciled records, retained terms, permitted billing and working access. State limits and open items instead of declaring success from one report whose acceptance may cover only an import.
Keep the transfer file available to the authorized buyer team. Name an owner for each unresolved item. Report later renewals and settlements against the original group. This separates demonstrated recurring continuity from accounts whose collection or service rights still need resolution.
Retain dated results and the approved response for each exception. A corrected ID may solve mapping while leaving billing or access unresolved. Show the remaining layer, responsible person and evidence needed before closing the item, rather than removing it because some work finished.
The final report should connect findings to the buyer’s recurring-revenue case. Keep verified results apart from estimates of future retention. A complete transition file explains both the work delivered and the limits of its proof, without promising every transferred customer will stay indefinitely.