What happens after I send a switching request?
A person follows up to discuss your priorities and possible next steps. Submitting the request does not upload or move data, connect another system, or begin a switch.
Define what matters, preserve the exports you control, and decide how you would judge a future setup. If you request help, a person follows up about next steps. The request itself changes nothing.
Required scope
Available exports
Acceptance checks
Open questions
Request boundary
Conversation only
No upload · no old-account access · no transfer · no execution
EstheticSense does not offer an automated import or connector through this request. There is no promised transfer, preview, execution path, cutover date, or access to the system you use today.
Four decisions
A switch starts as an owner decision: scope, source preservation, acceptance criteria, then a request for conversation.
Scope
Separate the workflows your team would require first from the work that can wait and the records that should remain in an archive. This is your decision, not a preset package.
Preserve
Sign in to the current provider yourself and download the exports it already makes available. Keep untouched originals in storage your business controls.
Accept
Decide what your team would need to inspect before accepting any future setup. A written standard makes the decision reviewable instead of emotional.
Request
Tell us which system you use and what matters most. A person follows up about next steps. The request does not move data, grant access, or start a switch.
Owner-controlled export checklist
Your current provider defines what it can export. Keep those originals under your control and document what each file represents.
Before any file is shared
What the request does
Tell us the system you use, the workflows you care about, and the questions you need answered. A person follows up about possible next steps.
What it does not do
A person follows up to discuss your priorities and possible next steps. Submitting the request does not upload or move data, connect another system, or begin a switch.
No. A planning request does not grant account access. You remain responsible for signing in, downloading any available exports, and deciding whether anything may be shared later.
Bring the name of your current system, the workflows that matter most, your constraints, and a list of the exports your provider already offers. Keep the original files under your control.
This page makes no execution or timing promise. The follow-up is for planning: understanding scope, identifying unanswered questions, and deciding whether another conversation is useful.
No. The request does not schedule a cutover, operate either system, or promise a parallel-booking period. Any future operating decision remains with the owner.
Request a planning conversation about your current system and priorities. A person follows up; nothing changes automatically.