Try it for Free

Moving from Best Practice Allied to Power Diary

We can import your data from BP Allied into your Power Diary account! 

  • Practices often move from BP Allied to Power Diary and as such, we have invested in developing a streamlined process for importing BP Allied Data, which allows our team to prepare your data for import in a more efficient and timeous manner. 
  • We want to make your move from BP Allied as seamless and pain-free as possible. Once you have made the decision to move over to Power Diary, we are able to assist with importing data into your Power Diary account as a once-off complimentary service. There are no charges associated with the import. 
  • If your migration to Power Diary is time sensitive, please contact us to discuss the option of booking your import in with our Team, to ensure that it gets the priority that it needs.

This article covers:


Additional information:

Please click on these links to access additional important/relevant information with regards to your data import, and getting ready to switch over to using Power Diary.

Important: Please read through the above articles as they contain information generic to all data imports/migrations, but not included in this BP Allied-specific article.  If you have any questions that aren't answered in any of these articles, we encourage you to contact us. 

We can import the following BP Allied data:

based on previous BP Allied imports conducted by our Team, we can import:

  • Clients
  • Appointments
  • Client insurance (Medicare, NDIS, DVA, Health Fund numbers)
  • Third-Party Billers
  • Referrers
  • Referrals
  • Services (items)
  • Client Communication (Contacts)
  • Client Tasks
  • Session Notes (ClientMedications, ClientMedicalConditions, ClientSupplements, ClientHistory and Consultations)
  • Client documents:  see requirements in our "Importing your Data FAQ" helpdesk article - click here

* If there is any other data that is of particular importance to you, to have imported, and has not been mentioned in the above list, please let us know, and our Team can check your data to try to locate that data and ascertain if it is viable for import.

What can't be imported from BP Allied?

The following data isn't able to be imported:

  • General ledgers (transactions including invoices and payments)

Exporting your data from BP Allied

You will need to contact BP Allied directly to request for them to generate an export of your database including your client's documents. 

  • You can contact their support team using the following email address: support@bpsoftware.net
  • You will need to ask for them to extract and supply you with your SQL Server database files and client documents and that the client documents are exported into folders that use the Client GUID as the name rather than the client's name. 
  • BP Allied will then email you with links that download these files. 
  • Please forward the email containing these links to us at support@powerdiary.com along with the password for unlocking the files so that our team can access the data.

** Please ensure that you request the data format as specified above.  The streamlined procedure for extracting, cleansing and importing your data, that we have invested in creating, requires the above data format.  BP Allied may offer to extract and supply CSV files, but we cannot work with these.  


Important Notes

  • Data format: The preference from our side is that your export is done to a.BAK database backup file - as this is what our streamlining is being based on / built to accommodate. We can still perform your import if you send us.CSV files, but your import will probably happen more expediently and efficiently if we get a.BAK file.
  • Password: BP Allied data is typically locked by a password, please provide this in the comment when uploading the data or via email to support@powerdiary.com, so that we can access the data promptly upon receipt.
  • BP Allied is a resource-intensive import in which the data requires a LOT of manipulation. The data that is imported is not always an accurate reflection due to the way it is stored in Best Practice Allied versus the way we store data in Power Diary.
  • Clients:
    • Not all clients have a primary practitioner. These clients will be assigned a primary practitioner (typically the account holders practitioner or first practitioner created in the account unless otherwise requested).
    • Any fields that are not compatible with a specific field in the client profile are added to the Additional Comments section of the profile.
    • Not all clients have a first name listed, we will default the first name to "blank".
    • Multiple contact details (phones, emails, addresses) are provided. Power Diary supports one set of information in each of these fields, therefore we will filter the data to list one value and move the rest into the client's additional comments (on the client profile page).
  • Appointments:
    • No location is provided, this will be set to the default location for the account.
    • Appointments with no duration will be set to 15 minutes to enable import.
  • Financial Data: Invoices, payments and other transaction types are stored in one table (in General Ledger) which means we have found many issues with this, and importing this does not result in an accurate migration of your financial data. Given the complexity of mapping this dataset, as a general rule, we don’t import this invoice/payment data from BP Allied.   We recommend retaining a copy of this financial data for reference purposes, and "starting with a clean slate" when you switch over to Power Diary.
  • In addition to what has been discussed above, we do recommend that you read all generic "Important notes" relevant to importing your data, as documented here as there are relevant learnings and important information relevant to your data import that you need to be aware of. 


If you have any questions, please contact us at support@powerdiary.com

Don't have a Power Diary account? No problem! Get started with a 14-day free trial

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.