Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Migration - G/L Entries
HannesHolst
Member Posts: 119
Hey there!
After a long time of just reading and using the Search, I want to participate
For my current company, we are doing a migration from Sage200 into NAV2017.
Sage200 is based on a SQL-Database, so we have all the power of SQL-Queries.
As one of the tasks, the financial departments requested to have the G/L-entries migrated.
Ok, so far: I'm able to create a view in SQL, copy it into a RapidStart-Template and import everything into a General Journal (even possible by using the WebClient -
)
But, what is the best practise approach for the last financial year (if we ignore the data processing-capabilities of RapidStart and the time it consumes)?
- Could we go for a full import of G/L-entries for the last financial year?
- Import the final amounts of each month of the last financial year?
- Import only the balance of the end of the financial year?
Additionally, for the current financial year:
- Import all G/L-entries for the current financial year?
As writing this post, the combination of "Import the final amounts of each month of the last financial year" and "Import all G/L-entries for the current financial year" seems to be the best option.
What do you think?
Cheers,
Hannes
After a long time of just reading and using the Search, I want to participate
For my current company, we are doing a migration from Sage200 into NAV2017.
Sage200 is based on a SQL-Database, so we have all the power of SQL-Queries.
As one of the tasks, the financial departments requested to have the G/L-entries migrated.
Ok, so far: I'm able to create a view in SQL, copy it into a RapidStart-Template and import everything into a General Journal (even possible by using the WebClient -
)But, what is the best practise approach for the last financial year (if we ignore the data processing-capabilities of RapidStart and the time it consumes)?
- Could we go for a full import of G/L-entries for the last financial year?
- Import the final amounts of each month of the last financial year?
- Import only the balance of the end of the financial year?
Additionally, for the current financial year:
- Import all G/L-entries for the current financial year?
As writing this post, the combination of "Import the final amounts of each month of the last financial year" and "Import all G/L-entries for the current financial year" seems to be the best option.
What do you think?
Cheers,
Hannes
My blog - https://www.HannesHolst.com/
0
Best Answer
-
Options
tfranzen
Member Posts: 25
Hi Hannes,
as always it depends on the requests of the customer. When the customer is satisfied with the monthly final amounts of the last year and all the entries of the current year your approach will do fine. You should show the alternatives (time and money consumption) to the customer and they'll have to make the decision.
Cheers,
Thomas5
Answers
as always it depends on the requests of the customer. When the customer is satisfied with the monthly final amounts of the last year and all the entries of the current year your approach will do fine. You should show the alternatives (time and money consumption) to the customer and they'll have to make the decision.
Cheers,
Thomas
Thanks for your reply.
It's good to hear that there is no "No Go" in the approach of how to migrate the G/L-Entries.
FYI:
We will go for balances by month for the last two years and for the current year we will import all postings.
Cheers,
Hannes
Andwian