Practical guide
Planning a controlled move between systems
Define what a successful move must preserve
A migration is successful when the practice can perform its required work with the right information after cutover. A count of imported records is useful evidence, but it does not establish that staff can find the history, appointments, stock or open work they need. Begin with the operating requirements and work backward to the data and configuration.
Name the records that must be available on the first day, the information that can remain in a controlled historical archive and the work that needs a separate transition plan. Have the people who use each category help define acceptance. Clinical, front-desk, optical and billing requirements are related but not identical.
Platform setup takes 3–4 calendar days for a single location and no more than 7 calendar days for multiple locations. Confirm the start date and prerequisites with Jelo during your workflow review. This guide explains the preparation behind that statement. It is not a promise that every source system or dataset can be moved within the same elapsed time.
Assign owners before setting the final date
Identify the practice decision-maker, the person coordinating exports, the reviewers for each data category and the staff responsible for external account setup. One person may hold several responsibilities, but each task should have an owner and a clear next action.
Create a short issue register with the requirement, source, status, owner and evidence needed to close it. Keep unresolved mandatory items visible during scheduling discussions. A proposed date should not cause an unanswered export or payer dependency to disappear from the plan.
Agree on how decisions will be recorded and where the team will find the current plan. Avoid competing versions in private notes. A concise shared record of scope and acceptance is more useful than a long project document that does not identify who can resolve the next blocker.
Confirm access to the current system's exports
Ask the current vendor or responsible account owner what information can be exported and how the practice obtains it. Identify the available formats, attachments, time range and any practical conditions that affect the request. Do not assume that a visible screen can be reproduced in a usable export.
Confirm who is authorized to request and receive the data. Keep credentials and patient records out of general planning documents. Use the approved transfer and storage process agreed for the migration, and identify the person who verifies that the expected files or records arrived.
If the export scope is incomplete or unclear, obtain a sample before setting a final cutover. The destination team needs evidence of what the source actually provides. A verbal assurance that data can be moved does not resolve questions about missing fields, file relationships or historical material.
Inventory data by how staff use it
Separate demographics, clinical history, prescriptions, documents, future appointments, inventory and financial work in the planning inventory. Add other categories your practice requires rather than assuming this list is exhaustive. For each category, record the source and the staff role that can verify it.
Describe the intended use after migration. A scanned historical document may remain an attachment, while a future appointment needs to support scheduling work. These categories can have different acceptance criteria even when both are successfully transferred as files or records.
Keep unknown destinations or formats explicit. If information will remain in an archive or previous system, identify how authorized staff will access it and who owns that arrangement. The goal is continuity of the required work, not a claim that every piece of history becomes a native editable field.
Review identity and duplicate risks
Patient identity needs attention when information comes from several exports or systems. Similar names, changed contact details and duplicate source records can complicate matching. Agree on the information used for review and the person responsible for uncertain cases.
Do not automatically merge records because a name appears similar. The migration process should preserve uncertainty for an authorized reviewer rather than creating an unsupported conclusion. Keep the evidence and decision within the approved environment, with enough context for the next reviewer to understand the result.
Include duplicate and changed-detail examples in the sample validation. Staff should be able to identify the intended person after the move and know what to do if a possible duplicate remains. This is an acceptance requirement for the operating team, not merely a technical check that an import completed.
Validate clinical context with clinicians
Have clinicians review representative records for the history and documents they need in daily work. Include more than a newly created chart with little information. Choose examples that reflect the practice's range of record complexity, while keeping patient data within the approved migration environment.
Check how historical information is presented and whether staff understand its source. Structured values, free text and attachments may have different behavior in the destination. Record any limitation that affects search, review or reuse so the clinical team does not discover it unexpectedly during an encounter.
The clinician should determine whether the migrated context is usable for the intended workflow. This does not certify clinical completeness of the original records or alter their content. The EHR guide provides additional acceptance questions for history, templates, review and downstream handoffs.
Treat attachments as their own validation task
Documents and images can carry important context even when the structured record looks correct. Confirm which attachments are in scope, how they remain associated with the intended record and how authorized staff open them. File presence alone does not establish that the relationship or content is usable.
Choose a sample across relevant document types and ages. Ask the staff member who normally uses them to find and open the files through the intended workflow. Record missing, unreadable or unexpectedly associated material for investigation rather than assuming a successful transfer count resolves every issue.
If some historical material remains outside the destination, document the access route and responsible owner. Staff should understand where to look and what limitations apply. Do not invent a retention period or assume that the old vendor will preserve access indefinitely; confirm the practice's actual arrangement.
Check future appointments separately
Future appointments require their own review because they drive patient-facing work immediately after cutover. Confirm the date, time, appointment type, provider, office and patient context for a representative sample. Include rescheduled visits and different appointment types where relevant.
Identify how changes made after the initial extraction will be handled. A schedule can change while migration preparation continues, so the team needs an agreed method for ensuring that the final operating view reflects the current plan. Record who coordinates this step and how staff confirm it.
Review patient-facing instructions and reminders alongside the schedule. An accurate appointment record can still cause confusion if an old message points to a different office or time. The scheduling guide helps connect migrated appointments with intake, communication and the day's changes.
Reconcile opening inventory deliberately
Inventory migration should distinguish the catalog from office-specific quantities. Confirm product and variant identity, then establish the physical and recorded stock position for each office in scope. Similar frames or duplicate identifiers deserve particular attention during review.
Choose a cutoff and explain how receipts, sales, returns and transfers near that point will be handled. A quantity exported at one moment and counted at another may differ for an ordinary reason. Preserve the source and physical observations before approving any correction.
Use the inventory counting guide to structure the review. Opening stock should be a position the optical team can explain, not simply the result of loading a file. Outstanding purchases and lab work require their own review because they are not the same as physical items on hand.
Plan open orders and external lab work
An optical order may be active across the cutover date. Identify the orders that still need staff attention and the external references required to follow them. Decide where the team will work each item after launch and how it will understand what has already happened.
A retail record, payment and lab production status are distinct. Moving or recreating one does not establish that the external lab job has changed. Confirm the transition process before staff send duplicate work or assume that an old reference is no longer needed.
Jelo's VisionWeb integration is available, but the relevant location account, linked labs and catalogs need setup and validation. Use the VisionWeb guide to review those prerequisites. Keep existing open jobs in the transition plan even if new orders will use a different workflow after cutover.
Separate historical finances from open billing work
The practice may need access to historical payments while also continuing unresolved claims or balances. Identify these categories separately and decide where each will be reviewed after the move. A patient record import does not prove that the billing team has everything needed to continue an open item.
Review representative financial examples with the responsible person. Confirm the source references, recorded amounts and outstanding questions. If work remains in the previous system, document the access and responsibility rather than implying that every financial record has moved into a single new workflow.
Jelo's insurance and payer work is handled through Jelo AI at 10% of insurance reimbursements received. Confirm the account and payer prerequisites for the intended service. The billing guide and AI biller setup page help identify the operating handoff without promising universal coverage or automatic resolution of legacy claims.
Configure the destination before the full rehearsal
Data readiness and configuration readiness are different tasks. Review appointment types, exam templates, intake forms, office information, staff access and the external accounts your practice intends to use. Assign each configuration an owner and a visible acceptance step.
Avoid waiting until the final rehearsal to decide basic operating rules. Staff can evaluate a workflow more usefully when the intended office context, form and template are already available. If a configuration remains uncertain, identify it as such rather than presenting a temporary example as the final setup.
Use fictional records to test configuration where real data is unnecessary. The software evaluation worksheet can preserve what was demonstrated and which questions remain. Keep these product and setup tests separate from the validation of the actual migrated records.
Validate external accounts as dependencies
List the payment, lab, messaging, payer and other accounts required for the first day. Identify who owns each account, what setup is needed and how the practice will verify the intended workflow. A platform feature can be available while a particular account is not ready.
Jelo's confirmed provider relationships include Stripe, VisionWeb, Sinch and Jelo AI. Other devices or services should remain explicit requirements until supported scope is confirmed. Do not assume that every existing connection transfers automatically with the patient data.
Use the integration guide for a register of prerequisites and exception tests. Include the point at which an action would affect a live external account, and use controlled examples for demonstrations. The final readiness review should distinguish demonstrated configuration from a planned setup task.
Train staff with their actual roles
Give each role a small set of tasks it must complete after launch. The front desk should book and change a fictional visit, clinicians should review and document an encounter, optical staff should follow an order and billing staff should identify unresolved work. Include the handoffs between them.
Test ordinary staff access rather than relying solely on an administrator. For multiple locations, have employees confirm the working office and the scope of the records they can review. Include an absence-coverage scenario so the practice is not dependent on the person who attended every setup call.
Customer accounts of quick adoption can be encouraging context, but they are not a guaranteed training schedule. Care Optica and Sharp Eye Care describe easy learning in their own experiences. Your readiness decision should depend on the tasks your staff can demonstrate and the questions they still need answered.
Create a cutover readiness record
Before choosing the final operating date, review the mandatory categories: data scope, sample validation, configuration, external accounts, staff training and historical access. Record the evidence for each and identify any unresolved item. An unanswered requirement should have an owner and a specific next step.
Decide which issues prevent launch and which have an approved interim process. The practice's decision-maker should understand the practical consequence of each accepted limitation. Document where the work will occur and who will review it, rather than leaving a workaround as an informal promise.
A readiness record does not need to be long. It needs to make the decision reviewable by the people who will operate the practice. The final date should follow that evidence, especially when exports, payer setup or staff availability change during preparation.
Plan the first operating period
Give staff a clear way to report a problem after launch, including the record or workflow affected and the next owner. Keep patient details in the approved support or practice environment. A general planning document can track the issue category and status without copying the clinical record.
Review the most important handoffs early: appointment preparation, clinical access, optical order continuity and unresolved financial work. Compare an observed issue with the accepted migration scope to determine whether it is a data discrepancy, configuration question, training need or new requirement.
Resolve those causes separately. Repeating training will not repair a missing file, while changing data will not clarify an undefined responsibility. A small, prioritized issue list helps the practice stabilize the workflow and keeps ordinary questions from obscuring a mandatory problem.
Keep an exit and data-access plan
Jelo confirms data exports for your own analytics, free cancellation and help moving to another system if needed. If your practice requires a particular export format, delivery time or transition service, ask for that detail before relying on it. The broad commitment does not specify every contractual or technical circumstance.
Maintain an understanding of which accounts and historical records belong to the practice and how authorized staff access them. Review the arrangement when the operating model changes, such as adding an office or replacing an external service. Continuity planning is useful even when the practice expects to stay with the platform.
Jelo also confirms HIPAA compliance, BAAs, an encrypted database and automatic daily backups. Request any additional recovery or technical details your organization needs through the security review. Do not infer a guaranteed recovery time from the existence of a daily backup.
Use the checklist as a shared decision tool
A checklist is most useful when each item has evidence and an owner. Mark an export available only when its scope is understood, mark validation complete only after the responsible staff review it, and mark a connection ready only when the relevant account requirements are confirmed.
Keep the current version accessible to the people coordinating the move. Record changes to scope or timing so staff do not act on an earlier assumption. The checklist should help the team make a decision, not create the appearance that every migration follows an identical sequence.
Bring your current system, data categories and timing constraints to a demo or migration discussion with Joel or Loreli. The next useful step is a concrete plan for exports, validation, configuration and training, with unanswered requirements documented before the practice commits to cutover.