This is a fork of dreautall's python script to import a Bluecoins database into a Firefly III instance. I ran into some issues with split transactions in my database export, but removing the offending lines seems to have solved it, use at your own risk.
- Set up a config file (see example in
config.example.py) - Make an export in Bluecoins, put the resulting
bluecoins.fydbfile into the folderbluecoins-data. - If you used attachments, put the
Picturesfolder (e.g. from a Google Drive export, or locally on your phone fromInternal Storage/Bluecoins/) also insidebluecoins-data. - Run
convert.py, check the output.
- Use this on an new (empty) Firefly III instance, or with a backup at hand. It might mess stuff up.
- Set up all needed currencies first inside Firefly III, transactions with unknown currency will throw an error when trying to import them.
- It's best to set up rules inside Firefly III first to modify the transactions according to your needs.
- This is also the way to go to assign actual source/destination accounts (instead of
(Cash)).
- This is also the way to go to assign actual source/destination accounts (instead of
- The initial bank statements are not imported. You can set them manually in Firefly III after the import for each account.
- Firefly III has some limitations that Bluecoins has not:
- Split transaction always needs to have the same source account.
- A split transaction needs to be the same type throughout (i.e. cannot be split between Deposit & Withdrawal).
- The Transaction Fees feature of Bluecoins not feasible in Firefly III. Instead, a separate Withdrawal is created, with a link to the original transaction.