Migrate your Function 365 data

Patient records are the primary object in any medical CRM including Function 365. We migrate core demographics, contact details, and NHS Numbers as a structured 10-digit identifier field. Custom patient properties are mapped individually during the scoping call.

Appointment history is date-sequenced and migrated with patient association preserved. Recurring appointment patterns are detected and re-created at the destination where the target CRM supports recurrence rules.

Clinical encounters represent discrete visit records with provider, date, and notes. Where encounters span multiple date ranges or contain nested subsections, we flatten or re-associate them to match the destination schema.

Prescription records contain medication name, dosage, frequency, and prescriber linkage. We map these to the destination's medication or prescription object and flag any custom prescription-related fields that require manual mapping.

Treatment plans may store structured phases alongside free-text clinical goals. We preserve the structured plan phases and migrate the goal text as a long-text field, noting the association back to the patient record.

Insurance claim records include payer, policy reference, claim status, and submitted amounts. We map claim status values explicitly to avoid mis-match errors at the destination when status terminology differs between platforms.

Document attachments associated with patient records are downloaded and re-uploaded to the destination CRM with original filenames and patient associations preserved. File-size limits at the destination are enforced during the chunking pass.

Custom fields added to any of the above objects are listed during scoping, and field-level value mapping is applied where source and destination property types differ, such as multi-select lists or date-only fields.