Import Existing Data into Grayrock
Intro
Moving to new software should not always mean starting again from an empty account.
Grayrock Money and Grayrock Trading Journal are designed for different types of information, so each product provides import workflows appropriate to the data it manages.
Start With the Product You’re Moving Into
Before importing anything, identify the destination.
Grayrock Money works with financial information such as accounts, transactions and categories.
Grayrock Trading Journal works with trading history, trade records and related performance data.
Moving Financial Data into Grayrock Money
Grayrock Money supports compatible CSV and XLSX data imports.
The guided import process can help map supported information such as accounts, transactions, categories and other compatible fields before records are added to the workspace.
Different source applications can structure financial data differently, so reviewing the mapping and normalized information is an important part of migration.
Moving Trading History into Grayrock Trading Journal
Grayrock Trading Journal provides several routes for bringing existing trading history into the journal.
These include recognized historical imports from:
MT4
MT5
cTrader
and supported:
CSV
XLSX
HTML
Compatible custom structures can also use Raw Data Mapping where available.
Internal link: Explore Trade Import & Migration →
Historical Import vs Automatic Sync
Historical import and automatic synchronization solve different problems.
Historical Import brings existing trading records into Grayrock.
Grayrock Sync keeps supported MT4 and MT5 completed trades synchronized while MetaTrader and the connector are running.
Internal link: Discover Grayrock Sync →
Review Before You Commit
Imported data should be reviewed rather than accepted blindly.
Check account assignments, dates, transaction or trade values and other mapped information before relying on imported records for analysis.
Keep Your Original Export
Even after a successful migration, retain the original source file.
Keeping the original export provides an independent reference and makes it easier to review or repeat a migration if necessary.
