Picture the first morning after a GP-to-Business Central cutover. A buyer opens an imported purchase order for a customer-specific item and finds nothing on it that points back to the sales order it was raised to fill. Both documents came across intact. The connection between them did not.
That gap is structural, not a migration bug. GP and Business Central model the sales-to-purchase relationship in different ways, so restoring it means understanding both models before writing a single field.
Which GP orders need their SOP-to-POP link migrated?
Only orders open at cutover. Consider a drop-ship order your team fully invoiced last quarter: its commitment is complete, and nothing in Business Central will act on it. Carrying that link forward adds mapping work with no payoff. Scope the effort to open sales and purchase pairs, the only ones planning and posting logic needs to see.
What does Business Central use instead of GP's link?
Two features: special orders and drop shipments, each with separate fields. A special order fills Special Order Purchase No. and Special Order Purch. Line No. on the Sales Line, mirrored on the Purchase Line. A drop shipment sets its own flag and uses Purchase Order No. Mislabel a GP drop-ship as a special order, and the receipt won't auto-post.
Why don't RapidStart configuration packages restore the link?
RapidStart works one table at a time, which is fine for records that stand on their own. The link is a different problem: it requires writing a purchase line number into a sales order after both documents exist in Business Central. Think of it as a join, not a load. RapidStart has no step for that cross-record update.
What sequence rebuilds the link after migration?
Import Export PowerTool handles it as a second pass. Import open GP orders first so every line has a real Business Central document and line number. Then update Sales Line and Purchase Line with the paired numbers, and set the Purchasing Code plus the Special Order or Drop Shipment boolean. Reversing that order leaves nothing to point at.
Why test the update pass in a sandbox before production?
Import Export PowerTool writes straight to document lines, outside the interface users normally work in, and field types matter. Special Order Purchase No. and Special Order Sales No. are Code[20]; paired line numbers are integers. Picture a sales line whose link points at another customer's purchase line: it looks connected on screen but won't behave that way.
Which GP fields help verify the migrated links?
The ones GP itself used to approve the match: item number or vendor item number, unit of measure, and site ID, plus customer ID and ship-to address for drop-ship orders. Export them with every open line. If a migrated pair fails to reconcile, those fields show whether the original match held.
Disclaimer: This content is shared for informational purposes and is not promotional.
Top comments (0)