Dear Sterling25 and Mark,
I have some experience in doing this sort of thing. It is a bigger job than you might think.
When I migrated from another portfolio management package to Fund Manager in 2014, I had to move security, transaction, and pricing data. I could export it as .csv files, but I had to write a fair amount of python code to massage it so I could use FM's generic import.
The biggest work was on transactions--about 400 lines of code mostly mapping the transaction codes from old system to new. But also: dealing with situations where one system wanted one transaction, the other two; massaging date and currency formats; dealing with quantities on fixed income; etc., etc., etc.
Here's the code to handle just one type of transaction (there were 15 or so in total) from the source system.
- Code: Select all
def processDecreaseBasis():
FM.TRAN = 'DIST_T'
FM.ANUM = str(-PM.principal)
FM.BNUM = '0'
FM.CNUM = '0'
writeFM()
FM.TRAN = 'DIST_R'
FM.ANUM = str(PM.principal)
writeFM()
Because I was moving about 25 years of transactions, I could be confident that my code covered all needed transaction types. And I reconciled one system against the other (200 more lines of code).
I worry that if you try to do this for what we hope to be a short time, each day might bring a new transaction type. And I worry that you won't have any automatic way to reconcile.
Let's hope that Schwab gets this taken care of soon! Do we have an ETA?
Best,
David