US - Florida - Jacksonville

Expand all | Collapse all

combining two companies in Great Plains

  • 1.  combining two companies in Great Plains

    Posted May 24, 2019 11:46 AM
    We have three companies in Great Plains and are looking at combining two of the companies. Has anyone combined two companies in Great Plains? If someone has experience with combine two Great Plains companies, what was your experience with combining the two companies? Any information about this subject would be helpful.

    Heather Emrick
    Naval Aviation Museum Foundation

  • 2.  RE: combining two companies in Great Plains

    Posted May 28, 2019 11:14 AM
    ​We did this last year.  It wasn't necessarily difficult, but it took us a lot of planning and preparation.  Mostly because we had to combine them mid-year, but effective 1/1 (we are calendar year organization).

    1. If you can, wait until the beginning of your fiscal year.  This may limit the transaction history to combine and is a good, clean cut-off.
    2. We combined Company2 to Company1 rather than creating a new company and bringing both Company1 and Company2 into it.  For us, Company1 was already the primary entity and the majority of transactions were processed in it. 
      • Note we kept the Company1 database intact - we just created a new DB and restored the Company1 DB to it
      • We also cleaned up history of Company1 prior to backing up the DB for the new DB restore
    3. For historical reporting, you may want to bring in the balances only to each respective month and year you will report.  As you can only post to one historical year, this may mean "reverse closing" some of your years.
    4. If you use the bank recon module in Dynamics, you'll need to bring in the outstanding items at the end of the last reconciled period.  Which may include the detailed AP, AR transactions, etc.
    5. We exported all necessary transactions (invoices, journal entries, deposits, etc) from Company2 and created an import file for each transaction type.  Then used Scribe to import the transactions to Company1.  We considered audit trail, batch ids, document #s, etc. to ensure there was no duplication.  We only imported the 1/1/2018-merge date transactions.  Prior year transactions were imported only if there was a related transaction in 2018 (e.g. void check, cleared item, etc.)
    6. There was some manual work/entry involved, but not significant. We were offline a few days while we executed and verified all data.

    A good SQL person, may be able to combine tables rather than the export/import method we took.  Those are the highlights.  And plan, plan, plan is key.

    I hope it is helpful.


    Selena Breedlove
    SVP of Finance/Controller
    US Assure Inc
    Jacksonville FL

If you've found this thread useful, dive deeper into User Group community content by role