Migrate your Practice by Numbers data

Patient records hold demographics, contact info, insurance carrier assignments, and lifetime value scores. We preserve all standard fields and map custom patient properties to the destination schema, flagging any orphaned insurance references that cannot resolve in the target system.

Provider records include name, credentials, taxonomy, and scheduling preferences. These map cleanly between systems with straightforward Owner or Provider field assignments.

Appointment history includes date, provider, procedure codes, status, and patient link. We map procedure codes to destination code sets and preserve status histories across the migration window.

Treatment plans contain procedure sequences, case values, and acceptance statuses. We export these from Practice IQ exports and reconstruct them in the destination, noting any plan that references a procedure code not present in the target system.

Claims records include carrier, status, billed amount, and paid amount. We preserve the full claim lifecycle and flag any claims in 'in-progress' status that may need re-submission after cutover.

Payment records include amount, method, patient link, and claim association. We map payment method codes to destination equivalents and preserve the claim-to-payment linkage throughout the migration.

Practice IQ supports user-defined patient fields. We discover these during scoping, extract their values, and map them to equivalent custom fields in the destination or store them as structured notes if no matching field exists.

Communication history tracks SMS, email, and voice interactions per patient. We export the full log from Practice by Numbers and reconstruct it in the destination as activity or engagement records.

Uploaded documents attached to patient records require file extraction from PbN storage and re-upload to the destination with preserved parent-record links. We handle filename deconfliction and MIME-type verification.

PbN's AI-powered call tracking stores call logs, transcriptions, and attribution data. We export these records and map them to the destination's activity or call log object, preserving call duration and outcome data.

Survey responses and scores are exported as flat records linked to patients and appointment dates. We map survey question and answer pairs to equivalent survey fields in the destination system.

Custom campaign records include audience definitions, message templates, and performance metrics. We export campaign configurations and re-create them in the destination, preserving audience segment logic where possible.