Kingdee K/3 Cloud to Cloud Galaxy Checklist

0%

0 of 37 items complete

11 critical items still open - these are the highest-risk gaps.

Download checklist:

Scope and decision

Record the exact K/3 Cloud release, patch level and deployment model (on-premise or hosted) in productionCRITICALConfirm the upgrade path and licence terms to Cloud Galaxy with Kingdee or your partner in writingCRITICALDecide in-place upgrade versus new-environment migration with a data loadList all legal entities, ledgers and organizations in scope for wave oneDefine what is out of scope, such as archived years or retired product linesName a business owner for finance, supply chain, production and cost accountingAgree success criteria: period close time, order cycle, inventory accuracy

Data and master data

Run duplicate and obsolete checks on materials, customers and suppliers before moving anythingCRITICALFreeze or reconcile open sales orders, purchase orders and production orders before cutoverReconcile inventory by warehouse and batch to the general ledger inventory accountCRITICALReconcile accounts receivable and payable sub-ledgers to control accountsMap BOMs, routings and work centers and confirm version and effectivity rulesDecide how many closed accounting periods of history move overMap units of measure and unit conversion groups, including multi-unit materialsKeep a field-level mapping sheet signed off by the data owner

Customizations and integrations

Inventory all custom forms, plug-ins, workflows and reports built on K/3 CloudCRITICALClassify each customization: replaced by standard, rebuilt, or retiredCheck custom code against the Cloud Galaxy development framework and API versionsList every interface: MES, WMS, OA, banks, tax systems, EDI and e-commerceCRITICALRe-test authentication, service accounts and API endpoints for each interfaceReview custom reports and BI extracts for changed table or field namesConfirm third-party add-ons are supported on Cloud Galaxy

Finance, tax and compliance

Confirm voucher templates, account sets and accounting policies still follow the entity's accounting standardsCRITICALTest fapiao issuance and the link to the tax invoicing platform end to endCRITICALVerify VAT rate and tax classification code mapping on materials and servicesCheck period-end processes: depreciation, cost calculation, currency revaluationPreserve electronic accounting archives and audit trails from the old systemAlign with your auditors on how the migration will be evidencedCheck bank interface and payment file formats still work

Testing, cutover and support

Run at least two full mock migrations with timings and reconciliation reportsCRITICALExecute user acceptance tests per business process with signed test scriptsTest security: roles, data permissions by organization, segregation of dutiesRun performance tests on month-end cost calculation and MRP volumesPrepare a written cutover runbook with owners, times and a rollback decision pointCRITICALSchedule cutover after a period close, not in the middle of a periodTrain key users and super users before the second mock, not after go-livePlan hypercare for at least the first full period closeCRITICAL

Tick every item you have completed. Items marked critical are the ones that most often stop a Kingdee cutover or force a rollback. Confirm exact upgrade paths and tooling with Kingdee or your implementation partner, because they depend on your K/3 Cloud release and deployment model.

Optional expert review of your Kingdee migration plan

Send us your exported checklist and we will point out gaps in data, custom code and cutover planning.

Optional. The tool and every export work without this. No spam.

How to use this checklist

Work through the groups in order, starting with scope and decision, because the answers shape every later group. Tick an item only when there is evidence: a signed reconciliation, a test result or a written confirmation from Kingdee. The checklist marks critical items; if any critical item is open two weeks before cutover, escalate it. Export the list to PDF for steering committee reviews or to Excel to assign owners and dates next to each line.

Assign one owner per item, not per group
Attach evidence to critical items
Re-run the checklist after each mock migration
Keep the exported file with your project records

Why Kingdee migrations go wrong

Most problems come from three places. First, master data that was never cleaned, so duplicates and inactive items travel into the new system. Second, custom development: plug-ins and workflows written years ago that nobody documented, which may not run against the newer framework. Third, integrations with MES, banks and tax platforms that are tested late. A migration is also a chance to retire customizations that standard Cloud Galaxy functions now cover, which lowers future upgrade cost.

Reconciliation is the real exit test

A successful migration is proven by numbers. For each mock, reconcile inventory quantity and value by warehouse, receivables and payables by counterparty, and trial balance by account set. Keep a variance log and explain every difference before the next mock. Finance should sign the final reconciliation, not the project team. If a number moved because of a deliberate policy change, record that separately so auditors can follow it.

Common mistakes

Teams underestimate user training, run only one mock, cut over in the middle of a period, and forget that bank and tax interfaces need their own credentials and test windows. Another frequent error is treating the project as technical only, when the real change is in how cost accounting, approvals and permissions behave. Plan business sign-off at every stage.

Frequently Asked Questions

Is Kingdee K/3 Cloud the same product as Cloud Galaxy?

They are closely related. Kingdee's cloud ERP line for mid-size enterprises has been marketed under different names over time, and Cloud Galaxy is the current branding for that line. Always confirm with Kingdee which release and licence your estate maps to, because upgrade paths depend on version.

Should we upgrade in place or migrate to a new environment?

In-place upgrades keep history and configuration but carry old problems with them. A new environment with a data load gives a clean start but needs strong reconciliation. Choose based on data quality, customization volume and downtime tolerance, and confirm the supported route with Kingdee.

How many mock migrations are enough?

Two full mocks is a sensible minimum, and a third is wise for complex multi-entity estates. Each mock should include timings, reconciliation and a defect list. The final mock should follow the real cutover runbook exactly, including the rollback decision.

Does this checklist replace Kingdee's own guidance?

No. It is a project management aid built from common migration risks. Kingdee and your implementation partner own the technical upgrade procedure, tooling and supported paths for your release, and their instructions take priority over any generic list.

If you want help checking custom code, interfaces and reconciliations before cutover, Netray and its ERP partners can review your plan. Where policy allows, AI-assisted comparison can run on your own servers so project data stays in your control.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Kingdee K/3 Cloud to Cloud Galaxy Migration Checklist